On Tue, Sep 17, 2013 at 06:05:27PM +0200, Daniel Vetter wrote:
> On Tue, Sep 17, 2013 at 12:12 AM, Daniel Vetter wrote:
> > On Mon, Sep 16, 2013 at 02:56:43PM -0700, Tom.O'rou...@intel.com wrote:
> >> From: Tom O'Rourke
> >>
> >> Enabling rps (turbo setup) was put in a work queue because it may
>
On Tue, Sep 17, 2013 at 12:12 AM, Daniel Vetter wrote:
> On Mon, Sep 16, 2013 at 02:56:43PM -0700, Tom.O'rou...@intel.com wrote:
>> From: Tom O'Rourke
>>
>> Enabling rps (turbo setup) was put in a work queue because it may
>> take quite awhile. This change flushes the work queue to initialize
>>
On Mon, Sep 16, 2013 at 02:56:43PM -0700, Tom.O'rou...@intel.com wrote:
> From: Tom O'Rourke
>
> Enabling rps (turbo setup) was put in a work queue because it may
> take quite awhile. This change flushes the work queue to initialize
> rps values before use by sysfs or debugfs. Specifically,
> r
From: Tom O'Rourke
Enabling rps (turbo setup) was put in a work queue because it may
take quite awhile. This change flushes the work queue to initialize
rps values before use by sysfs or debugfs. Specifically,
rps.delayed_resume_work is flushed before using rps.hw_max,
rps.max_delay, rps.min_de