|author||Zhang Rui <firstname.lastname@example.org>||2013-05-13 02:42:12 +0000|
|committer||Rafael J. Wysocki <email@example.com>||2013-05-14 01:46:50 +0200|
PM / Documentation: remove inaccurate suspend/hibernate transition lantency statement
The lantency of the transition from suspend and hibernate is platform-dependent. Thus we should not refer the lantency in the documentation. Signed-off-by: Zhang Rui <firstname.lastname@example.org> Signed-off-by: Rafael J. Wysocki <email@example.com>
Diffstat (limited to 'Documentation')
1 files changed, 0 insertions, 10 deletions
diff --git a/Documentation/power/states.txt b/Documentation/power/states.txt
index 42f28b7aaf6b..442d43df9b25 100644
@@ -36,9 +36,6 @@ We try to put devices in a low-power state equivalent to D1, which
also offers low power savings, but low resume latency. Not all devices
support D1, and those that don't are left on.
-A transition from Standby to the On state should take about 1-2
ACPI State: S3
@@ -56,9 +53,6 @@ transition back to the On state.
For at least ACPI, STR requires some minimal boot-strapping code to
resume the system from STR. This may be true on other platforms.
-A transition from Suspend-to-RAM to the On state should take about
ACPI State: S4
@@ -88,7 +82,3 @@ low-power state (like ACPI S4), or it may simply power down. Powering
down offers greater savings, and allows this mechanism to work on any
system. However, entering a real low-power state allows the user to
trigger wake up events (e.g. pressing a key or opening a laptop lid).
-A transition from Suspend-to-Disk to the On state should take about 30
-seconds, though it's typically a bit more with the current