From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Martin Kaiser <martin@kaiser.cx>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
Michael Straube <straube.linux@gmail.com>,
Pavel Skripkin <paskripkin@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] staging: r8188eu: remove rtw_usleep_os
Date: Mon, 6 Jun 2022 08:05:14 +0200 [thread overview]
Message-ID: <Yp2ZGp1JUSWaSzFI@kroah.com> (raw)
In-Reply-To: <20220602194807.281115-3-martin@kaiser.cx>
On Thu, Jun 02, 2022 at 09:48:06PM +0200, Martin Kaiser wrote:
> Remove the rtw_usleep_os helper function. There are only two callers, both
> of which call rtw_usleep_os(100).
>
> The original code would translate rtw_usleep_os(100) into msleep(1). Using
> msleep for < 20ms is not recommended. Replace the msleep calls with
> usleep_range, based on the explanations in
> Documentation/timers/timers-howto.rst.
>
> Signed-off-by: Martin Kaiser <martin@kaiser.cx>
> ---
> drivers/staging/r8188eu/core/rtw_pwrctrl.c | 2 +-
> drivers/staging/r8188eu/hal/rtl8188e_hal_init.c | 2 +-
> drivers/staging/r8188eu/include/osdep_service.h | 2 --
> drivers/staging/r8188eu/os_dep/osdep_service.c | 8 --------
> 4 files changed, 2 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/staging/r8188eu/core/rtw_pwrctrl.c b/drivers/staging/r8188eu/core/rtw_pwrctrl.c
> index 7b816b824947..11fd05633529 100644
> --- a/drivers/staging/r8188eu/core/rtw_pwrctrl.c
> +++ b/drivers/staging/r8188eu/core/rtw_pwrctrl.c
> @@ -266,7 +266,7 @@ static s32 LPS_RF_ON_check(struct adapter *padapter, u32 delay_ms)
> err = -1;
> break;
> }
> - rtw_usleep_os(100);
> + usleep_range(1000, 1200);
How do you know this is the proper range?
> }
>
> return err;
> diff --git a/drivers/staging/r8188eu/hal/rtl8188e_hal_init.c b/drivers/staging/r8188eu/hal/rtl8188e_hal_init.c
> index e17375a74f17..1aa7d01b67b1 100644
> --- a/drivers/staging/r8188eu/hal/rtl8188e_hal_init.c
> +++ b/drivers/staging/r8188eu/hal/rtl8188e_hal_init.c
> @@ -208,7 +208,7 @@ static void efuse_read_phymap_from_txpktbuf(
> rtw_write8(adapter, REG_TXPKTBUF_DBG, 0);
> timeout = jiffies + msecs_to_jiffies(1000);
> while (!rtw_read8(adapter, REG_TXPKTBUF_DBG) && time_before(jiffies, timeout))
> - rtw_usleep_os(100);
> + usleep_range(1000, 1200);
Same here, how do you know this is the correct range?
I would just use msleep as needed and later change to a range if you
have figured out that is allowed.
thanks,
greg k-h
next prev parent reply other threads:[~2022-06-06 6:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 19:48 [PATCH 0/3] staging: r8188eu: some minor cleanups Martin Kaiser
2022-06-02 19:48 ` [PATCH 1/3] staging: r8188eu: use ieee80211 defines for back action codes Martin Kaiser
2022-06-02 19:48 ` [PATCH 2/3] staging: r8188eu: remove rtw_usleep_os Martin Kaiser
2022-06-06 6:05 ` Greg Kroah-Hartman [this message]
2022-06-02 19:48 ` [PATCH 3/3] staging: r8188eu: fix the declaration of process_pwrbit_data Martin Kaiser
2022-06-03 20:52 ` [PATCH 0/3] staging: r8188eu: some minor cleanups Pavel Skripkin
2022-06-26 18:06 ` [PATCH v2] staging: r8188eu: remove rtw_usleep_os Martin Kaiser
2022-06-26 20:44 ` Philipp Hortmann
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=Yp2ZGp1JUSWaSzFI@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@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
all inboxes | Powered by JetHome®