diff options
| author | Rafael J. Wysocki <rjw@sisk.pl> | 2010-09-24 16:46:14 -0400 |
|---|---|---|
| committer | Len Brown <len.brown@intel.com> | 2010-09-24 16:52:02 -0400 |
| commit | 539986482b0db07b7164ab086d167ab99b4d3061 (patch) | |
| tree | 56f1c78d70d50a88b0802528034a90d07d37a3ed /samples | |
| parent | 2422084a94fcd5038406261b331672a13c92c050 (diff) | |
| download | kernel_samsung_espresso10-539986482b0db07b7164ab086d167ab99b4d3061.zip kernel_samsung_espresso10-539986482b0db07b7164ab086d167ab99b4d3061.tar.gz kernel_samsung_espresso10-539986482b0db07b7164ab086d167ab99b4d3061.tar.bz2 | |
PM / ACPI: Blacklist systems known to require acpi_sleep=nonvs
Commit 2a6b69765ad794389f2fc3e14a0afa1a995221c2 (ACPI: Store NVS
state even when entering suspend to RAM) changed the ACPI suspend
to RAM code so that the NVS memory area is always unconditionally
saved during suspend and restored during resume, since some systems
evidently need that for the suspend-resume to work on them. However,
it turned out that this change broke suspend-resume on a few systems,
so commit 72ad5d77fb981963edae15eee8196c80238f5ed0 (ACPI / Sleep:
Allow the NVS saving to be skipped during suspend to RAM) introduced
the acpi_sleep=nonvs command line switch to allow their users to
work around this issue. To keep track of the systems that require
this workaround and to make the life of their users slightly easier
blacklist them in acpisleep_dmi_table[].
https://bugzilla.kernel.org/show_bug.cgi?id=16396
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions