From: Christos Kollintzas <c.kollintzas.92@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: replace udelay with usleep_range
Date: Sun, 10 Jul 2022 16:00:19 +0300 [thread overview]
Message-ID: <YsrNY+uU8tUXJiPV@mandalorian.koija> (raw)
In-Reply-To: <YslY25NnW6O5Tn+p@kroah.com>
On Sat, Jul 09, 2022 at 12:30:51PM +0200, Greg KH wrote:
> On Sat, Jul 09, 2022 at 01:06:56PM +0300, Christos Kollintzas wrote:
> > Adhere to Linux kernel coding style.
> >
> > Reported by checkpatch:
> >
> > CHECK: usleep_range is preferred over udelay
> >
> > Signed-off-by: Christos Kollintzas <c.kollintzas.92@gmail.com>
> > ---
> > 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 c680160d6380..eeafbab4ace1 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, 110);
>
> When doing these types of changes, you really need access to the
> hardware involved in order to be able to properly test it.
>
> Especially for this type of function which is trying to do timing
> changes which the hardware requires.
>
> Did you test this on the real hardware and did it work properly?
>
> thanks,
>
> greg k-h
I did not.
I will try to find the hardware and send a patch that is
properly tested.
thanks,
Christos Kollintzas
next prev parent reply other threads:[~2022-07-10 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 10:06 [PATCH] staging: fbtft: replace udelay with usleep_range Christos Kollintzas
2022-07-09 10:30 ` Greg KH
2022-07-10 13:00 ` Christos Kollintzas [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-15 8:40 WooYoung Jeon
2026-01-15 8:47 ` Andy Shevchenko
2026-01-15 8:59 ` Greg Kroah-Hartman
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=YsrNY+uU8tUXJiPV@mandalorian.koija \
--to=c.kollintzas.92@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox