From: Johannes Berg <johannes@sipsolutions.net>
To: Karthikeyan Kathirvel <karthikeyan.kathirvel@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org
Subject: Re: [PATCH wireless-next v2 1/2] wifi: UHR: define DPS/DBE/P-EDCA elements and fix size parsing
Date: Thu, 12 Feb 2026 18:34:20 +0100 [thread overview]
Message-ID: <7ac00be5cfa6a31b91d72db027030b89195f25a2.camel@sipsolutions.net> (raw)
In-Reply-To: <20260212172401.234059-2-karthikeyan.kathirvel@oss.qualcomm.com>
Hi,
Nice, thanks for sending this.
> + * subclause 9.4.1.87. Refer Figure 9-207u.
> + * Please refer IEEE80211_UHR_DPS*
"refer to"? Or "See Figure ..."?
> +#define IEEE80211_UHR_DPS_PADDING_DELAY 0x0000003F
> +#define IEEE80211_UHR_DPS_RESERVED1 0x000000C0
> +#define IEEE80211_UHR_DPS_TRANSITION_DELAY 0x00003F00
> +#define IEEE80211_UHR_DPS_RESERVED2 0x0000C000
> +#define IEEE80211_UHR_DPS_ICF_REQUIRED 0x00010000
> +#define IEEE80211_UHR_DPS_PARAMETERIZED_FLAG 0x00020000
> +#define IEEE80211_UHR_DPS_LC_MODE_BW 0x001C0000
> +#define IEEE80211_UHR_DPS_LC_MODE_NSS 0x01E00000
> +#define IEEE80211_UHR_DPS_LC_MODE_MCS 0x1E000000
> +#define IEEE80211_UHR_DPS_MOBILE_AP_DPS_STATIC_HCM 0x20000000
> +#define IEEE80211_UHR_DPS_RESERVED3 0xC0000000
Not sure I'd defined the ..._RESERVED* ones at all? There's no way we'd
ever use them really unless they get defined to something else.
> + * subclause 9.4.1.87. Refer Figure 9-207u.
> + *
> + * Please refer IEEE80211_UHR_DPS*
Also here as well.
> +#define IEEE80211_UHR_DBE_OPER_BANDWIDTH 0x07
> +#define IEEE80211_UHR_DBE_OPER_DIS_SUBCHANNEL_BITMAP_PRES 0x08
> +#define IEEE80211_UHR_DBE_OPER_RESERVED 0xF0
same comment about reserved
> +#define IEEE80211_UHR_DBE_OPER_DIS_SUBCHANNEL_BITMAP 0xFFFF
And this ... I think should just not be there? When would we ever mask a
16 bit value with an all 16 bits mask?
> +#define IEEE80211_UHR_P_EDCA_RESERVED 0x7800
> +/**
reserved again, don't think it makes sense - and probably should have a
blank line before the /**
> static inline const struct ieee80211_uhr_npca_info *
> ieee80211_uhr_npca_info(const struct ieee80211_uhr_operation *oper)
> {
> + const u8 *pos;
> +
> if (!(oper->params & cpu_to_le16(IEEE80211_UHR_OPER_PARAMS_NPCA_ENA)))
> return NULL;
>
> - /* FIXME: DPS */
> + pos = oper->variable;
I'd probably have directly put 'const u8 *pos = oper->variable;', but
doesn't really matter.
johannes
next prev parent reply other threads:[~2026-02-12 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 17:23 [PATCH wireless-next v2 00/02] wifi: ieee80211/mac80211: Add UHR (802.11bn) Capability and Operation parsing helpers Karthikeyan Kathirvel
2026-02-12 17:24 ` [PATCH wireless-next v2 1/2] wifi: UHR: define DPS/DBE/P-EDCA elements and fix size parsing Karthikeyan Kathirvel
2026-02-12 17:34 ` Johannes Berg [this message]
2026-02-12 17:53 ` Karthikeyan Kathirvel
2026-02-12 17:24 ` [PATCH wireless-next v2 2/2] wifi: mac80211_hwsim: Add UHR capabilities to the driver Karthikeyan Kathirvel
2026-02-12 17:36 ` [PATCH wireless-next v2 00/02] wifi: ieee80211/mac80211: Add UHR (802.11bn) Capability and Operation parsing helpers Johannes Berg
2026-02-12 17:43 ` Karthikeyan Kathirvel
2026-02-12 18:29 ` Johannes Berg
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=7ac00be5cfa6a31b91d72db027030b89195f25a2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath12k@lists.infradead.org \
--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