[PATCH] regulator: pwm: Fix regulator ramp delay for continuous mode
broonie at kernel.org
Tue Jun 28 12:53:37 PDT 2016
On Tue, Jun 28, 2016 at 12:31:19PM -0700, Doug Anderson wrote:
> In all seriousness, I think the design for usleep_range() is to try to
> batch up wakeups to allow longer periods of sleeping and to optimize
> power. This you want to sleep as long as is allowable and then if you
> happen to wakeup for some other reason anyway then you process all the
> things whose minimum has passed. IIRC it was trying to get back to
> the good old days of only having jiffies where everyone was
> synchronized on the tick and you could sleep till the next tick after
> all the work was done. When you think of it this way then sleeping to
> the max makes sense. ...but it also means that you need to be careful
> and really not set the max too high.
That's what I *thought* it was doing, but when I looked at the
implementation down to the hrtimer level it was explicitly saying it was
actively trying to deliver the maximum delay but might do less. I'd
have expected that the implementation would check to see if there was a
wakeup scheduled in the range, piggybacking on the first one if so, and
if there was nothing it'd go for the minimum (perhaps with a bit of
rounding). Oh well.
> Of course, in practice I've found that often usleep_range() 99% of the
> time sleeps for the max. That can lead to some very subtle bugs if
> your min sleep is not long enough (!).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 473 bytes
Desc: not available
More information about the Linux-rockchip