From: Jean Pihet
Implement the per-device PM QoS constraints by creating a device
PM QoS API, which calls the PM QoS constraints management core code.
The per-device latency constraints data strctures are stored
in the device dev_pm_info struct.
The device PM code calls the init and destroy of
From: Jean Pihet
Implement the per-device PM QoS constraints by creating a device
PM QoS API, which calls the PM QoS constraints management core code.
The per-device latency constraints data strctures are stored
in the device dev_pm_info struct.
The device PM code calls the init and destroy of
On Thu, Aug 11, 2011 at 05:06:43PM +0200, jean.pi...@newoldbits.com wrote:
> From: Jean Pihet
>
> Implement the per-device PM QoS constraints by creating a device
> PM QoS API, which calls the PM QoS constraints management core code.
>
> The per-device latency constraints data strctures are stor
Hi,
Well, it looks like I should have reviewed this one more carefully.
On Thursday, August 11, 2011, jean.pi...@newoldbits.com wrote:
> From: Jean Pihet
>
> Implement the per-device PM QoS constraints by creating a device
> PM QoS API, which calls the PM QoS constraints management core code.
>
Rafael,
2011/8/13 Rafael J. Wysocki :
> Hi,
>
> Well, it looks like I should have reviewed this one more carefully.
>
> On Thursday, August 11, 2011, jean.pi...@newoldbits.com wrote:
>> From: Jean Pihet
>>
>> Implement the per-device PM QoS constraints by creating a device
>> PM QoS API, which ca
Hi,
On Sunday, August 14, 2011, Jean Pihet wrote:
...
> >> +
> >> + if (dev_pm_qos_request_active(req)) {
> >> + WARN(1, KERN_ERR "dev_pm_qos_add_request() called for
> >> already "
> >> + "added request\n");
> >> + return;
> >> + }
> >> + r
Hi,
On Tuesday, August 16, 2011, jean.pi...@newoldbits.com wrote:
> From: Jean Pihet
>
> Implement the per-device PM QoS constraints by creating a device
> PM QoS API, which calls the PM QoS constraints management core code.
>
> The per-device latency constraints data strctures are stored
> in
