Linux wireless drivers development
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ping-Ke Shih <pkshih@realtek.com>,
	Larry Finger <Larry.Finger@gmail.com>,
	Kalle Valo <kvalo@kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [RFC] rtw88: Fix startup problems for SDIO wifi plus UART Bluetooth
Date: Wed, 10 Apr 2024 21:47:58 -0500	[thread overview]
Message-ID: <287e9d4e-316a-4579-961e-58e75abea534@lwfinger.net> (raw)
In-Reply-To: <5af71338f3904aac9d2c237637c851e7@realtek.com>

On 4/10/24 9:13 PM, Ping-Ke Shih wrote:
> 
> Larry Finger <Larry.Finger@gmail.com> wrote:
> 
>> As discussed in the links below, the SDIO part of RTW8821CS fails to
>> start correctly if such startup happens while the UART portion of
>> the chip is initializing.
> 
> I checked with SDIO team internally, but they didn't meet this case, so we may
> take this workaround.
> 
> SDIO team wonder if something other than BT cause this failure, and after
> system boots everything will be well. Could you boot the system without WiFi/BT
> drivers, but insmod drivers manually after booting?

I sent the request to the user with the problem. I do not have any SDIO devices.

> 
> 
>> ---
>>   drivers/net/wireless/realtek/rtw88/sdio.c | 28 +++++++++++++++++++++++
>>   1 file changed, 28 insertions(+)
>>
>> diff --git a/drivers/net/wireless/realtek/rtw88/sdio.c b/drivers/net/wireless/realtek/rtw88/sdio.c
>> index 0cae5746f540..eec0ad85be72 100644
>> --- a/drivers/net/wireless/realtek/rtw88/sdio.c
>> +++ b/drivers/net/wireless/realtek/rtw88/sdio.c
>> @@ -1325,6 +1325,34 @@ int rtw_sdio_probe(struct sdio_func *sdio_func,
> 
> [...]
> 
>> +       mdelay(500);
> 
> Will it better to use sleep function?

My thoughts were that a sleep function would tie up a CPU, whereas the delay 
would not. Initially, we tested an msleep(150) statement, but that only gave a 
60% success rate, whereas mdelay(500) worked 20 straight tries.

Thanks for your comments.

Larry



  reply	other threads:[~2024-04-11  2:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  1:26 [RFC] rtw88: Fix startup problems for SDIO wifi plus UART Bluetooth Larry Finger
2024-04-11  2:13 ` Ping-Ke Shih
2024-04-11  2:47   ` Larry Finger [this message]
2024-04-11  4:25     ` Ping-Ke Shih
2024-04-11  7:08     ` Kalle Valo
2024-04-11 17:28       ` Larry Finger
2024-04-15  0:45         ` Ping-Ke Shih
2024-04-15  1:23           ` Larry Finger

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=287e9d4e-316a-4579-961e-58e75abea534@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=Larry.Finger@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=stable@vger.kernel.org \
    /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