On Fri, Oct 06, 2017 at 08:03:23AM +, Nicholas Mc Guire wrote:
> On Sun, Sep 24, 2017 at 12:18:12AM +, Levin, Alexander (Sasha Levin)
> wrote:
> > On Fri, Sep 22, 2017 at 09:46:28AM +0100, Charles Keepax wrote:
> > >On Wed, Sep 20, 2017 at 04:45:02AM +, Levin, Alexander (Sasha Levin)
On Sun, Sep 24, 2017 at 12:18:12AM +, Levin, Alexander (Sasha Levin) wrote:
> On Fri, Sep 22, 2017 at 09:46:28AM +0100, Charles Keepax wrote:
> >On Wed, Sep 20, 2017 at 04:45:02AM +, Levin, Alexander (Sasha Levin)
> >wrote:
> >> From: Nicholas Mc Guire
> >>
> >> [ Upstream commit ed784c53
On Fri, Sep 22, 2017 at 09:46:28AM +0100, Charles Keepax wrote:
>On Wed, Sep 20, 2017 at 04:45:02AM +, Levin, Alexander (Sasha Levin) wrote:
>> From: Nicholas Mc Guire
>>
>> [ Upstream commit ed784c532a3d0959db488f40a96c5127f63d42dc ]
>>
>> The delay here is not in atomic context and does not
On Wed, Sep 20, 2017 at 04:45:02AM +, Levin, Alexander (Sasha Levin) wrote:
> From: Nicholas Mc Guire
>
> [ Upstream commit ed784c532a3d0959db488f40a96c5127f63d42dc ]
>
> The delay here is not in atomic context and does not seem critical with
> respect to precision, but usleep_range(min,max)
From: Nicholas Mc Guire
[ Upstream commit ed784c532a3d0959db488f40a96c5127f63d42dc ]
The delay here is not in atomic context and does not seem critical with
respect to precision, but usleep_range(min,max) with min==max results in
giving the timer subsystem no room to optimize uncritical delays.
5 matches
Mail list logo