Lines Matching +full:suspend +full:- +full:mode
15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
21 See Documentation/admin-guide/pm/sleep-states.rst for more
28 The /sys/power/mem_sleep file controls the operating mode of
29 system suspend. Reading from it returns the available modes
31 supported). The mode that will be used on subsequent attempts
32 to suspend the system (by writing "mem" to the /sys/power/state
35 Writing one of the above strings to this file causes the mode
36 represented by it to be used on subsequent attempts to suspend
39 See Documentation/admin-guide/pm/sleep-states.rst for more
46 The /sys/power/disk file controls the operating mode of the
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
53 firmware will handle the system suspend.
55 'platform' - the memory image will be saved by the kernel and
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
73 memory, suspend devices, wait for 5 seconds, resume devices,
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
101 impossible, the kernel will try to suspend anyway using the
103 this file, the suspend image will be as small as possible.
114 debug a machine that just hangs during suspend (or more
120 To use this debugging feature you should attempt to suspend
123 dmesg -s 1000000 | grep 'hash matches'
131 CAUTION: Using it will cause your machine's real-time (CMOS)
162 user space to enable or disable asynchronous suspend and resume
164 drivers' suspend and resume callbacks to be executed in parallel
165 with each other and with the main suspend thread. It is enabled
192 be written a string representing a non-negative integer that
264 control whether the time taken by devices to suspend and
266 devices that take too long to suspend or resume.
279 kernel during the most recent system suspend/resume cycle.
289 of debug messages from the system suspend/hiberbation
314 The /sys/power/suspend_stats directory contains suspend related
343 number of times preparing all non-sysdev devices for
352 non-sysdev devices failed.
375 the number of times executing "suspend" callbacks
376 of all non-sysdev devices failed.
383 the number of times executing "late suspend" callbacks
391 the number of times executing "noirq suspend" callbacks
399 the last device for which a suspend/resume callback failed.
414 the last failed step in the suspend/resume path.
421 filesystems during system suspend (after freezing user space
426 The default is "1" if the build-time "SUSPEND_SKIP_SYNC" config