Lines Matching +full:suspend +full:- +full:to +full:- +full:disk
6 provide a unified interface to the power management
15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
18 Writing one of the above strings to this file causes the system
19 to transition into the corresponding state, if available.
21 See Documentation/admin-guide/pm/sleep-states.rst for more
29 system suspend. Reading from it returns the available modes
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
42 What: /sys/power/disk
46 The /sys/power/disk file controls the operating mode of the
47 suspend-to-disk mechanism. Reading from this file returns
48 the name of the method by which the system will be put to
49 sleep on the next suspend. There are four methods supported:
50 'firmware' - means that the memory image will be saved to disk
52 firmware will handle the system suspend.
53 'platform' - the memory image will be saved by the kernel and
54 the system will be put to sleep by the platform driver (e.g.
56 'shutdown' - the memory image will be saved by the kernel and
58 'reboot' - the memory image will be saved by the kernel and
61 Additionally, /sys/power/disk can be used to turn on one of the
62 two testing modes of the suspend-to-disk mechanism: 'testproc'
63 or 'test'. If the suspend-to-disk mechanism is in the
64 'testproc' mode, writing 'disk' to /sys/power/state will cause
65 the kernel to disable nonboot CPUs and freeze tasks, wait for 5
67 the 'test' mode, writing 'disk' to /sys/power/state will cause
68 the kernel to disable nonboot CPUs and freeze tasks, shrink
69 memory, suspend devices, wait for 5 seconds, resume devices,
70 unfreeze tasks and enable nonboot CPUs. Then, we are able to
74 The suspend-to-disk method may be chosen by writing to this
84 It will only change to 'firmware' or 'platform' if the system
92 created by the suspend-to-disk mechanism. It can be written a
93 string representing a non-negative integer that will be used
95 suspend-to-disk code will do its best to ensure the image size
96 will not exceed this number. However, if it turns out to be
97 impossible, the kernel will try to suspend anyway using the
98 smallest image possible. In particular, if "0" is written to
99 this file, the suspend image will be as small as possible.
102 limit, which is set to 500 MB by default.
110 debug a machine that just hangs during suspend (or more
111 commonly, during resume). Namely, the RTC is only used to save
113 it contains '0' which may be changed to '1' by writing a
116 To use this debugging feature you should attempt to suspend
119 dmesg -s 1000000 | grep 'hash matches'
121 If you do not get any matches (or they appear to be false
123 referred to a device created by a loadable kernel module. In
127 CAUTION: Using it will cause your machine's real-time (CMOS)
128 clock to be set to a random invalid time after a resume.
142 The advantage of this file over the hash matches printed to the
146 Due to the small hash size necessary to fit in the RTC, it is
148 case further investigation is required to determine which
158 user space to enable or disable asynchronous suspend and resume
160 drivers' suspend and resume callbacks to be executed in parallel
161 with each other and with the main suspend thread. It is enabled
163 disabled by writing "0" to this file, in which case all devices
170 The /sys/power/wakeup_count file allows user space to put the
175 read from. Writing to it will only succeed if the current
176 number of wakeup events is equal to the written value and, if
178 to a sleep state if any wakeup events are reported after the
185 The /sys/power/reserved_size file allows user space to control
188 be written a string representing a non-negative integer that
189 will be used as the amount of memory to reserve for allocations
193 set to 1 MB by default.
201 work item attempting to trigger a transition of the system to
205 of whether or not the attempt to put the system to sleep has
207 writes "off" to /sys/power/autosleep.
210 written to it to be returned.
216 The /sys/power/wake_lock file allows user space to create
220 string without white space is written to /sys/power/wake_lock,
221 it will be assumed to represent a wakeup source name. If there
225 If a string written to /sys/power/wake_lock contains white
243 The /sys/power/wake_unlock file allows user space to deactivate
245 When a string is written to /sys/power/wake_unlock, it will be
246 assumed to represent the name of a wakeup source to deactivate.
258 The /sys/power/pm_print_times file allows user space to
259 control whether the time taken by devices to suspend and
261 devices that take too long to suspend or resume.
271 The /sys/power/pm_wakeup_irq file reports to user space the IRQ
274 kernel during the most recent system suspend/resume cycle.
284 of debug messages from the system suspend/hiberbation
285 infrastructure to the kernel log.
287 Writing a "1" to this file enables the debug messages and
288 writing a "0" (default) to it disables them. Reads from
295 This file is used for telling the kernel an offset into a disk
296 to use when hibernating the system such as with a swap file.
303 set using the kernel command line for disk offset.