From: Louis Kotze <loukot@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Louis Kotze <loukot@gmail.com>
Subject: [PATCH 4/4] wifi: rtw89: advertise EHT OM Control for 8922a per WFA cert
Date: Mon, 4 May 2026 06:48:17 +0200 [thread overview]
Message-ID: <e280556159e254463092c82cba5035534624f171.1777832019.git.loukot@gmail.com> (raw)
In-Reply-To: <cover.1777832019.git.loukot@gmail.com>
Wi-Fi Alliance Certificate WFA129313 (RTL8922AE, 2024-05-23, firmware
6102.24.109.0) certifies "Operating mode indication" as a Wi-Fi 7
feature for this chip. The driver currently sets only MAX_MPDU_LEN +
RESTRICTED_TWT in mac_cap_info[0], leaving EHT OM Control unset.
Set IEEE80211_EHT_MAC_CAP0_OM_CONTROL in mac_cap_info[0]. EHT OM
Control extends the HE OMI control mechanism (already advertised at
the HE layer) to EHT-specific operating-mode notifications. mt76
(mt7996, mt7925) and iwlwifi mvm + mld already set this single bit
for their Wi-Fi 7 STAs; hwsim sets it in test code.
Tested on RTL8922AU against TP-Link Deco BE63; assoc + EMLSR multi-
link state remain stable.
Link: https://api.cert.wi-fi.org/api/certificate/download/public?variantId=129706 [WFA cert WFA129313]
Signed-off-by: Louis Kotze <loukot@gmail.com>
---
drivers/net/wireless/realtek/rtw89/core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/realtek/rtw89/core.c b/drivers/net/wireless/realtek/rtw89/core.c
index aedb2a284cd4..229c9f8ea65e 100644
--- a/drivers/net/wireless/realtek/rtw89/core.c
+++ b/drivers/net/wireless/realtek/rtw89/core.c
@@ -5564,7 +5564,8 @@ static void rtw89_init_eht_cap(struct rtw89_dev *rtwdev,
eht_cap_elem->mac_cap_info[0] =
u8_encode_bits(chip->max_eht_mpdu_cap,
IEEE80211_EHT_MAC_CAP0_MAX_MPDU_LEN_MASK) |
- IEEE80211_EHT_MAC_CAP0_RESTRICTED_TWT;
+ IEEE80211_EHT_MAC_CAP0_RESTRICTED_TWT |
+ IEEE80211_EHT_MAC_CAP0_OM_CONTROL;
eht_cap_elem->mac_cap_info[1] = 0;
eht_cap_elem->phy_cap_info[0] =
--
2.54.0
next prev parent reply other threads:[~2026-05-04 4:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 4:48 [PATCH 0/4] wifi: rtw89: advertise WFA-certified EHT capabilities for 8922a Louis Kotze
2026-05-04 4:48 ` [PATCH 1/4] wifi: rtw89: advertise EML Capabilities and Restricted TWT " Louis Kotze
2026-05-04 4:48 ` [PATCH 2/4] wifi: rtw89: advertise Multi-RU OFDMA receive for 8922a per WFA cert Louis Kotze
2026-05-04 4:48 ` [PATCH 3/4] wifi: rtw89: advertise MLD TID-to-link mapping and link reconfiguration Louis Kotze
2026-05-04 4:48 ` Louis Kotze [this message]
2026-05-06 9:12 ` [PATCH 0/4] wifi: rtw89: advertise WFA-certified EHT capabilities for 8922a Ping-Ke Shih
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=e280556159e254463092c82cba5035534624f171.1777832019.git.loukot@gmail.com \
--to=loukot@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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