From: Nam Cao <namcao@linutronix.de>
To: Omer PALA <palaomer100@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: replace msleep with usleep_range
Date: Thu, 17 Sep 2026 10:17:00 +0200 [thread overview]
Message-ID: <87mrtgthqb.fsf@yellow.woof> (raw)
In-Reply-To: <20260917071931.8063-1-palaomer100@gmail.com>
Omer PALA <palaomer100@gmail.com> writes:
> Replace msleep(1) with usleep_range(1000, 1500) because msleep with small
> values (<20ms) can sleep for up to 20ms due to timer tick resolution.
> Using usleep_range provides a more precise and consistent delay for
> hardware power control operations.
Why is precise delay important for power control?
Precise delay comes with a cost, so we don't do that unless necessary.
Nam
next prev parent reply other threads:[~2026-09-17 8:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 7:19 [PATCH] staging: rtl8723bs: replace msleep with usleep_range Omer PALA
2026-09-17 7:50 ` Dan Carpenter
2026-09-17 8:14 ` Ömer PALA
2026-09-19 7:43 ` Krzysztof Kozlowski
2026-09-17 8:17 ` Nam Cao [this message]
2026-09-17 8:24 ` Ömer PALA
-- strict thread matches above, loose matches on Subject: below --
2026-03-19 19:54 [PATCH] staging: rtl8723bs: Replace " AyushMukkanwar
2026-03-19 20:23 ` Ethan Tidmore
2026-03-20 7:42 ` Andy Shevchenko
2026-03-14 5:11 [PATCH] staging: rtl8723bs: replace " Marcos Andrade
2026-03-14 20:56 ` Ethan Tidmore
2026-03-09 0:40 sluisr
2026-03-09 13:33 ` Bryant Boatright
2026-03-09 16:01 ` Greg KH
2026-02-14 17:31 Ofek Almog
2026-02-14 18:11 ` Ethan Tidmore
2026-02-14 18:24 ` Andy Shevchenko
2026-02-14 19:23 ` Ofek Almog
2026-02-15 6:52 ` Greg KH
2026-02-10 5:58 Vo Thanh Cong
2026-02-10 6:37 ` Greg Kroah-Hartman
2026-02-09 12:07 Ethan Lam
2026-02-09 12:35 ` Greg KH
2026-02-08 12:15 Miguel Angel De la Vega Rodriguez
2026-02-08 14:35 ` Greg Kroah-Hartman
2026-01-10 20:44 Işıkhan IŞIK
2026-01-11 12:49 ` 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=87mrtgthqb.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=palaomer100@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 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.