Linux wireless drivers development
 help / color / mirror / Atom feed
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: Mon, 18 May 2026 07:51:17 +0000	[thread overview]
Message-ID: <5fc263787831471f87585fb90a9b0fcb@realtek.com> (raw)
In-Reply-To: <fcdde81a-97ec-458f-8e70-ac024938f1d7@gmail.com>

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?

> 
> Tested with RTL8832AU, RTL8832BU, RTL8832CU, and RTL8912AU.
> 
> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>

Some minor suggestions. Otherwise, 

Acked-by: Ping-Ke Shih <pkshih@realtek.com>

[...]

> diff --git a/drivers/net/wireless/realtek/rtw89/usb.c b/drivers/net/wireless/realtek/rtw89/usb.c
> index c6d55e669776..bfe004a49ccc 100644
> --- a/drivers/net/wireless/realtek/rtw89/usb.c
> +++ b/drivers/net/wireless/realtek/rtw89/usb.c
> @@ -12,7 +12,7 @@
>  static void rtw89_usb_read_port_complete(struct urb *urb);
> 
>  static void rtw89_usb_vendorreq(struct rtw89_dev *rtwdev, u32 addr,
> -                               void *data, u16 len, u8 reqtype)
> +                               void *data, u16 len, u8 reqtype, bool warn)
>  {
>         struct rtw89_usb *rtwusb = rtw89_usb_priv(rtwdev);
>         struct usb_device *udev = rtwusb->udev;
> @@ -52,7 +52,7 @@ static void rtw89_usb_vendorreq(struct rtw89_dev *rtwdev, u32 addr,
> 
>                 if (ret == -ESHUTDOWN || ret == -ENODEV)
>                         set_bit(RTW89_FLAG_UNPLUGGED, rtwdev->flags);
> -               else if (ret < 0)
> +               else if (ret < 0 && warn)
>                         rtw89_warn(rtwdev,
>                                    "usb %s%u 0x%x fail ret=%d value=0x%x attempt=%d\n",
>                                    str_read_write(reqtype == RTW89_USB_VENQT_READ),
> @@ -80,7 +80,7 @@ static u32 rtw89_usb_read_cmac(struct rtw89_dev *rtwdev, u32 addr)
> 
>         for (count = 0; ; count++) {
>                 rtw89_usb_vendorreq(rtwdev, addr32, &data, 4,
> -                                   RTW89_USB_VENQT_READ);
> +                                   RTW89_USB_VENQT_READ, true);

Not sure if you like to implement a __rtw89_usb_vendorreq(), and 
preserve rtw89_usb_vendorreq() as a wrapper with original prototype.
Then, no need to stir here. 

I mean:

__rtw89_usb_vendorreq(..., bool warn);

static void rtw89_usb_vendorreq(struct rtw89_dev *rtwdev, u32 addr,
				void *data, u16 len, u8 reqtype)
{
	__rtw89_usb_vendorreq(rtwdev, addr, data, len, reqtype, true);
}

(just a soft suggestion)

> 
>                 val32 = le32_to_cpu(data);
>                 if (val32 != RTW89_R32_DEAD)

[...]


  reply	other threads:[~2026-05-18  7:51 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 [this message]
2026-05-19 15:34   ` Bitterblue Smith
2026-05-20  0:46     ` 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=5fc263787831471f87585fb90a9b0fcb@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