Re: [PATCH 3/7] cpufreq: Only query drivers that implement cpufreq_driver.target()

2013-02-05 Thread Viresh Kumar
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

Re: [PATCH 3/7] cpufreq: Only query drivers that implement cpufreq_driver.target()

2013-02-05 Thread Dirk Brandewie
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()

Re: [PATCH 3/7] cpufreq: Only query drivers that implement cpufreq_driver.target()

2013-02-05 Thread Viresh Kumar
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

[PATCH 3/7] cpufreq: Only query drivers that implement cpufreq_driver.target()

2013-02-05 Thread dirk . brandewie
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