Lines Matching refs:the
6 provide a unified interface to the power management
14 Reading from this file returns the available sleep state
16 (hibernation). The meanings of the first three labels depend on
17 the relative_sleep_states command line argument as follows:
20 states from the deepest ("mem", always present) to the
22 not be present depending on the capabilities of the
30 Writing to this file one of these strings causes the system to
31 transition into the corresponding state, if available. See
39 The /sys/power/disk file controls the operating mode of the
41 the name of the method by which the system will be put to
42 sleep on the next suspend. There are four methods supported:
43 'firmware' - means that the memory image will be saved to disk
44 by some firmware, in which case we also assume that the
45 firmware will handle the system suspend.
46 'platform' - the memory image will be saved by the kernel and
47 the system will be put to sleep by the platform driver (e.g.
49 'shutdown' - the memory image will be saved by the kernel and
50 the system will be powered off.
51 'reboot' - the memory image will be saved by the kernel and
52 the system will be rebooted.
54 Additionally, /sys/power/disk can be used to turn on one of the
55 two testing modes of the suspend-to-disk mechanism: 'testproc'
56 or 'test'. If the suspend-to-disk mechanism is in the
58 the kernel to disable nonboot CPUs and freeze tasks, wait for 5
60 the 'test' mode, writing 'disk' to /sys/power/state will cause
61 the kernel to disable nonboot CPUs and freeze tasks, shrink
64 look in the log messages and work out, for example, which code
68 file one of the accepted strings:
77 It will only change to 'firmware' or 'platform' if the system
84 The /sys/power/image_size file controls the size of the image
85 created by the suspend-to-disk mechanism. It can be written a
87 as an upper limit of the image size, in bytes. The kernel's
88 suspend-to-disk code will do its best to ensure the image size
90 impossible, the kernel will try to suspend anyway using the
92 this file, the suspend image will be as small as possible.
94 Reading from this file will display the current image size
101 The /sys/power/pm_trace file controls the code which saves the
102 last PM event point in the RTC across reboots, so that you can
104 commonly, during resume). Namely, the RTC is only used to save
105 the last PM event point if this file contains '1'. Initially
110 the machine, then reboot it and run
115 positives), it is possible that the last PM event point
118 your system is started up and the kernel modules are loaded.
127 The /sys/power/pm_trace_dev_match file contains the name of the
128 device associated with the last PM event point saved in the RTC
130 contains the list of current devices (including those
132 the device hash in the RTC at boot, with a newline after each
135 The advantage of this file over the hash matches printed to the
139 Due to the small hash size necessary to fit in the RTC, it is
140 possible that more than one device matches the hash, in which
142 device is causing the problem. Note that genuine RTC clock
150 The /sys/power/pm_async file controls the switch allowing the
154 with each other and with the main suspend thread. It is enabled
155 if this file contains "1", which is the default. It may be
163 The /sys/power/wakeup_count file allows user space to put the
164 system into a sleep state while taking into account the
166 the current number of registered wakeup events and it blocks if
167 some wakeup events are being processed at the time the file is
168 read from. Writing to it will only succeed if the current
169 number of wakeup events is equal to the written value and, if
170 successful, will make the kernel abort a subsequent transition
171 to a sleep state if any wakeup events are reported after the
179 the amount of memory reserved for allocations made by device
180 drivers during the "device freeze" stage of hibernation. It can
182 will be used as the amount of memory to reserve for allocations
185 Reading from this file will display the current value, which is
192 The /sys/power/autosleep file can be written one of the strings
194 work item attempting to trigger a transition of the system to
195 the sleep state represented by that string is queued up. This
197 in the system at that time. After every execution, regardless
198 of whether or not the attempt to put the system to sleep has
199 succeeded, the work item requeues itself until user space
202 Reading from this file causes the last string successfully
211 those wakeup sources is active, reads from the
217 will be registered, assigned the given name and activated.
219 space, the part of the string preceding the white space will be
221 The other part of the string will be regarded as a timeout (in
222 nanoseconds) such that the wakeup source will be automatically
224 set regardless of the current state of the wakeup source object
227 Reads from this file return a string consisting of the names of
228 wakeup sources created with the help of it that are active at
229 the moment, separated with spaces.
237 wakeup sources created with the help of /sys/power/wake_lock.
239 assumed to represent the name of a wakeup source to deactivate.
241 the moment, it will be deactivated.
243 Reads from this file return a string consisting of the names of
244 wakeup sources created with the help of /sys/power/wake_lock
245 that are inactive at the moment, separated with spaces.
252 control whether the time taken by devices to suspend and
258 will display the current value.