From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next v3] wifi: rtw89: usb: Support switching to USB 3 mode
Date: Wed, 20 May 2026 00:46:17 +0000 [thread overview]
Message-ID: <97ff1c5305b9454eae55ec58db09158c@realtek.com> (raw)
In-Reply-To: <b4da28cd-17e0-46f2-a73c-e77d9c96cca1@gmail.com>
Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> On 18/05/2026 10:51, Ping-Ke Shih wrote:
> > Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> >> The Realtek wifi 6/7 devices which support USB 3 are weird: when first
> >> plugged in, they pretend to be USB 2. The driver needs to send some
> >> commands to the device, which make it disappear and come back as a
> >> USB 3 device.
> >>
> >> Implement the required commands in rtw89.
> >>
> >> Add a new function rtw89_usb_write32_quiet() to avoid the warnings
> >> when writing to R_{AX,BE}_PAD_CTRL2. Even though the write succeeds,
> >> usb_control_msg() returns -EPROTO, probably because the USB device
> >> disappears immediately. This results in some confusing warnings in
> >> the kernel log.
> >>
> >> When a USB 3 device is plugged into a USB 2 port, rtw89 will try to
> >> switch it to USB 3 mode only once. The device will disappear and come
> >> back still in USB 2 mode, of course.
> >
> > As we always try to switch USB 3, is it needed to add a hint to users
> > to plug USB 2 port if he has a bad performance on 2GHz band?
> >
>
> I can add a message like "2.4 GHz performance may be better in a USB 2
> port".
I suppose we should use rtw89_info().
I'll wait for v4.
prev parent reply other threads:[~2026-05-20 0:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 12:49 [PATCH rtw-next v3] wifi: rtw89: usb: Support switching to USB 3 mode Bitterblue Smith
2026-05-18 7:51 ` Ping-Ke Shih
2026-05-19 15:34 ` Bitterblue Smith
2026-05-20 0:46 ` Ping-Ke Shih [this message]
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=97ff1c5305b9454eae55ec58db09158c@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--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