Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
	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: Thu, 11 Apr 2024 04:25:54 +0000	[thread overview]
Message-ID: <2afb5edcf8bf4173ab339e54707ada0b@realtek.com> (raw)
In-Reply-To: <287e9d4e-316a-4579-961e-58e75abea534@lwfinger.net>



Larry Finger <larry.finger@gmail.com> wrote:

> 
> On 4/10/24 9:13 PM, Ping-Ke Shih wrote:
> >
> > Larry Finger <Larry.Finger@gmail.com> wrote:
> >
> >> +       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.
> 

Sorry, I didn't consider the experimental results of msleep(150) and mdelay(500).

My point was busy waiting of mdelay(). I just want to say if msleep(500) is 
better than mdelay(500). 



  reply	other threads:[~2024-04-11  4:26 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
2024-04-11  4:25     ` Ping-Ke Shih [this message]
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=2afb5edcf8bf4173ab339e54707ada0b@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Larry.Finger@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --cc=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --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