summaryrefslogtreecommitdiffstats
path: root/drivers/cpufreq/db8500-cpufreq.c
diff options
context:
space:
mode:
authorMyungJoo Ham <myungjoo.ham@samsung.com>2011-08-18 19:45:16 +0900
committerDave Jones <davej@redhat.com>2011-10-26 17:19:46 -0400
commit0073f538c1c35f996982b583f5de7a6a43408b9b (patch)
tree035c9975f1d65d265ae4165f31b31325fe269dfd /drivers/cpufreq/db8500-cpufreq.c
parent8efd072b32d67436413e98e25e9a316216e88900 (diff)
[CPUFREQ] ARM Exynos4210 PM/Suspend compatibility with different bootloaders
We have various bootloaders for Exynos4210 machines. Some of they set the ARM core frequency at boot time even when the boot is a resume from suspend-to-RAM. Such changes may create inconsistency in the data of CPUFREQ driver and have incurred hang issues with suspend-to-RAM. This patch enables to save and restore CPU frequencies with pm-notifier and sets the frequency at the initial (boot-time) value so that there wouldn't be any inconsistency between bootloader and kernel. This patch does not use CPUFREQ's suspend/resume callbacks because they are syscore-ops, which do not allow to use mutex that is being used by regulators that are used by the target function. This also prevents any CPUFREQ transitions during suspend-resume context, which could be dangerous at noirq-context along with regulator framework. Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by: Dave Jones <davej@redhat.com>
Diffstat (limited to 'drivers/cpufreq/db8500-cpufreq.c')
0 files changed, 0 insertions, 0 deletions