public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 2/4] wifi: rtw89: advertise Multi-RU OFDMA receive for 8922a per WFA cert
Date: Mon,  4 May 2026 06:48:15 +0200	[thread overview]
Message-ID: <fe55fcddbbb3dcf41f77376795ab68024007256b.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) attests "Multi-RU" as a certified Wi-Fi 7 feature for
this chip. The driver currently hard-zeroes the corresponding receive
cap bit in rtw89_init_eht_cap(), which prevents the AP from scheduling
Multi-RU OFDMA TBF (Trigger-Based Frame) payloads with sub-242-tone RU
allocations to this STA.

Set IEEE80211_EHT_PHY_CAP5_RX_LESS_242_TONE_RU_SUPP in phy_cap_info[5]
to match the certified silicon behaviour. The Tx-side bit
(CAP5_TX_LESS_242_TONE_RU_SUPP) remains zero since this driver is
STA-mode only and Tx of Multi-RU TBFs is an AP-mode capability.

Tested on RTL8922AU (USB variant, same MAC + RF as cert'd PCIe AE)
against TP-Link Deco BE63 mesh; STA associates and remains stable for
24h+ with no regression in single-RU traffic patterns or in EMLSR
multi-link assoc behavior introduced by the previous EML+R-TWT patch.

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 056639db1dfa..986deb2c1384 100644
--- a/drivers/net/wireless/realtek/rtw89/core.c
+++ b/drivers/net/wireless/realtek/rtw89/core.c
@@ -5598,7 +5598,8 @@ static void rtw89_init_eht_cap(struct rtw89_dev *rtwdev,
 
 	eht_cap_elem->phy_cap_info[5] =
 		u8_encode_bits(IEEE80211_EHT_PHY_CAP5_COMMON_NOMINAL_PKT_PAD_20US,
-			       IEEE80211_EHT_PHY_CAP5_COMMON_NOMINAL_PKT_PAD_MASK);
+			       IEEE80211_EHT_PHY_CAP5_COMMON_NOMINAL_PKT_PAD_MASK) |
+		IEEE80211_EHT_PHY_CAP5_RX_LESS_242_TONE_RU_SUPP;
 
 	eht_cap_elem->phy_cap_info[6] = 0;
 	eht_cap_elem->phy_cap_info[7] = 0;
-- 
2.54.0


  parent reply	other threads:[~2026-05-04  4:48 UTC|newest]

Thread overview: 5+ 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 ` Louis Kotze [this message]
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 ` [PATCH 4/4] wifi: rtw89: advertise EHT OM Control for 8922a per WFA cert Louis Kotze

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=fe55fcddbbb3dcf41f77376795ab68024007256b.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