public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH rtw-next 1/2] wifi: rtw88: usb: Reduce control message timeout to 500 ms
Date: Thu, 8 May 2025 19:41:58 +0300	[thread overview]
Message-ID: <2298a71e-2a52-4912-96b6-2c331dec8179@gmail.com> (raw)
In-Reply-To: <d661841634644d089c3250fda7ae43be@realtek.com>

On 08/05/2025 06:11, Ping-Ke Shih wrote:
> Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
>> RTL8811AU stops responding during the firmware download on some systems:
>>
>> [  809.256440] rtw_8821au 5-2.1:1.0: Firmware version 42.4.0, H2C version 0
>> [  812.759142] rtw_8821au 5-2.1:1.0 wlp48s0f4u2u1: renamed from wlan0
>> [  837.315388] rtw_8821au 1-4:1.0: write register 0x1ef4 failed with -110
>> [  867.524259] rtw_8821au 1-4:1.0: write register 0x1ef8 failed with -110
>> [  868.930976] rtw_8821au 5-2.1:1.0 wlp48s0f4u2u1: entered promiscuous mode
>> [  897.730952] rtw_8821au 1-4:1.0: write register 0x1efc failed with -110
>>
>> Each write takes 30 seconds to fail because that's the timeout currently
>> used for control messages in rtw_usb_write().
>>
>> In this scenario the firmware download takes at least 2000 seconds.
>> Because this is done from the USB probe function, the long delay makes
>> other things in the system hang.
>>
>> Reduce the timeout to 500 ms. This is the value used by the official USB
>> wifi drivers from Realtek.
> 
> A question about timeout time. Is this enough for USB 2 or older?
> 

Yes, it's fine.

>>
>> Of course this only makes things hang for ~30 seconds instead of ~30
>> minutes. It doesn't fix the firmware download.
>>
>> Tested with RTL8822CU, RTL8812BU, RTL8811CU, RTL8814AU, RTL8811AU,
>> RTL8812AU, RTL8821AU, RTL8723DU.
>>
>> Cc: stable@vger.kernel.org
>> Fixes: a82dfd33d123 ("wifi: rtw88: Add common USB chip support")
>> Link: https://github.com/lwfinger/rtw88/issues/344
>> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> 
> Acked-by: Ping-Ke Shih <pkshih@realtek.com>
> 
> 


      reply	other threads:[~2025-05-08 16:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 13:03 [PATCH rtw-next 1/2] wifi: rtw88: usb: Reduce control message timeout to 500 ms Bitterblue Smith
2025-05-07 13:05 ` [PATCH rtw-next 2/2] wifi: rtw88: usb: Upload the firmware in bigger chunks Bitterblue Smith
2025-05-08  3:29   ` Ping-Ke Shih
2025-05-08 16:58     ` Bitterblue Smith
2025-05-09  0:43       ` Ping-Ke Shih
2025-05-10 11:51         ` Bitterblue Smith
2025-05-08  3:11 ` [PATCH rtw-next 1/2] wifi: rtw88: usb: Reduce control message timeout to 500 ms Ping-Ke Shih
2025-05-08 16:41   ` Bitterblue Smith [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=2298a71e-2a52-4912-96b6-2c331dec8179@gmail.com \
    --to=rtl8821cerfe2@gmail.com \
    --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