Linux-Wireless Archive mirror
 help / color / mirror / Atom feed
From: Rathees Kumar R Chinannan <quic_rrchinan@quicinc.com>
To: <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>, <quic_rrchinan@quicinc.com>
Subject: [RFC v2 0/2] wifi: nl80211/mac80211 Handle BSS critical update
Date: Wed, 3 Apr 2024 21:52:23 +0530	[thread overview]
Message-ID: <20240403162225.3096228-1-quic_rrchinan@quicinc.com> (raw)

When a critical update occurs to any of elements inside beacon frame, AP
shall increment BSS Parameters Change Count(BPCC) subfield and set the
Critical Update flag subfield of the Capability Information to notify
client that the critical update occurred on AP. Refer section "35.3.10
BSS parameter critical update procedure" on IEEE P802.11be D4.0 for
details.

On beacon offload case, change in CU parameters should be sent to user
space either before or along with probe or assoc request frame receive
to ensure that user space uses latest CU values and BPCC while generating
response to the received frames. So, add the critical update parameters
as a new attribute to existing NL80211_CMD_FRAME command instead of
sending this on a separate NL80211 event.

Add an ieee80211_critical_update() API to send the parameters to cfg80211
and call it when event received from firmware to update critical
parameters to user space.

Driver (ath12k) changes that utilize this will be posted in the future
versions.

Based on the suggestion received on below link, add extended feature
NL80211_EXT_FEATURE_CRITICAL_UPDATE_OFFLOAD flag if driver handles
synchronization among all the links and update critical information on
partner link beacon for AP MLD and user space can update critical
information only on impacted link beacon template. Add this critical
update attribute on NL80211_CMD_FRAME only when this flag is set
by driver.

Link: https://lore.kernel.org/all/df711a5978b84856a54953a32e4b05923b48870a.camel@sipsolutions.net/
Suggested-by: Johannes Berg <johannes@sipsolutions.net>

Rathees Kumar R Chinannan (2):
  wifi: nl80211: Add attribute to send critical update parameters
  wifi: mac80211: Indicate ongoing critical update parameters

 include/net/cfg80211.h       |  10 +++
 include/net/mac80211.h       |  13 ++++
 include/uapi/linux/nl80211.h | 104 +++++++++++++++++++++++++++++
 net/mac80211/cfg.c           |  43 +++++++++++-
 net/mac80211/rx.c            |  12 ++++
 net/mac80211/tx.c            |   9 +++
 net/wireless/nl80211.c       | 123 ++++++++++++++++++++++++++++++++++-
 7 files changed, 312 insertions(+), 2 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-04-03 16:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 16:22 Rathees Kumar R Chinannan [this message]
2024-04-03 16:22 ` [RFC v2 1/2] wifi: nl80211: Add attribute to send critical update parameters Rathees Kumar R Chinannan
2024-05-03  9:12   ` Johannes Berg
2024-05-07 17:25     ` Rathees Kumar R Chinannan
2024-04-03 16:22 ` [RFC v2 2/2] wifi: mac80211: Indicate ongoing " Rathees Kumar R Chinannan
2024-05-03  9:27 ` [RFC v2 0/2] wifi: nl80211/mac80211 Handle BSS critical update Johannes Berg
2024-05-07 17:49   ` Rathees Kumar R Chinannan

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=20240403162225.3096228-1-quic_rrchinan@quicinc.com \
    --to=quic_rrchinan@quicinc.com \
    --cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).