On 18 November 2013 16:27, Lan Tianyu <tianyu.lan@xxxxxxxxx> wrote: > How about introducing a resume/suspend callback pointer or list(if there > are several places that need to deal with cpu resume/suspend) in the > struct cpu and populate it in the cpufreq_add_dev()? > > The suspend/resume() of cpu_subsys needs to check the callback pointer > and run it if available. That's almost a new infrastructure then and looks more hackish :) Apart from that even cpufreq would be a bit hacky as we don't really need per-cpu callbacks.. -- 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
