diff options
| author | Rafael J. Wysocki <rjw@sisk.pl> | 2011-03-23 22:16:32 +0100 |
|---|---|---|
| committer | Rafael J. Wysocki <rjw@sisk.pl> | 2011-03-23 22:16:32 +0100 |
| commit | e00e56dfd3cf1d209ce630a2b440c91e4a30bbd3 (patch) | |
| tree | 4d1329036e250db15411b21b15a158f9042945bd /virt | |
| parent | fb3600cc50302c9577b76838fcac1ee78828007d (diff) | |
| download | kernel_samsung_smdk4412-e00e56dfd3cf1d209ce630a2b440c91e4a30bbd3.zip kernel_samsung_smdk4412-e00e56dfd3cf1d209ce630a2b440c91e4a30bbd3.tar.gz kernel_samsung_smdk4412-e00e56dfd3cf1d209ce630a2b440c91e4a30bbd3.tar.bz2 | |
cpufreq: Use syscore_ops for boot CPU suspend/resume (v2)
The cpufreq subsystem uses sysdev suspend and resume for
executing cpufreq_suspend() and cpufreq_resume(), respectively,
during system suspend, after interrupts have been switched off on the
boot CPU, and during system resume, while interrupts are still off on
the boot CPU. In both cases the other CPUs are off-line at the
relevant point (either they have been switched off via CPU hotplug
during suspend, or they haven't been switched on yet during resume).
For this reason, although it may seem that cpufreq_suspend() and
cpufreq_resume() are executed for all CPUs in the system, they are
only called for the boot CPU in fact, which is quite confusing.
To remove the confusion and to prepare for elimiating sysdev
suspend and resume operations from the kernel enirely, convernt
cpufreq to using a struct syscore_ops object for the boot CPU
suspend and resume and rename the callbacks so that their names
reflect their purpose. In addition, put some explanatory remarks
into their kerneldoc comments.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions