From: Ping-Ke Shih <pkshih@realtek.com>
To: Devin Wittmayer <lucid_duck@justthetip.ca>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH rtw-next v2 1/1] wifi: rtw89: usb: Support switching to USB 3 mode
Date: Tue, 12 May 2026 01:25:16 +0000 [thread overview]
Message-ID: <c71a1459979040f0a33b3f0b839deb76@realtek.com> (raw)
In-Reply-To: <20260511180351.26471-1-lucid_duck@justthetip.ca>
Devin Wittmayer <lucid_duck@justthetip.ca> wrote:
>
> On Mon, 2026-05-11 at 19:26 +0200, Johannes Berg wrote:
> > > +static bool rtw89_switch_usb_mode = true;
> > > +module_param_named(switch_usb_mode, rtw89_switch_usb_mode, bool, 0644);
> > > +MODULE_PARM_DESC(switch_usb_mode,
> > > + "Set to N to disable switching to USB 3 mode to avoid potential interference in the 2.4
> GHz band (default: Y)");
> >
> > We shouldn't really add new module parameters.
This module parameter follows the pattern Bitterblue established for
> rtw88: same user-facing name (switch_usb_mode), same description, same
> default. Commit 315c23a64e99 "wifi: rtw88: usb: Support USB 3 with
> RTL8822CU/RTL8822BU" (2024-07-10) added it to rtw88/usb.c and it
> remains in-tree.
I took the patch of rtw88 because we switch USB mode at probe stage, but
USB 3 mode has interference on 2.4GHz band (as the comment says). If a user
insist on 2.4GHz with a good performance, this is an option to keep USB 2
mode.
>
> Three v3 paths I see:
>
> 1. Drop the param. Users hitting USB3 2.4 GHz harmonic interference
> would need to use a USB 2 port instead.
> 2. Move the escape hatch behind a sysfs or nl80211 control. New UABI
> surface; open to design suggestions on that.
> 3. Keep it for rtw89/rtw88 symmetry on the same USB3 / 2.4 GHz
> harmonic interference issue.
An additional option might be to not support 2.4GHz channels when switching
to USB 3. But I'm not really sure if it is acceptable to USB users.
Ping-Ke
next prev parent reply other threads:[~2026-05-12 1:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 5:44 [PATCH 0/1] wifi: rtw89: usb: Support switching to USB 3 mode Lucid Duck
2026-05-08 5:44 ` [PATCH 1/1] " Lucid Duck
2026-05-08 6:59 ` Zenm Chen
2026-05-11 10:55 ` [PATCH 0/1] " Bitterblue Smith
2026-05-11 16:08 ` [PATCH rtw-next v2 " Devin Wittmayer
2026-05-11 16:08 ` [PATCH rtw-next v2 1/1] " Devin Wittmayer
2026-05-11 17:26 ` Johannes Berg
2026-05-11 18:03 ` Devin Wittmayer
2026-05-12 1:25 ` Ping-Ke Shih [this message]
2026-05-11 18:14 ` Bitterblue Smith
2026-05-11 20:03 ` Devin Wittmayer
2026-05-11 22:27 ` Bitterblue Smith
2026-05-12 0:35 ` Devin Wittmayer
2026-05-12 8:48 ` Bitterblue Smith
2026-05-12 1:35 ` Ping-Ke Shih
2026-05-12 2:54 ` Devin Wittmayer
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=c71a1459979040f0a33b3f0b839deb76@realtek.com \
--to=pkshih@realtek.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lucid_duck@justthetip.ca \
--cc=rtl8821cerfe2@gmail.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