Lines Matching +full:sleep +full:- +full:hardware +full:- +full:state
9 What: /sys/power/state
13 The /sys/power/state file controls system sleep states.
14 Reading from this file returns the available sleep state
15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
19 to transition into the corresponding state, if available.
21 See Documentation/admin-guide/pm/sleep-states.rst for more
32 to suspend the system (by writing "mem" to the /sys/power/state
39 See Documentation/admin-guide/pm/sleep-states.rst for more
47 suspend-to-disk mechanism. Reading from this file returns
49 sleep on the next suspend. There are four methods supported:
51 'firmware' - means that the memory image will be saved to disk
55 'platform' - the memory image will be saved by the kernel and
56 the system will be put to sleep by the platform driver (e.g.
59 'shutdown' - the memory image will be saved by the kernel and
62 'reboot' - the memory image will be saved by the kernel and
66 two testing modes of the suspend-to-disk mechanism: 'testproc'
67 or 'test'. If the suspend-to-disk mechanism is in the
68 'testproc' mode, writing 'disk' to /sys/power/state will cause
71 the 'test' mode, writing 'disk' to /sys/power/state will cause
78 The suspend-to-disk method may be chosen by writing to this
81 - 'firmware'
82 - 'platform'
83 - 'shutdown'
84 - 'reboot'
85 - 'testproc'
86 - 'test'
96 created by the suspend-to-disk mechanism. It can be written a
97 string representing a non-negative integer that will be used
99 suspend-to-disk code will do its best to ensure the image size
123 dmesg -s 1000000 | grep 'hash matches'
131 CAUTION: Using it will cause your machine's real-time (CMOS)
175 system into a sleep state while taking into account the
182 to a sleep state if any wakeup events are reported after the
192 be written a string representing a non-negative integer that
204 returned by reads from /sys/power/state. If that happens, a
206 the sleep state represented by that string is queued up. This
209 of whether or not the attempt to put the system to sleep has
235 set regardless of the current state of the wakeup source object
322 of times entering system sleep state succeeded.
329 of times entering system sleep state failed.
343 number of times preparing all non-sysdev devices for
352 non-sysdev devices failed.
376 of all non-sysdev devices failed.
407 system sleep state.
421 contains the duration of time spent in a hardware sleep
422 state in the most recent system suspend-resume cycle.
430 contains the aggregate of time spent in a hardware sleep
431 state since the kernel was booted. This number
439 contains the maximum amount of time that the hardware can
440 report for time spent in a hardware sleep state. When sleep
455 The default is "1" if the build-time "SUSPEND_SKIP_SYNC" config