On 6 February 2013 07:36, Dirk Brandewie wrote:
> On 02/05/2013 05:47 PM, Viresh Kumar wrote:
>>
>> On Tue, Feb 5, 2013 at 11:54 PM, wrote:
>>>
>>> From: Dirk Brandewie
>>>
>>> Scaling drivers that implement cpufreq_driver.setpolicy() have
>>> internal governors and may/will change the current
On 02/05/2013 05:47 PM, Viresh Kumar wrote:
On Tue, Feb 5, 2013 at 11:54 PM, wrote:
From: Dirk Brandewie
Scaling drivers that implement cpufreq_driver.setpolicy() have
internal governors and may/will change the current operating frequency
very frequently this will cause cpufreq_out_of_sync()
On Tue, Feb 5, 2013 at 11:54 PM, wrote:
> From: Dirk Brandewie
>
> Scaling drivers that implement cpufreq_driver.setpolicy() have
> internal governors and may/will change the current operating frequency
> very frequently this will cause cpufreq_out_of_sync() to be called
> every time. Only call
From: Dirk Brandewie
Scaling drivers that implement cpufreq_driver.setpolicy() have
internal governors and may/will change the current operating frequency
very frequently this will cause cpufreq_out_of_sync() to be called
every time. Only call cpufreq_driver.get() for drivers that implement
cpufr
4 matches
Mail list logo