On 21 August 2014 10:36, Shilpasri G Bhat <[email protected]> wrote: > The intention here is stop the cpufreq governor and then to set the cpus to > nominal frequency so as to ensure that the frequency won't be changed later. > > The .suspend callback of the driver is not called during reboot/kexec. > So we need an explicit reboot notifier to call cpufreq-suspend() to > suffice the requirement.
Hi Shilpa, No, we can't allow any platform driver to misuse cpufreq_suspend(). Platform drivers aren't *allowed* to call this routine. Now the deal is how do we move to nominal frequency on reboot.. @Rafael: Any suggestions? How do we ensure that governors are stopped on these notifiers, or if there is some other solution here? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
