summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2022-07-21 18:13:30 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2022-07-26 20:53:00 +0200
commitec6c0503190417abf8b8f8e3e955ae583a4e50d4 (patch)
treee6dfd060c5dd3b0c5033dcf16af9d31d51e64b57 /Documentation
parent1a2dcab517cbf8f58ebf1e12aea253f5df9cff80 (diff)
downloadlinux-stable-ec6c0503190417abf8b8f8e3e955ae583a4e50d4.tar.gz
linux-stable-ec6c0503190417abf8b8f8e3e955ae583a4e50d4.tar.bz2
linux-stable-ec6c0503190417abf8b8f8e3e955ae583a4e50d4.zip
ACPI: PM: x86: Print messages regarding LPS0 idle support
Because suspend-to-idle is always supported and on x86 it is the only way to suspend the system if S3 is not supported by the platform, the kernel attempts to enter low-power S0 idle in the suspend-to-idle flow regardless of whether or not the ACPI_FADT_LOW_POWER_S0 flag is set in the FADT. However, if that flag is not set, residency counters associated with low-power S0 idle may not count and the platform may refuse to put the EC into a low-power mode, for example. For this reason, print diagnostic messages when the platform should achieve significant energy savings in low-power S0 idle (because the ACPI_FADT_LOW_POWER_S0 flag is set in the FADT) and when suspend-to-idle becomes the default suspend method (because low-power S0 idle should be equally or more efficient than S3, if available). Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions