From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: [PATCH wireless-next 00/14] wifi: UHR non-primary channel access
Date: Tue, 28 Apr 2026 11:25:28 +0200 [thread overview]
Message-ID: <20260428092708.71740-16-johannes@sipsolutions.net> (raw)
This series implements UHR NPCA (non-primary channel access) in general
(chandef etc.), for the AP side (just configuration values), and the
client (using it from assoc response.)
A few things to note:
- I know that the 802.11bn draft is likely to change and use an 8-bit
NPCA primary channel field, which changes the parsing. This will need
to be adjusted once that finalizes.
- This change will likely also come together with allowing NPCA to be
used inside the DBE rather than only inside the BSS bandwidth, but
we'll see how this will play out in the spec.
- I have, at least for now, deliberately opted to keep more patches
rather than squashing "don't parse full UHR operation from beacons"
and "separate NPCA validity from chandef validity" as I think it may
be easier to follow, but we can change that. It reflects my thought
process more than anything I guess.
- In addition to this I also have preliminary DBE (dynamic bandwidth
extension) patches, but I've opted to not include them here for now.
- For the AP side, I've only made "fake NPCA" patches that allow
advertising it with specific values in hostapd, rather than handling
the client request to enable it and updating the BSS values. I don't
really know how "real AP" vendors want to handle this, so I'm
deliberately leaving it out.
johannes
next reply other threads:[~2026-04-28 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 9:25 Johannes Berg [this message]
2026-04-28 9:25 ` [PATCH wireless-next 01/14] wifi: mac80211: use struct for ieee80211_determine_ap_chan() args Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 02/14] wifi: mac80211: move ieee80211_chandef_usable() up Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 03/14] wifi: mac80211: carry element parsing frame type/from_ap Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 04/14] wifi: cfg80211: allow representing NPCA in chandef Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 05/14] wifi: cfg80211: add helper for parsing NPCA to chandef Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 06/14] wifi: mac80211: use NPCA in chandef for validation Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 07/14] wifi: mac80211: remove NPCA during chandef downgrade Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 08/14] wifi: mac80211: add NPCA to chandef tracing Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 09/14] wifi: mac80211: allow only AP chanctx sharing with NPCA Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 10/14] wifi: mac80211: mlme: use NPCA chandef if capable Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 11/14] wifi: mac80211: set AP NPCA parameters in bss_conf Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 12/14] wifi: cfg80211: separate NPCA validity from chandef validity Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 13/14] wifi: mac80211: don't parse full UHR operation from beacons Johannes Berg
2026-04-28 9:25 ` [PATCH wireless-next 14/14] wifi: mac80211: check AP using NPCA has NPCA capability Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260428092708.71740-16-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox