| author | Vaibhav Bedia <vaibhav.bedia@ti.com> | |
| Mon, 12 Mar 2012 18:05:47 +0000 (23:35 +0530) | ||
| committer | Vaibhav Bedia <vaibhav.bedia@ti.com> | |
| Mon, 12 Mar 2012 18:05:47 +0000 (23:35 +0530) | ||
| commit | 3491cfa6f7f4ae06efaa8e3bc3b5d9063bf4b56c | |
| tree | d1691f62d4c97bac5618dbd062cc38887184ec88 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 95210de8c1b28314e4e948fc1d26a44ad9dbaf87 | commit | diff |
cpufreq: OMAP: Disable cpufreq during suspend
On AM335x, we need to reconfigure the PLLs and voltage
during suspend. With regulator calls in the suspend code
errors were reported by the cpufreq driver in the resume
path. This is probably because cpufreq is suspended
very late in the overall suspend process.
For now, we make use of SUSPEND_PREPARE notification
to block any further OPP changes from the driver.
Signed-off-by: Vaibhav Bedia <vaibhav.bedia@ti.com>
On AM335x, we need to reconfigure the PLLs and voltage
during suspend. With regulator calls in the suspend code
errors were reported by the cpufreq driver in the resume
path. This is probably because cpufreq is suspended
very late in the overall suspend process.
For now, we make use of SUSPEND_PREPARE notification
to block any further OPP changes from the driver.
Signed-off-by: Vaibhav Bedia <vaibhav.bedia@ti.com>
| arch/arm/mach-omap2/pm33xx.c | diff | blob | history | |
| drivers/cpufreq/omap-cpufreq.c | diff | blob | history |