[GIT PULL] Power management and ACPI fixes for 4.0-rc8
From: Rafael J. Wysocki
Date: Thu Apr 09 2015 - 19:10:00 EST
Please pull from
to receive power management and ACPI fixes for v4.0-rc8 (if
there's one) or for final v4.0 (if there isn't) with top-most
Merge branches 'pm-sleep', 'pm-cpufreq' and 'pm-cpuidle'
on top of commit f22e6e847115abc3a0e2ad7bb18d243d42275af1
These are stable-candidate fixes of some recently reported issues
in the cpufreq core, cpuidle core, the ACPI cpuidle driver and the
- Revert a 3.17 hibernate commit that was supposed to fix an issue
related to e820 reserved regions, but broke resume from hibernation
on Lenovo x230 (Rafael J Wysocki).
- Prevent the ACPI cpuidle driver from overwriting the name and
description of the C0 state set by the core when the list of
C-states changes (Thomas Schlichter).
- Remove the no longer needed state_count field from struct cpuidle_device
which prevents the list of C-states shown by the sysfs interface from
becoming incorrect when the current number of them is different from
the number of C-states on boot (Bartlomiej Zolnierkiewicz).
- The cpufreq core updates the policy object of the only online CPU
during system resume to make it reflect the current hardware state,
but it always assumes that CPU to be CPU0 which need not be the
case, so fix the code to avoid that assumption (Viresh Kumar).
Bartlomiej Zolnierkiewicz (1):
cpuidle: remove state_count field from struct cpuidle_device
Rafael J. Wysocki (1):
Revert "PM / hibernate: avoid unsafe pages in e820 reserved regions"
Thomas Schlichter (1):
cpuidle: ACPI: do not overwrite name and description of C0
Viresh Kumar (1):
cpufreq: Schedule work for the first-online CPU on resume
drivers/acpi/processor_idle.c | 2 +-
drivers/cpufreq/cpufreq.c | 19 +++++++++++--------
drivers/cpuidle/cpuidle.c | 3 ---
drivers/cpuidle/sysfs.c | 5 +++--
include/linux/cpuidle.h | 1 -
kernel/power/snapshot.c | 21 +--------------------
6 files changed, 16 insertions(+), 35 deletions(-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/