<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/net/mac80211/ocb.c, branch linux-6.9.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.9.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.9.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2024-02-12T20:13:57Z</updated>
<entry>
<title>wifi: mac80211: flush only stations using requests links</title>
<updated>2024-02-12T20:13:57Z</updated>
<author>
<name>Aditya Kumar Singh</name>
</author>
<published>2024-02-05T16:29:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ec67d6e0d491d2a2df270ddcb7aa44db0984e11c'/>
<id>urn:sha1:ec67d6e0d491d2a2df270ddcb7aa44db0984e11c</id>
<content type='text'>
Whenever sta_flush() function is invoked, all STAs present in that
interface are flushed. In case of MLO, it is desirable to only flush such
STAs that are at least using a given link id as one of their links.

Add support for this by making change in the __sta_info_flush API argument
to accept a link ID. And then, only if the STA is using the given link as
one of its links, it would be flushed.

Signed-off-by: Aditya Kumar Singh &lt;quic_adisi@quicinc.com&gt;
Link: https://msgid.link/20240205162952.1697646-3-quic_adisi@quicinc.com
[reword commit message, in particular this isn't about "active" links]
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: introduce 'channel request'</title>
<updated>2024-02-08T12:07:34Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2024-01-29T18:34:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6092077ad09ce880c61735c314060f0bd79ae4aa'/>
<id>urn:sha1:6092077ad09ce880c61735c314060f0bd79ae4aa</id>
<content type='text'>
For channel contexts, mac80211 currently uses the cfg80211
chandef struct (control channel, center freq(s), width) to
define towards drivers and internally how these behave. In
fact, there are _two_ such structs used, where the min_def
can reduce bandwidth according to the stations connected.

Unfortunately,  with EHT this is longer be sufficient,  at
least not for all hardware.  EHT requires that non-AP STAs
that are connected to an AP with a lower bandwidth than it
(the AP) advertises (e.g. 160 MHz STA connected to 320 MHz
AP) still be able to receive downlink OFDMA and respond to
trigger frames for uplink OFDMA  that specify the position
and bandwidth  for the non-AP STA  relative to the channel
the AP is using.  Therefore, they need to be aware of this,
and at least for some hardware (e.g. Intel) this awareness
is in the hardware. As a result, use of the "same" channel
may need to be split over  two channel contexts where they
differ by the AP being used.

As a first step,  introduce a concept of a channel request
('chanreq') for each interface,  to control the context it
requests.   This step does nothing but reorganise the code,
so that later the AP's chandef can be added to the request
in order to handle the EHT case described above.

Link: https://msgid.link/20240129194108.2e88e48bd2e9.I4256183debe975c5ed71621611206fdbb69ba330@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: cfg80211: remove scan_width support</title>
<updated>2023-09-13T09:10:50Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2023-08-29T10:17:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5add321c329b1746589b51359259666ca3dbe219'/>
<id>urn:sha1:5add321c329b1746589b51359259666ca3dbe219</id>
<content type='text'>
There really isn't any support for scanning at different
channel widths than 20 MHz since there's no way to set it.
Remove this support for now, if somebody wants to maintain
this whole thing later we can revisit how it should work.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: cfg80211: remove wdev mutex</title>
<updated>2023-09-11T09:27:23Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2023-08-29T10:18:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=076fc8775dafe995e94c106bb732bf2d42dedcea'/>
<id>urn:sha1:076fc8775dafe995e94c106bb732bf2d42dedcea</id>
<content type='text'>
Since we're now protecting everything with the wiphy mutex
(and were really using it for almost everything before),
there's no longer any real reason to have a separate wdev
mutex. It may feel better, but really has no value.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: remove local-&gt;mtx</title>
<updated>2023-09-11T09:27:22Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2023-08-28T12:00:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0cd8080e46b834fa72026112488ab61d4b82f03a'/>
<id>urn:sha1:0cd8080e46b834fa72026112488ab61d4b82f03a</id>
<content type='text'>
We now hold the wiphy mutex everywhere that we use or
needed the local-&gt;mtx, so we don't need this mutex any
more. Remove it.

Most of this change was done automatically with spatch.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: use wiphy work for sdata-&gt;work</title>
<updated>2023-06-07T17:53:18Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2023-06-06T12:49:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=16114496d684a3df4ce09f7c6b7557a8b2922795'/>
<id>urn:sha1:16114496d684a3df4ce09f7c6b7557a8b2922795</id>
<content type='text'>
We'll need this later to convert other works that might
be cancelled from here, so convert this one first.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: consistently use u64 for BSS changes</title>
<updated>2023-06-06T12:16:48Z</updated>
<author>
<name>Anjaneyulu</name>
</author>
<published>2023-06-04T09:11:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=15ddba5f43114c1fd9cd83676e04a9e1acf8e37f'/>
<id>urn:sha1:15ddba5f43114c1fd9cd83676e04a9e1acf8e37f</id>
<content type='text'>
Currently, enum ieee80211_bss_change has more than 32 flags.
Change the type of the corresponding variables from u32 to u64.

Signed-off-by: Anjaneyulu &lt;pagadala.yesu.anjaneyulu@intel.com&gt;
Signed-off-by: Gregory Greenman &lt;gregory.greenman@intel.com&gt;
Link: https://lore.kernel.org/r/20230604120651.10354a05eaf1.If19359262fe2728dd523ea6d7c3aa7dc50940411@changeid
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: fix up link station creation/insertion</title>
<updated>2022-07-15T09:43:23Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2022-07-14T21:40:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f36fe0a2df03209f4d681fa954f20bfa4eefec45'/>
<id>urn:sha1:f36fe0a2df03209f4d681fa954f20bfa4eefec45</id>
<content type='text'>
When we create a station with a non-default link, then
we should have a link address, and we definitely need
to insert it into the link hash table on insertion.

Split the API into with and without link creation and
if it has a link, insert the link into the link hash
table on sta_info_insert().

Fixes: ba6ddab94fc6 ("wifi: mac80211: maintain link-sta hash table")
Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: move IEEE80211_SDATA_OPERATING_GMODE to link</title>
<updated>2022-07-15T09:43:21Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2022-07-12T08:49:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=39eac2de0098c3ac3e9c35cfdc924543f1f67acc'/>
<id>urn:sha1:39eac2de0098c3ac3e9c35cfdc924543f1f67acc</id>
<content type='text'>
The flag here is currently per interface, but the way we
set and clear it means it should be per link, so change
it.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
<entry>
<title>wifi: mac80211: RCU-ify link/link_conf pointers</title>
<updated>2022-07-15T09:43:14Z</updated>
<author>
<name>Johannes Berg</name>
</author>
<published>2022-06-17T20:36:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d8675a63518c6148827838058feb7f18403faed1'/>
<id>urn:sha1:d8675a63518c6148827838058feb7f18403faed1</id>
<content type='text'>
Since links can be added and removed dynamically, we need to
somehow protect the sdata-&gt;link[] and vif-&gt;link_conf[] array
pointers from disappearing when accessing them without locks.
RCU-ify the pointers to achieve this, which requires quite a
bit of rework.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
</content>
</entry>
</feed>
