All of lore.kernel.org
 help / color / mirror / Atom feed
From: WooYoung Jeon <chococookieman1@gmail.com>
To: Andy Shevchenko <andy@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	WooYoung Jeon <chococookieman1@gmail.com>
Subject: [PATCH] staging: fbtft: replace udelay with usleep_range
Date: Thu, 15 Jan 2026 17:40:19 +0900	[thread overview]
Message-ID: <20260115084019.28574-1-chococookieman1@gmail.com> (raw)

In the fb_ra8875 driver, udelay(100) is used for delay which
causes busy-waiting. Replacing it with usleep_range(100, 120)
allows the CPU to sleep during the delay, improving system
resource efficiency.

This change was suggested by checkpatch.pl.

Signed-off-by: WooYoung Jeon <chococookieman1@gmail.com>
---
 drivers/staging/fbtft/fb_ra8875.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/fbtft/fb_ra8875.c b/drivers/staging/fbtft/fb_ra8875.c
index 0ab1de664..92c9e4e03 100644
--- a/drivers/staging/fbtft/fb_ra8875.c
+++ b/drivers/staging/fbtft/fb_ra8875.c
@@ -210,7 +210,7 @@ static void write_reg8_bus8(struct fbtft_par *par, int len, ...)
 	}
 	len--;
 
-	udelay(100);
+	usleep_range(100, 120);
 
 	if (len) {
 		buf = (u8 *)par->buf;
-- 
2.43.0


             reply	other threads:[~2026-01-15  8:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15  8:40 WooYoung Jeon [this message]
2026-01-15  8:47 ` [PATCH] staging: fbtft: replace udelay with usleep_range Andy Shevchenko
2026-01-15  8:59 ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2022-07-09 10:06 Christos Kollintzas
2022-07-09 10:30 ` Greg KH
2022-07-09 10:30   ` Greg KH
2022-07-10 13:00   ` Christos Kollintzas
2022-07-10 13:00     ` Christos Kollintzas

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=20260115084019.28574-1-chococookieman1@gmail.com \
    --to=chococookieman1@gmail.com \
    --cc=andy@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@vger.kernel.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.