On 10-10-17, 09:57, Jesper Nilsson wrote: > On Fri, Aug 16, 2013 at 04:25:04AM +0200, 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. > > > > Acked-by: Jesper Nilsson <jesper.nilsson@xxxxxxxx> Wow.. You just Acked a 4 years old patch :) -- viresh -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
