According to Documentation/timers/timers-howto.txt
udelay() is only called once from a place where sleeping is allowed.
We can replace it with a call to usleep_range()
with a reasonable upper limit.
Signed-off-by: Sunny Kumar sunny.kumar@gmail.com
---
drivers/usb/storage/transport.c | 2 +-
According to Documentation/timers/timers-howto.txt
udelay() is only called once from a place where sleeping is allowed.
We can replace it with a call to usleep_range()
with a reasonable upper limit.
Signed-off-by: Sunny Kumar sunny.kumar@gmail.com
---
drivers/usb/storage/transport.c | 2 +-
89648c1532e860b986fc5286245c404ddbe45b35 Mon Sep 17 00:00:00 2001
From: Sunny Kumar sunny.kumar@gmail.com
Date: Wed, 24 Jun 2015 19:50:30 +0530
Subject: [PATCH 1/1] usb: usleep_range is preferred over udelay where wakeup
is flexible
According to Documentation/timers/timers-howto.txt
udelay() is only called once from
On Wed, 24 Jun 2015, Sunny Kumar wrote:
According to Documentation/timers/timers-howto.txt
udelay() is only called once from a place where sleeping is allowed.
We can replace it with a call to usleep_range()
with a reasonable upper limit.
Signed-off-by: Sunny Kumar
Please don't top-post.
On Wed, 24 Jun 2015, Sunny Kumar wrote:
Ok so what about putting lower limit to 125 and increase upper limit 200
Or even just 150. That would be fine.
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to
62bc3514ec4da51e7e766199d00de0594b17d23b Mon Sep 17 00:00:00 2001
From: Sunny Kumar sunny.kumar@gmail.com
Date: Wed, 24 Jun 2015 21:07:18 +0530
Subject: [PATCH 1/1] usb: usleep_range is preferred over udelay where wakeup
is flexible
According to Documentation/timers/timers-howto.txt
udelay() is only called once from
