From: Johannes Berg <johannes@sipsolutions.net>
To: Karthikeyan Kathirvel <karthikeyan.kathirvel@oss.qualcomm.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH wireless-next v8 0/3] wifi: initial UHR support
Date: Mon, 02 Feb 2026 12:12:55 +0100 [thread overview]
Message-ID: <e0090840157dcb9968e683dab437296871bbd4a5.camel@sipsolutions.net> (raw)
In-Reply-To: <98c47cd2-6e90-4a17-a8a3-ea2d2290a72e@oss.qualcomm.com>
On Mon, 2026-02-02 at 16:20 +0530, Karthikeyan Kathirvel wrote:
>
> Would like to see your approach of NPCA for AP side, since we are
> working on Enhanced critical update for all UHR operation features(which
> includes NPCA as well).
So, FWIW, I went over this a few times in my head ... how do we support
it when one station has NPCA and another doesn't (need a per-STA flag?),
how do we update the NPCA operation when stations with different
parameters join/leave the BSS, etc.
Ultimately I decided that I'm going to leave these problems to you ;-)
For now literally all I've implemented for testing is an ability to
represent NPCA in the chandef (adding npca_chan and npca_punctured
bitmap to it), and two new nl80211 attributes to configure such a
chandef.
That won't even be an upstream hostapd patch, just some hack to set the
NPCA chandef in nl80211 and advertise it in the UHR operation element,
but it's already good enough to test a single client.
(Oh and nl80211 won't accept that unless the driver advertises NPCA
support in UHR for the AP interface, which our driver won't do outside
some testing mode.)
johannes
next prev parent reply other threads:[~2026-02-02 11:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 15:21 [PATCH wireless-next v8 0/3] wifi: initial UHR support Johannes Berg
2026-01-30 15:21 ` [PATCH wireless-next v8 1/3] wifi: ieee80211: add some initial UHR definitions Johannes Berg
2026-01-30 15:21 ` [PATCH wireless-next v8 2/3] wifi: cfg80211: add initial UHR support Johannes Berg
2026-02-11 14:19 ` Johannes Berg
2026-02-12 11:08 ` Harshitha Prem
2026-02-13 10:11 ` Johannes Berg
2026-02-13 10:26 ` Johannes Berg
2026-02-16 17:39 ` Harshitha Prem
2026-02-16 17:17 ` Harshitha Prem
2026-02-17 10:05 ` Johannes Berg
2026-02-24 11:01 ` Harshitha Prem
2026-03-06 12:43 ` Johannes Berg
2026-03-12 5:49 ` Harshitha Prem
2026-03-12 8:22 ` Johannes Berg
2026-03-12 19:32 ` Johannes Berg
2026-01-30 15:21 ` [PATCH wireless-next v8 3/3] wifi: mac80211: " Johannes Berg
2026-01-30 18:29 ` Pablo MARTIN-GOMEZ
2026-02-02 8:27 ` Johannes Berg
2026-02-02 10:27 ` [PATCH wireless-next v8 0/3] wifi: " Pablo MARTIN-GOMEZ
2026-02-02 11:13 ` Johannes Berg
2026-02-02 10:50 ` Karthikeyan Kathirvel
2026-02-02 11:12 ` Johannes Berg [this message]
2026-02-05 8:38 ` Karthikeyan Kathirvel
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=e0090840157dcb9968e683dab437296871bbd4a5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=karthikeyan.kathirvel@oss.qualcomm.com \
--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