On Sun, Nov 03, 2019 at 09:40:03AM -0600, Rama Kumar wrote: > > Hi, > > Changed udelay() to usleep_range() based on the document in the path, > "Documentation/timers/timers-howto.rst". It was suggested to use > usleep_range() function for sleeping duration between 10us - 20 ms. original > code used udelay() for sleeping 20 us. > > --- > drivers/staging/fbtft/fb_agm1264k-fl.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/fbtft/fb_agm1264k-fl.c > b/drivers/staging/fbtft/fb_agm1264k-fl.c > index eeeeec97ad27..471a145e3c00 100644 > --- a/drivers/staging/fbtft/fb_agm1264k-fl.c > +++ b/drivers/staging/fbtft/fb_agm1264k-fl.c > @@ -85,7 +85,7 @@ static void reset(struct fbtft_par *par) > dev_dbg(par->info->device, "%s()\n", __func__); > > gpiod_set_value(par->gpio.reset, 0); > - udelay(20); > + usleep_range(20,20); > gpiod_set_value(par->gpio.reset, 1); > mdelay(120); > } > -- > Signed-off-by: Rama Kumar <ramakumar.kanasund...@gmail.com>
Always run checkptch.pl on patches you send out so you don't get grumpy maintainers telling you to run checkpatch.pl on your patch :) thanks, greg k-h _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
