Re: [PATCH v2] PM / QoS: Fix device resume latency PM QoS

2017-10-26 Thread Rafael J. Wysocki
On Thu, Oct 26, 2017 at 4:00 AM, Ramesh Thomas wrote: > On 2017-10-25 at 00:16:25 -0700, Ramesh Thomas wrote: >> On 2017-10-24 at 13:35:05 +0200, Rafael J. Wysocki wrote: >> > From: Rafael J. Wysocki >> > >> >> [cut] >> >> > @@ -63,10 +60,14 @@ static bool default_suspend_ok(struct de >> > >> >

Re: [PATCH v2] PM / QoS: Fix device resume latency PM QoS

2017-10-25 Thread Ramesh Thomas
On 2017-10-25 at 00:16:25 -0700, Ramesh Thomas wrote: > On 2017-10-24 at 13:35:05 +0200, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > [cut] > > > @@ -63,10 +60,14 @@ static bool default_suspend_ok(struct de > > > > spin_unlock_irqrestore(&dev->power.lock, flags); > > > >

Re: [PATCH v2] PM / QoS: Fix device resume latency PM QoS

2017-10-25 Thread Ramesh Thomas
On 2017-10-24 at 13:35:05 +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > [cut] > @@ -63,10 +60,14 @@ static bool default_suspend_ok(struct de > > spin_unlock_irqrestore(&dev->power.lock, flags); > > - if (constraint_ns < 0) > + if (constraint_ns == 0) >

[PATCH v2] PM / QoS: Fix device resume latency PM QoS

2017-10-24 Thread Rafael J. Wysocki
From: Rafael J. Wysocki The special value of 0 for device resume latency PM QoS means "no restriction", but there are two problems with that. First, device resume latency PM QoS requests with 0 as the value are always put in front of requests with positive values in the priority lists used inter