public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Karthikeyan Kathirvel <karthikeyan.kathirvel@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC wireless-next 02/13] wifi: ieee80211: Add UHR (802.11bn) definitions
Date: Tue, 16 Dec 2025 10:08:37 +0100	[thread overview]
Message-ID: <94411a1f601b3b4cbc09cb780c37df9013f3b6bb.camel@sipsolutions.net> (raw)
In-Reply-To: <20251216062656.1738022-3-karthikeyan.kathirvel@oss.qualcomm.com>

On Tue, 2025-12-16 at 11:56 +0530, Karthikeyan Kathirvel wrote:
> 
> +/**
> + * struct ieee80211_uhr_mcs_nss_supp_20mhz_only - UHR 20 MHz only station max
> + * supported NSS for per MCS.

I think I'd rename this? Due to

> + * As per spec P802.11bn_D1.0 38.3.11 - "UHR-MCS 0-15 are the same as
> + * EHT-MCS 0-15"

it will only ever be used for basic UHR MCSes.

> +#define IEEE80211_UHR_DBE_CAP_MAX_BW			GENMASK(2, 0)
> +#define IEEE80211_UHR_DBE_CAP_EHT_MCS_BW_160MHZ_PRES	BIT(3)
> +#define IEEE80211_UHR_DBE_CAP_EHT_MCS_BW_320MHZ_PRES	BIT(4)
> +#define IEEE80211_UHR_DBE_CAP_RESERVED			GENMASK(7, 5)
> +#define IEEE80211_UHR_DBE_CAP_EHT_MCS_BW_160MHZ		GENMASK(31, 8)
> +#define IEEE80211_UHR_DBE_CAP_EHT_MCS_BW_320MHZ		GENMASK(55, 32)

For the record, I'm not a huge fan of GENMASK(), I tend to think just
hex is more readable :-)

Here, using GENMASK() is also wrong for the last one of those, and it's
really not obvious.


> +/**
> + * struct ieee80211_uhr_operation_info - uhr operation information

nit: "UHR" (throughout)

johannes

  reply	other threads:[~2025-12-16  9:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16  6:26 [PATCH RFC wireless-next 00/13] wifi: ieee80211/cfg80211: Add UHR (802.11bn) Capability and Operation support Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 01/13] wifi: nl80211: reduce multiple deference of link_sta_params Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 02/13] wifi: ieee80211: Add UHR (802.11bn) definitions Karthikeyan Kathirvel
2025-12-16  9:08   ` Johannes Berg [this message]
2025-12-17 12:54     ` Karthikeyan Kathirvel
2025-12-17 12:55       ` Johannes Berg
2025-12-17 12:56         ` Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 03/13] wifi: cfg80211: Add data structures to capture UHR capabilities Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 04/13] wifi: cfg80211: add a helper function to return the UHR interface capabilities Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 05/13] wifi: cfg80211: Support configuration of station UHR capabilities Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 06/13] wifi: nl80211: retrieve UHR related elements in AP mode Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 07/13] wifi: nl80211/reg: add no-UHR regulatory flag Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 08/13] wifi: mac80211: Support parsing UHR elements Karthikeyan Kathirvel
2025-12-16  9:10   ` Johannes Berg
2025-12-16  6:26 ` [PATCH RFC wireless-next 09/13] wifi: mac80211: Add UHR capabilities to association/probe request for STA mode Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 10/13] wifi: mac80211: Handle station association response with UHR Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 11/13] wifi: mac80211: set UHR support flag in AP mode Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 12/13] wifi: cfg80211: support disabling UHR mode Karthikeyan Kathirvel
2025-12-16  6:26 ` [PATCH RFC wireless-next 13/13] wifi: mac80211_hwsim: Add UHR capabilities in driver Karthikeyan Kathirvel
2025-12-16  9:04 ` [PATCH RFC wireless-next 00/13] wifi: ieee80211/cfg80211: Add UHR (802.11bn) Capability and Operation support Johannes Berg
2025-12-16  9:12   ` Johannes Berg
2025-12-17 10:05     ` Karthikeyan Kathirvel
2025-12-22 11:59       ` 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=94411a1f601b3b4cbc09cb780c37df9013f3b6bb.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