On Fri, Sep 13, 2013 at 06:32:32PM +0530, Viresh Kumar wrote: > 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_transition(policy, &freqs, CPUFREQ_POSTCHANGE); > > This is replicated over all cpufreq drivers today and there doesn't exists a > good enough reason why this shouldn't be moved to cpufreq core instead. > > Earlier patches have added support in cpufreq core to do cpufreq notification > on > frequency change, this one removes it from this driver. > > Some related minor cleanups are also done along with it. > > Cc: Russell King <li...@arm.linux.org.uk> > Signed-off-by: Viresh Kumar <viresh.ku...@linaro.org>
Shouldn't this patch set CPUFREQ_ASYNC_NOTIFICATION somewhere? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
