From: "Haris M. Bhatti" <kernel@techtum.dev>
To: gregkh@linuxfoundation.org
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
"Haris M. Bhatti" <kernel@techtum.dev>
Subject: [PATCH] drivers: staging: fbtft: Replace usage of udelay
Date: Thu, 15 Dec 2022 01:37:46 +0000 [thread overview]
Message-ID: <20221215013746.270404-1-kernel@techtum.dev> (raw)
checkpatch highlighted that use of udelay should be replaced by
usleep_range.
---
drivers/staging/fbtft/fb_ra8875.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fb_ra8875.c b/drivers/staging/fbtft/fb_ra8875.c
index 398bdbf53c9a..75cf3bb18414 100644
--- a/drivers/staging/fbtft/fb_ra8875.c
+++ b/drivers/staging/fbtft/fb_ra8875.c
@@ -217,7 +217,7 @@ static void write_reg8_bus8(struct fbtft_par *par, int len, ...)
}
len--;
- udelay(100);
+ usleep_range(100, 101);
if (len) {
buf = (u8 *)par->buf;
@@ -238,7 +238,7 @@ static void write_reg8_bus8(struct fbtft_par *par, int len, ...)
/* restore user spi-speed */
par->fbtftops.write = fbtft_write_spi;
- udelay(100);
+ usleep_range(100, 101);
}
static int write_vmem16_bus8(struct fbtft_par *par, size_t offset, size_t len)
--
2.38.1
WARNING: multiple messages have this Message-ID (diff)
From: "Haris M. Bhatti" <kernel@techtum.dev>
To: gregkh@linuxfoundation.org
Cc: "Haris M. Bhatti" <kernel@techtum.dev>,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH] drivers: staging: fbtft: Replace usage of udelay
Date: Thu, 15 Dec 2022 01:37:46 +0000 [thread overview]
Message-ID: <20221215013746.270404-1-kernel@techtum.dev> (raw)
checkpatch highlighted that use of udelay should be replaced by
usleep_range.
---
drivers/staging/fbtft/fb_ra8875.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/fbtft/fb_ra8875.c b/drivers/staging/fbtft/fb_ra8875.c
index 398bdbf53c9a..75cf3bb18414 100644
--- a/drivers/staging/fbtft/fb_ra8875.c
+++ b/drivers/staging/fbtft/fb_ra8875.c
@@ -217,7 +217,7 @@ static void write_reg8_bus8(struct fbtft_par *par, int len, ...)
}
len--;
- udelay(100);
+ usleep_range(100, 101);
if (len) {
buf = (u8 *)par->buf;
@@ -238,7 +238,7 @@ static void write_reg8_bus8(struct fbtft_par *par, int len, ...)
/* restore user spi-speed */
par->fbtftops.write = fbtft_write_spi;
- udelay(100);
+ usleep_range(100, 101);
}
static int write_vmem16_bus8(struct fbtft_par *par, size_t offset, size_t len)
--
2.38.1
next reply other threads:[~2022-12-15 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 1:37 Haris M. Bhatti [this message]
2022-12-15 1:37 ` [PATCH] drivers: staging: fbtft: Replace usage of udelay Haris M. Bhatti
2022-12-15 4:37 ` Greg KH
2022-12-15 4:37 ` 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=20221215013746.270404-1-kernel@techtum.dev \
--to=kernel@techtum.dev \
--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.