Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Shashikala Prabhu <shashikala.prabhu@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, vikram@qti.qualcomm.com,
	 kiranv@qti.qualcomm.com, pshashik@qti.qualcomm.com,
	cgopi@qti.qualcomm.com, ybasamma@qti.qualcomm.com,
	vthiagar@qti.qualcomm.com, sivad@qti.qualcomm.com,
		uvignesh@qti.qualcomm.com, mohathan@qti.qualcomm.com,
	abishekg@qti.qualcomm.com
Subject: Re: [PATCH wireless-next 1/2] wifi: nl80211: Add NL80211_ATTR_MAX_CH_SWITCH_TIME attribute
Date: Thu, 04 Jun 2026 13:02:25 +0200	[thread overview]
Message-ID: <09e2bd29cf9f8ad3fe64776343fd1e06426ea362.camel@sipsolutions.net> (raw)
In-Reply-To: <20260518103106.1462604-2-shashikala.prabhu@oss.qualcomm.com>

On Mon, 2026-05-18 at 16:01 +0530, Shashikala Prabhu wrote:
> From: Chandru Gopi <cgopi@qti.qualcomm.com>
> 
> IEEE Std 802.11-2024 subclause 9.4.2.216 (Max Channel Switch Time element)
> defines a Switch Time field in the Channel Switch Announcement (CSA)
> element that indicates the time delta between the time the last beacon
> is transmitted by the AP in the current channel and the expected time
> of the first beacon transmitted by the AP in the new channel.
> 
> Add a new u32 nl80211 attribute, NL80211_ATTR_MAX_CH_SWITCH_TIME,
> to carry this value in the NL80211_CMD_CH_SWITCH_STARTED_NOTIFY
> event. Userspace can use this information to decide whether to
> remain connected or disconnect before the AP moves to the new
> channel.

This really confused me a lot because that event is used on both sides
... don't include the new netlink attribute when it's on the AP side.

Also bad split with the patches - make one cfg/nl80211 API patch, and
one mac80211 patch.

>  	NL80211_ATTR_NPCA_PUNCT_BITMAP,
>  
> +	NL80211_ATTR_MAX_CH_SWITCH_TIME,
>  	/* add attributes here, update the policy in nl80211.c */

nit: looks odd without the blank line

> +++ b/net/wireless/nl80211.c
> @@ -1093,6 +1093,7 @@ static const struct nla_policy nl80211_policy[NUM_NL80211_ATTR] = {
>  	[NL80211_ATTR_NPCA_PRIMARY_FREQ] = { .type = NLA_U32 },
>  	[NL80211_ATTR_NPCA_PUNCT_BITMAP] =
>  		NLA_POLICY_FULL_RANGE(NLA_U32, &nl80211_punct_bitmap_range),
> +	[NL80211_ATTR_MAX_CH_SWITCH_TIME] = { .type = NLA_U32 },

That seems wrong since it's output only, it shouldn't even be accepted
on input.

johannes

  reply	other threads:[~2026-06-04 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 10:31 [PATCH wireless-next 0/2] wifi: cfg80211/mac80211: Add Max Channel Switch Time (MCST) in channel switch started notify event Shashikala Prabhu
2026-05-18 10:31 ` [PATCH wireless-next 1/2] wifi: nl80211: Add NL80211_ATTR_MAX_CH_SWITCH_TIME attribute Shashikala Prabhu
2026-06-04 11:02   ` Johannes Berg [this message]
2026-05-18 10:31 ` [PATCH wireless-next 2/2] wifi: cfg80211/mac80211: Pass MCST element value in ch_switch_started_notify Shashikala Prabhu

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=09e2bd29cf9f8ad3fe64776343fd1e06426ea362.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=abishekg@qti.qualcomm.com \
    --cc=cgopi@qti.qualcomm.com \
    --cc=kiranv@qti.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mohathan@qti.qualcomm.com \
    --cc=pshashik@qti.qualcomm.com \
    --cc=shashikala.prabhu@oss.qualcomm.com \
    --cc=sivad@qti.qualcomm.com \
    --cc=uvignesh@qti.qualcomm.com \
    --cc=vikram@qti.qualcomm.com \
    --cc=vthiagar@qti.qualcomm.com \
    --cc=ybasamma@qti.qualcomm.com \
    /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