All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sridhar Arra <sridhar.arra.dev@gmail.com>
To: gregkh@linuxfoundation.org
Cc: error27@gmail.com, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Sridhar Arra <sridhar.arra.dev@gmail.com>
Subject: [PATCH] staging: rtl8723bs: replace msleep with usleep_range for short delays
Date: Sat,  9 May 2026 13:37:27 +0530	[thread overview]
Message-ID: <20260509080727.21636-1-sridhar.arra.dev@gmail.com> (raw)

The checkpatch.pl tool warns that msleep() for values less than 20ms
can be inaccurate. This patch converts the 10ms msleep to
usleep_range(10000, 11000) to provide more precise timing using
high-resolution timers.

Signed-off-by: Sridhar Arra <sridhar.arra.dev@gmail.com>
---
 drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c b/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
index 5f00fe282d1b..d66f17076818 100644
--- a/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
+++ b/drivers/staging/rtl8723bs/core/rtw_mlme_ext.c
@@ -5834,7 +5834,8 @@ u8 chk_bmc_sleepq_hdl(struct adapter *padapter, unsigned char *pbuf)
 		return H2C_SUCCESS;
 
 	if ((pstapriv->tim_bitmap & BIT(0)) && (psta_bmc->sleepq_len > 0)) {
-		msleep(10);/*  10ms, ATIM(HIQ) Windows */
+		/* 10ms - 11ms, ATIM(HIQ) Windows */
+		usleep_range(10000, 11000);
 
 		/* spin_lock_bh(&psta_bmc->sleep_q.lock); */
 		spin_lock_bh(&pxmitpriv->lock);
-- 
2.34.1


             reply	other threads:[~2026-05-09  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-09  8:07 Sridhar Arra [this message]
2026-05-11  8:06 ` [PATCH] staging: rtl8723bs: replace msleep with usleep_range for short delays Greg KH

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=20260509080727.21636-1-sridhar.arra.dev@gmail.com \
    --to=sridhar.arra.dev@gmail.com \
    --cc=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.