On 13 September 2013 21:23, Russell King - ARM Linux
wrote:
> On Fri, Sep 13, 2013 at 06:32:07PM +0530, Viresh Kumar wrote:
>> + read_lock_irqsave(&cpufreq_driver_lock, flags);
>> + notify = !(cpufreq_driver->flags & CPUFREQ_ASYNC_NOTIFICATION);
>> + read_unlock
On Fri, Sep 13, 2013 at 06:32:07PM +0530, Viresh Kumar wrote:
> + read_lock_irqsave(&cpufreq_driver_lock, flags);
> + notify = !(cpufreq_driver->flags & CPUFREQ_ASYNC_NOTIFICATION);
> + read_unlock_irqrestore(&cpufreq_driver_lock, flags);
I don't think this need
Most of the drivers do following in their ->target_index() routines:
struct cpufreq_freqs freqs;
freqs.old = old freq...
freqs.new = new freq...
cpufreq_notify_transition(policy, &freqs, CPUFREQ_PRECHANGE);
/* Change rate here */
cpufreq_notify_tr
3 matches
Mail list logo