From: Ping-Ke Shih <pkshih@realtek.com>
To: <linux-wireless@vger.kernel.org>
Cc: <owen.hsiao@realtek.com>, <echuang@realtek.com>,
<henchy.chen@realtek.com>, <phhuang@realtek.com>,
<kevin_yang@realtek.com>
Subject: [PATCH rtw-next v2 03/14] wifi: rtw89: allow two station interfaces in SCC
Date: Wed, 2 Sep 2026 13:29:47 +0800 [thread overview]
Message-ID: <20260902052958.50371-4-pkshih@realtek.com> (raw)
In-Reply-To: <20260902052958.50371-1-pkshih@realtek.com>
From: Hsiao-Yung Chen <henchy.chen@realtek.com>
The single-channel interface combination previously permitted only one
STATION interface, alongside one P2P or AP interface. Raise the STATION
limit to two so that a STA + STA combination is allowed in the single
channel concurrency (SCC) case.
This enables concurrent dual-STA use cases on the same channel, such as
having one STA interface connected to an AP router for Internet access,
while the second STA interface connects to another local peer/device for
dedicated media/data streaming.
Benchmark results on RTL8922DE in 6 GHz / 80 MHz SCC mode (UDP):
STA1 alone SCC STA1+STA2 STA2 alone
UDP TX (Gbps) 0.95 0.52 + 0.49 0.99
UDP RX (Gbps) 0.95 0.56 + 0.46 0.95
Signed-off-by: Hsiao-Yung Chen <henchy.chen@realtek.com>
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
drivers/net/wireless/realtek/rtw89/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/realtek/rtw89/core.c b/drivers/net/wireless/realtek/rtw89/core.c
index 397ebbfcac09..24275c2250e7 100644
--- a/drivers/net/wireless/realtek/rtw89/core.c
+++ b/drivers/net/wireless/realtek/rtw89/core.c
@@ -167,7 +167,7 @@ static struct ieee80211_rate rtw89_bitrates[] = {
static const struct ieee80211_iface_limit rtw89_iface_limits[] = {
{
- .max = 1,
+ .max = 2,
.types = BIT(NL80211_IFTYPE_STATION),
},
{
--
2.25.1
next prev parent reply other threads:[~2026-09-02 5:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 5:29 [PATCH rtw-next v2 00/14] wifi: rtw89: update RTL8922D capabilities and settings, and enable P2P device Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 01/14] wifi: rtw89: 8922de: add low latency quirk for Valve device Ping-Ke Shih
2026-09-08 3:15 ` Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 02/14] wifi: rtw89: 8922d: disable VCORE for thermal protection by default Ping-Ke Shih
2026-09-08 6:03 ` Ping-Ke Shih
2026-09-02 5:29 ` Ping-Ke Shih [this message]
2026-09-02 5:29 ` [PATCH rtw-next v2 04/14] wifi: rtw89: 8922d: update BB wrapper RFSI ctrl to v4 Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 05/14] wifi: rtw89: 8922d: set BB wrapper settings according to operating channel Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 06/14] wifi: rtw89: 8922d: move conditionally disabled TX shape to common flow Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 07/14] wifi: rtw89: 8922d: update BB wrapper RFSI ctrl to v5 Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 08/14] wifi: rtw89: 8922d: send RFE type to firmware Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 09/14] wifi: rtw89: 8922d: bypass RX IQK when scan Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 10/14] wifi: rtw89: 8922d: correct selection of CCK rate circuit Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 11/14] wifi: rtw89: chan: introduce helper and refine active list iteration Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 12/14] wifi: rtw89: regd: check only active vifs when recalculating 6 GHz power type Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 13/14] wifi: rtw89: skip tracking things when entity is paused Ping-Ke Shih
2026-09-02 5:29 ` [PATCH rtw-next v2 14/14] wifi: rtw89: add p2p device declaration Ping-Ke Shih
2026-09-06 0:20 ` [PATCH rtw-next v2 00/14] wifi: rtw89: update RTL8922D capabilities and settings, and enable P2P device Maxim Skokov
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=20260902052958.50371-4-pkshih@realtek.com \
--to=pkshih@realtek.com \
--cc=echuang@realtek.com \
--cc=henchy.chen@realtek.com \
--cc=kevin_yang@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=owen.hsiao@realtek.com \
--cc=phhuang@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