Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Macias <dencity7@gmail.com>, linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH wireless] wifi: mac80211: use HT CCFS2 when computing the AP's HE and lower bandwidth
Date: Mon, 26 Oct 2026 12:07:16 +0100	[thread overview]
Message-ID: <116e1f238e2d78817a2ac5b42b00e0faeabf16bc.camel@sipsolutions.net> (raw)
In-Reply-To: <20261026040148.2633920-1-dencity7@gmail.com> (sfid-20261026_050215_574698_93BE14B6)

On Sun, 2026-10-25 at 21:01 -0700, John Macias wrote:
> If the driver advertises VHT extended NSS BW support, hostapd announces
> a 160 MHz BSS the way IEEE 802.11-2020 allows for that case: the VHT
> Operation element has channel width 1, CCFS0 is the 80 MHz segment and
> CCFS1 is 0, and the 160 MHz centre is in the CCFS2 field of the HT
> Operation element.
> 
> ieee80211_calc_ap_he_and_lower() only looks at the VHT CCFS1, so it
> sets bss_bw.he_and_lower to 80 MHz and ieee80211_sta_usable_bw() then
> limits every HE and VHT station to 80 MHz. Stations parse CCFS2 and use
> 160 MHz towards the AP, but the AP never transmits wider than 80 MHz.
> 
> Take CCFS2 from the HT Operation element when the VHT CCFS1 is 0, as
> the station side already does in ieee80211_chandef_vht_oper().

This, by itself, is wrong.

johannes

  reply	other threads:[~2026-10-26 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  4:01 [PATCH wireless] wifi: mac80211: use HT CCFS2 when computing the AP's HE and lower bandwidth John Macias
2026-10-26 11:07 ` Johannes Berg [this message]
2026-10-26 20:15   ` John Macias

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=116e1f238e2d78817a2ac5b42b00e0faeabf16bc.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=dencity7@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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