From: Julia Lawall <julia.lawall@inria.fr>
To: Abubakar Musa Samaila <abubakarmusasamaila@gmail.com>
Cc: gregkh@linuxfoundation.org, andy@kernel.org,
outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: fbtft: fb_upd161704: Replace udelay() with usleep_range()
Date: Sun, 25 Oct 2026 10:29:20 -0400 (EDT) [thread overview]
Message-ID: <7f65e825-b6eb-e7b-6bfc-a7549140c49c@inria.fr> (raw)
In-Reply-To: <CAHxSwT_bdBdiwwXpGpr9+rGizZU3p+RsB18hPH5TxqMuMZOsQw@mail.gmail.com>
On Sun, 25 Oct 2026, Abubakar Musa Samaila wrote:
> Replace udelay() calls inside the init_display() initialization
> sequence with usleep_range() to avoid CPU busy-waiting. Since
> init_display() runs in a non-atomic context, sleeping allows the CPU
> to yield, improving power efficiency and system responsiveness.
The patch fails when I try to apply it to the staging-next tree.
julia
>
> Signed-off-by: Abubakar Musa Samaila <abubakarmusasamaila@gmail.com>
> ---
> v3:
> - Remove raw git headers from the email body per maintainer feedback.
> - Add a descriptive commit message body explaining the rationale for
> usleep_range().
>
> v2:
> - Send patch inline in the email body rather than as an attachment.
> - No functional changes to the code diff itself.
>
> v1:
> drivers/staging/fbtft/fb_upd161704.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/staging/fbtft/fb_upd161704.c
> b/drivers/staging/fbtft/fb_upd161704.c
> index 7288140e7..94ae5bbf0 100644
> --- a/drivers/staging/fbtft/fb_upd161704.c
> +++ b/drivers/staging/fbtft/fb_upd161704.c
> @@ -32,27 +32,27 @@ static int init_display(struct fbtft_par *par)
>
> /* oscillator start */
> write_reg(par, 0x003A, 0x0001); /*Oscillator 0: stop, 1: operation */
> - udelay(100);
> + usleep_range(100, 150);
>
> /* y-setting */
> write_reg(par, 0x0024, 0x007B); /* amplitude setting */
> - udelay(10);
> + usleep_range(10, 20);
> write_reg(par, 0x0025, 0x003B); /* amplitude setting */
> write_reg(par, 0x0026, 0x0034); /* amplitude setting */
> - udelay(10);
> + usleep_range(10, 20);
> write_reg(par, 0x0027, 0x0004); /* amplitude setting */
> write_reg(par, 0x0052, 0x0025); /* circuit setting 1 */
> - udelay(10);
> + usleep_range(10, 20);
> write_reg(par, 0x0053, 0x0033); /* circuit setting 2 */
> write_reg(par, 0x0061, 0x001C); /* adjustment V10 positive polarity */
> - udelay(10);
> + usleep_range(10, 20);
> write_reg(par, 0x0062, 0x002C); /* adjustment V9 negative polarity */
> write_reg(par, 0x0063, 0x0022); /* adjustment V34 positive polarity */
> - udelay(10);
> + usleep_range(10, 20);
> write_reg(par, 0x0064, 0x0027); /* adjustment V31 negative polarity */
> - udelay(10);
> + usleep_range(10, 20);
> write_reg(par, 0x0065, 0x0014); /* adjustment V61 negative polarity */
> - udelay(10);
> + usleep_range(10, 20);
> write_reg(par, 0x0066, 0x0010); /* adjustment V61 negative polarity */
>
> /* Basical clock for 1 line (BASECOUNT[7:0]) number specified */
> @@ -60,7 +60,7 @@ static int init_display(struct fbtft_par *par)
>
> /* Power supply setting */
> write_reg(par, 0x0019, 0x0000); /* DC/DC output setting */
> - udelay(200);
> + usleep_range(200, 250);
> write_reg(par, 0x001A, 0x1000); /* DC/DC frequency setting */
> write_reg(par, 0x001B, 0x0023); /* DC/DC rising setting */
> write_reg(par, 0x001C, 0x0C01); /* Regulator voltage setting */
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-10-25 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 14:22 Abubakar Musa Samaila
2026-10-25 14:29 ` Julia Lawall [this message]
2026-10-25 15:04 ` Andy Shevchenko
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=7f65e825-b6eb-e7b-6bfc-a7549140c49c@inria.fr \
--to=julia.lawall@inria.fr \
--cc=abubakarmusasamaila@gmail.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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 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®