diff options
| author | Karel Zak | 2009-08-18 15:48:34 +0200 |
|---|---|---|
| committer | Karel Zak | 2009-09-07 12:04:26 +0200 |
| commit | 77f5744c982cd57b1bf1181f8f37023512236902 (patch) | |
| tree | 391e615804c7696d868180e4b3df0b1474e95459 /sys-utils/rtcwake.8 | |
| parent | mkswap: fix memory leaks, cleanup check_blocks() (diff) | |
| download | kernel-qcow2-util-linux-77f5744c982cd57b1bf1181f8f37023512236902.tar.gz kernel-qcow2-util-linux-77f5744c982cd57b1bf1181f8f37023512236902.tar.xz kernel-qcow2-util-linux-77f5744c982cd57b1bf1181f8f37023512236902.zip | |
rtcwake: add S5 support
Based on patch from
Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
at
https://bugzilla.redhat.com/show_bug.cgi?id=449115
Piergiorgio's note about S5:
> According to the ACPI specifications, chapter 4.7.2.4 "Real Time
> Clock Alarm", the wakeup from RTC, when supported, should work from
> *sleep* state S1-S3 and, optionally, from S4.
>
> Note 3 (same chapter) says that S5 is *not* a sleep state and should
> not be supported. Actually it also says that: "The OS will disable
> the RTC_EN bit prior to entering the G2/S5 or G3 states regardless."
>
> Nevertheless, on all PC supporting the RTC wakeup I tested, all were
> able to wake from S5.
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'sys-utils/rtcwake.8')
| -rw-r--r-- | sys-utils/rtcwake.8 | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/sys-utils/rtcwake.8 b/sys-utils/rtcwake.8 index f230e2056..999b67863 100644 --- a/sys-utils/rtcwake.8 +++ b/sys-utils/rtcwake.8 @@ -100,6 +100,10 @@ and can be used even in the absence of low-level platform support for power management. This state operates similarly to Suspend-to-RAM, but includes a final step of writing memory contents to disk. .TP +.B off +ACPI state S5 (Poweroff). This is done by calling '/sbin/shutdown'. +Not officially supported by ACPI, but usually working. +.TP .B no Don't suspend. The rtcwake command sets RTC wakeup time only. .TP |