1 What: /sys/power/ 1 What: /sys/power/
2 Date: August 2006 2 Date: August 2006
3 Contact: Rafael J. Wysocki <rjw@rjwysock 3 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
4 Description: 4 Description:
5 The /sys/power directory will 5 The /sys/power directory will contain files that will
6 provide a unified interface to 6 provide a unified interface to the power management
7 subsystem. 7 subsystem.
8 8
9 What: /sys/power/state 9 What: /sys/power/state
10 Date: November 2016 10 Date: November 2016
11 Contact: Rafael J. Wysocki <rjw@rjwysock 11 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
12 Description: 12 Description:
13 The /sys/power/state file cont 13 The /sys/power/state file controls system sleep states.
14 Reading from this file returns 14 Reading from this file returns the available sleep state
15 labels, which may be "mem" (su 15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to 16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
17 17
18 Writing one of the above strin 18 Writing one of the above strings to this file causes the system
19 to transition into the corresp 19 to transition into the corresponding state, if available.
20 20
21 See Documentation/admin-guide/ !! 21 See Documentation/power/states.txt for more information.
22 information. <<
23 22
24 What: /sys/power/mem_sleep 23 What: /sys/power/mem_sleep
25 Date: November 2016 24 Date: November 2016
26 Contact: Rafael J. Wysocki <rjw@rjwysock 25 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
27 Description: 26 Description:
28 The /sys/power/mem_sleep file 27 The /sys/power/mem_sleep file controls the operating mode of
29 system suspend. Reading from 28 system suspend. Reading from it returns the available modes
30 as "s2idle" (always present), 29 as "s2idle" (always present), "shallow" and "deep" (present if
31 supported). The mode that wil 30 supported). The mode that will be used on subsequent attempts
32 to suspend the system (by writ 31 to suspend the system (by writing "mem" to the /sys/power/state
33 file described above) is enclo 32 file described above) is enclosed in square brackets.
34 33
35 Writing one of the above strin 34 Writing one of the above strings to this file causes the mode
36 represented by it to be used o 35 represented by it to be used on subsequent attempts to suspend
37 the system. 36 the system.
38 37
39 See Documentation/admin-guide/ !! 38 See Documentation/power/states.txt for more information.
40 information. <<
41 39
42 What: /sys/power/disk 40 What: /sys/power/disk
43 Date: September 2006 41 Date: September 2006
44 Contact: Rafael J. Wysocki <rjw@rjwysock 42 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
45 Description: 43 Description:
46 The /sys/power/disk file contr 44 The /sys/power/disk file controls the operating mode of the
47 suspend-to-disk mechanism. Re 45 suspend-to-disk mechanism. Reading from this file returns
48 the name of the method by whic 46 the name of the method by which the system will be put to
49 sleep on the next suspend. Th 47 sleep on the next suspend. There are four methods supported:
50 <<
51 'firmware' - means that the me 48 'firmware' - means that the memory image will be saved to disk
52 by some firmware, in which cas 49 by some firmware, in which case we also assume that the
53 firmware will handle the syste 50 firmware will handle the system suspend.
54 <<
55 'platform' - the memory image 51 'platform' - the memory image will be saved by the kernel and
56 the system will be put to slee 52 the system will be put to sleep by the platform driver (e.g.
57 ACPI or other PM registers). 53 ACPI or other PM registers).
58 <<
59 'shutdown' - the memory image 54 'shutdown' - the memory image will be saved by the kernel and
60 the system will be powered off 55 the system will be powered off.
61 <<
62 'reboot' - the memory image wi 56 'reboot' - the memory image will be saved by the kernel and
63 the system will be rebooted. 57 the system will be rebooted.
64 58
65 Additionally, /sys/power/disk 59 Additionally, /sys/power/disk can be used to turn on one of the
66 two testing modes of the suspe 60 two testing modes of the suspend-to-disk mechanism: 'testproc'
67 or 'test'. If the suspend-to- 61 or 'test'. If the suspend-to-disk mechanism is in the
68 'testproc' mode, writing 'disk 62 'testproc' mode, writing 'disk' to /sys/power/state will cause
69 the kernel to disable nonboot 63 the kernel to disable nonboot CPUs and freeze tasks, wait for 5
70 seconds, unfreeze tasks and en 64 seconds, unfreeze tasks and enable nonboot CPUs. If it is in
71 the 'test' mode, writing 'disk 65 the 'test' mode, writing 'disk' to /sys/power/state will cause
72 the kernel to disable nonboot 66 the kernel to disable nonboot CPUs and freeze tasks, shrink
73 memory, suspend devices, wait 67 memory, suspend devices, wait for 5 seconds, resume devices,
74 unfreeze tasks and enable nonb 68 unfreeze tasks and enable nonboot CPUs. Then, we are able to
75 look in the log messages and w 69 look in the log messages and work out, for example, which code
76 is being slow and which device 70 is being slow and which device drivers are misbehaving.
77 71
78 The suspend-to-disk method may 72 The suspend-to-disk method may be chosen by writing to this
79 file one of the accepted strin 73 file one of the accepted strings:
80 74
81 - 'firmware' !! 75 'firmware'
82 - 'platform' !! 76 'platform'
83 - 'shutdown' !! 77 'shutdown'
84 - 'reboot' !! 78 'reboot'
85 - 'testproc' !! 79 'testproc'
86 - 'test' !! 80 'test'
87 81
88 It will only change to 'firmwa 82 It will only change to 'firmware' or 'platform' if the system
89 supports that. 83 supports that.
90 84
91 What: /sys/power/image_size 85 What: /sys/power/image_size
92 Date: August 2006 86 Date: August 2006
93 Contact: Rafael J. Wysocki <rjw@rjwysock 87 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
94 Description: 88 Description:
95 The /sys/power/image_size file 89 The /sys/power/image_size file controls the size of the image
96 created by the suspend-to-disk 90 created by the suspend-to-disk mechanism. It can be written a
97 string representing a non-nega 91 string representing a non-negative integer that will be used
98 as an upper limit of the image 92 as an upper limit of the image size, in bytes. The kernel's
99 suspend-to-disk code will do i 93 suspend-to-disk code will do its best to ensure the image size
100 will not exceed this number. 94 will not exceed this number. However, if it turns out to be
101 impossible, the kernel will tr 95 impossible, the kernel will try to suspend anyway using the
102 smallest image possible. In p 96 smallest image possible. In particular, if "0" is written to
103 this file, the suspend image w 97 this file, the suspend image will be as small as possible.
104 98
105 Reading from this file will di 99 Reading from this file will display the current image size
106 limit, which is set to around !! 100 limit, which is set to 500 MB by default.
107 101
108 What: /sys/power/pm_trace 102 What: /sys/power/pm_trace
109 Date: August 2006 103 Date: August 2006
110 Contact: Rafael J. Wysocki <rjw@rjwysock 104 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
111 Description: 105 Description:
112 The /sys/power/pm_trace file c 106 The /sys/power/pm_trace file controls the code which saves the
113 last PM event point in the RTC 107 last PM event point in the RTC across reboots, so that you can
114 debug a machine that just hang 108 debug a machine that just hangs during suspend (or more
115 commonly, during resume). Nam 109 commonly, during resume). Namely, the RTC is only used to save
116 the last PM event point if thi 110 the last PM event point if this file contains '1'. Initially
117 it contains '0' which may be c 111 it contains '0' which may be changed to '1' by writing a
118 string representing a nonzero 112 string representing a nonzero integer into it.
119 113
120 To use this debugging feature 114 To use this debugging feature you should attempt to suspend
121 the machine, then reboot it an !! 115 the machine, then reboot it and run
122 116
123 dmesg -s 1000000 | grep 'has !! 117 dmesg -s 1000000 | grep 'hash matches'
124 118
125 If you do not get any matches 119 If you do not get any matches (or they appear to be false
126 positives), it is possible tha 120 positives), it is possible that the last PM event point
127 referred to a device created b 121 referred to a device created by a loadable kernel module. In
128 this case cat /sys/power/pm_tr 122 this case cat /sys/power/pm_trace_dev_match (see below) after
129 your system is started up and 123 your system is started up and the kernel modules are loaded.
130 124
131 CAUTION: Using it will cause y 125 CAUTION: Using it will cause your machine's real-time (CMOS)
132 clock to be set to a random in 126 clock to be set to a random invalid time after a resume.
133 127
134 What; /sys/power/pm_trace_dev_match 128 What; /sys/power/pm_trace_dev_match
135 Date: October 2010 129 Date: October 2010
136 Contact: James Hogan <jhogan@kernel.org> !! 130 Contact: James Hogan <james@albanarts.com>
137 Description: 131 Description:
138 The /sys/power/pm_trace_dev_ma 132 The /sys/power/pm_trace_dev_match file contains the name of the
139 device associated with the las 133 device associated with the last PM event point saved in the RTC
140 across reboots when pm_trace h 134 across reboots when pm_trace has been used. More precisely it
141 contains the list of current d 135 contains the list of current devices (including those
142 registered by loadable kernel 136 registered by loadable kernel modules since boot) which match
143 the device hash in the RTC at 137 the device hash in the RTC at boot, with a newline after each
144 one. 138 one.
145 139
146 The advantage of this file ove 140 The advantage of this file over the hash matches printed to the
147 kernel log (see /sys/power/pm_ 141 kernel log (see /sys/power/pm_trace), is that it includes
148 devices created after boot by 142 devices created after boot by loadable kernel modules.
149 143
150 Due to the small hash size nec 144 Due to the small hash size necessary to fit in the RTC, it is
151 possible that more than one de 145 possible that more than one device matches the hash, in which
152 case further investigation is 146 case further investigation is required to determine which
153 device is causing the problem. 147 device is causing the problem. Note that genuine RTC clock
154 values (such as when pm_trace 148 values (such as when pm_trace has not been used), can still
155 match a device and output its !! 149 match a device and output it's name here.
156 150
157 What: /sys/power/pm_async 151 What: /sys/power/pm_async
158 Date: January 2009 152 Date: January 2009
159 Contact: Rafael J. Wysocki <rjw@rjwysock 153 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
160 Description: 154 Description:
161 The /sys/power/pm_async file c 155 The /sys/power/pm_async file controls the switch allowing the
162 user space to enable or disabl 156 user space to enable or disable asynchronous suspend and resume
163 of devices. If enabled, this 157 of devices. If enabled, this feature will cause some device
164 drivers' suspend and resume ca 158 drivers' suspend and resume callbacks to be executed in parallel
165 with each other and with the m 159 with each other and with the main suspend thread. It is enabled
166 if this file contains "1", whi 160 if this file contains "1", which is the default. It may be
167 disabled by writing "0" to thi 161 disabled by writing "0" to this file, in which case all devices
168 will be suspended and resumed 162 will be suspended and resumed synchronously.
169 163
170 What: /sys/power/wakeup_count 164 What: /sys/power/wakeup_count
171 Date: July 2010 165 Date: July 2010
172 Contact: Rafael J. Wysocki <rjw@rjwysock 166 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
173 Description: 167 Description:
174 The /sys/power/wakeup_count fi 168 The /sys/power/wakeup_count file allows user space to put the
175 system into a sleep state whil 169 system into a sleep state while taking into account the
176 concurrent arrival of wakeup e 170 concurrent arrival of wakeup events. Reading from it returns
177 the current number of register 171 the current number of registered wakeup events and it blocks if
178 some wakeup events are being p 172 some wakeup events are being processed at the time the file is
179 read from. Writing to it will 173 read from. Writing to it will only succeed if the current
180 number of wakeup events is equ 174 number of wakeup events is equal to the written value and, if
181 successful, will make the kern 175 successful, will make the kernel abort a subsequent transition
182 to a sleep state if any wakeup 176 to a sleep state if any wakeup events are reported after the
183 write has returned. 177 write has returned.
184 178
185 What: /sys/power/reserved_size 179 What: /sys/power/reserved_size
186 Date: May 2011 180 Date: May 2011
187 Contact: Rafael J. Wysocki <rjw@rjwysock 181 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
188 Description: 182 Description:
189 The /sys/power/reserved_size f 183 The /sys/power/reserved_size file allows user space to control
190 the amount of memory reserved 184 the amount of memory reserved for allocations made by device
191 drivers during the "device fre 185 drivers during the "device freeze" stage of hibernation. It can
192 be written a string representi 186 be written a string representing a non-negative integer that
193 will be used as the amount of 187 will be used as the amount of memory to reserve for allocations
194 made by device drivers' "freez 188 made by device drivers' "freeze" callbacks, in bytes.
195 189
196 Reading from this file will di 190 Reading from this file will display the current value, which is
197 set to 1 MB by default. 191 set to 1 MB by default.
198 192
199 What: /sys/power/autosleep 193 What: /sys/power/autosleep
200 Date: April 2012 194 Date: April 2012
201 Contact: Rafael J. Wysocki <rjw@rjwysock 195 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
202 Description: 196 Description:
203 The /sys/power/autosleep file 197 The /sys/power/autosleep file can be written one of the strings
204 returned by reads from /sys/po 198 returned by reads from /sys/power/state. If that happens, a
205 work item attempting to trigge 199 work item attempting to trigger a transition of the system to
206 the sleep state represented by 200 the sleep state represented by that string is queued up. This
207 attempt will only succeed if t 201 attempt will only succeed if there are no active wakeup sources
208 in the system at that time. A 202 in the system at that time. After every execution, regardless
209 of whether or not the attempt 203 of whether or not the attempt to put the system to sleep has
210 succeeded, the work item reque 204 succeeded, the work item requeues itself until user space
211 writes "off" to /sys/power/aut 205 writes "off" to /sys/power/autosleep.
212 206
213 Reading from this file causes 207 Reading from this file causes the last string successfully
214 written to it to be returned. 208 written to it to be returned.
215 209
216 What: /sys/power/wake_lock 210 What: /sys/power/wake_lock
217 Date: February 2012 211 Date: February 2012
218 Contact: Rafael J. Wysocki <rjw@rjwysock 212 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
219 Description: 213 Description:
220 The /sys/power/wake_lock file 214 The /sys/power/wake_lock file allows user space to create
221 wakeup source objects and acti 215 wakeup source objects and activate them on demand (if one of
222 those wakeup sources is active 216 those wakeup sources is active, reads from the
223 /sys/power/wakeup_count file b 217 /sys/power/wakeup_count file block or return false). When a
224 string without white space is 218 string without white space is written to /sys/power/wake_lock,
225 it will be assumed to represen 219 it will be assumed to represent a wakeup source name. If there
226 is a wakeup source object with 220 is a wakeup source object with that name, it will be activated
227 (unless active already). Othe 221 (unless active already). Otherwise, a new wakeup source object
228 will be registered, assigned t 222 will be registered, assigned the given name and activated.
229 If a string written to /sys/po 223 If a string written to /sys/power/wake_lock contains white
230 space, the part of the string 224 space, the part of the string preceding the white space will be
231 regarded as a wakeup source na 225 regarded as a wakeup source name and handled as descrived above.
232 The other part of the string w 226 The other part of the string will be regarded as a timeout (in
233 nanoseconds) such that the wak 227 nanoseconds) such that the wakeup source will be automatically
234 deactivated after it has expir 228 deactivated after it has expired. The timeout, if present, is
235 set regardless of the current 229 set regardless of the current state of the wakeup source object
236 in question. 230 in question.
237 231
238 Reads from this file return a 232 Reads from this file return a string consisting of the names of
239 wakeup sources created with th 233 wakeup sources created with the help of it that are active at
240 the moment, separated with spa 234 the moment, separated with spaces.
241 235
242 236
243 What: /sys/power/wake_unlock 237 What: /sys/power/wake_unlock
244 Date: February 2012 238 Date: February 2012
245 Contact: Rafael J. Wysocki <rjw@rjwysock 239 Contact: Rafael J. Wysocki <rjw@rjwysocki.net>
246 Description: 240 Description:
247 The /sys/power/wake_unlock fil 241 The /sys/power/wake_unlock file allows user space to deactivate
248 wakeup sources created with th 242 wakeup sources created with the help of /sys/power/wake_lock.
249 When a string is written to /s 243 When a string is written to /sys/power/wake_unlock, it will be
250 assumed to represent the name 244 assumed to represent the name of a wakeup source to deactivate.
251 <<
252 If a wakeup source object of t 245 If a wakeup source object of that name exists and is active at
253 the moment, it will be deactiv 246 the moment, it will be deactivated.
254 247
255 Reads from this file return a 248 Reads from this file return a string consisting of the names of
256 wakeup sources created with th 249 wakeup sources created with the help of /sys/power/wake_lock
257 that are inactive at the momen 250 that are inactive at the moment, separated with spaces.
258 251
259 What: /sys/power/pm_print_times 252 What: /sys/power/pm_print_times
260 Date: May 2012 253 Date: May 2012
261 Contact: Sameer Nanda <snanda@chromium.o 254 Contact: Sameer Nanda <snanda@chromium.org>
262 Description: 255 Description:
263 The /sys/power/pm_print_times 256 The /sys/power/pm_print_times file allows user space to
264 control whether the time taken 257 control whether the time taken by devices to suspend and
265 resume is printed. These prin 258 resume is printed. These prints are useful for hunting down
266 devices that take too long to 259 devices that take too long to suspend or resume.
267 260
268 Writing a "1" enables this pri 261 Writing a "1" enables this printing while writing a "0"
269 disables it. The default valu 262 disables it. The default value is "0". Reading from this file
270 will display the current value 263 will display the current value.
271 264
272 What: /sys/power/pm_wakeup_irq 265 What: /sys/power/pm_wakeup_irq
273 Date: April 2015 266 Date: April 2015
274 Contact: Alexandra Yates <alexandra.yate 267 Contact: Alexandra Yates <alexandra.yates@linux.intel.org>
275 Description: 268 Description:
276 The /sys/power/pm_wakeup_irq f 269 The /sys/power/pm_wakeup_irq file reports to user space the IRQ
277 number of the first wakeup int 270 number of the first wakeup interrupt (that is, the first
278 interrupt from an IRQ line arm 271 interrupt from an IRQ line armed for system wakeup) seen by the
279 kernel during the most recent 272 kernel during the most recent system suspend/resume cycle.
280 273
281 This output is useful for syst 274 This output is useful for system wakeup diagnostics of spurious
282 wakeup interrupts. 275 wakeup interrupts.
283 <<
284 What: /sys/power/pm_debug_messages <<
285 Date: July 2017 <<
286 Contact: Rafael J. Wysocki <rjw@rjwysock <<
287 Description: <<
288 The /sys/power/pm_debug_messag <<
289 of debug messages from the sys <<
290 infrastructure to the kernel l <<
291 <<
292 Writing a "1" to this file ena <<
293 writing a "0" (default) to it <<
294 this file return the current v <<
295 <<
296 What: /sys/power/resume_offset <<
297 Date: April 2018 <<
298 Contact: Mario Limonciello <mario.limonc <<
299 Description: <<
300 This file is used for telling <<
301 to use when hibernating the sy <<
302 <<
303 Reads from this file will disp <<
304 the kernel will be using on th <<
305 attempt. <<
306 <<
307 Using this sysfs file will ove <<
308 set using the kernel command l <<
309 <<
310 What: /sys/power/suspend_stats <<
311 Date: July 2019 <<
312 Contact: Kalesh Singh <kaleshsingh96@gma <<
313 Description: <<
314 The /sys/power/suspend_stats d <<
315 statistics. <<
316 <<
317 What: /sys/power/suspend_stats/succe <<
318 Date: July 2019 <<
319 Contact: Kalesh Singh <kaleshsingh96@gma <<
320 Description: <<
321 The /sys/power/suspend_stats/s <<
322 of times entering system sleep <<
323 <<
324 What: /sys/power/suspend_stats/fail <<
325 Date: July 2019 <<
326 Contact: Kalesh Singh <kaleshsingh96@gma <<
327 Description: <<
328 The /sys/power/suspend_stats/f <<
329 of times entering system sleep <<
330 <<
331 What: /sys/power/suspend_stats/faile <<
332 Date: July 2019 <<
333 Contact: Kalesh Singh <kaleshsingh96@gma <<
334 Description: <<
335 The /sys/power/suspend_stats/f <<
336 number of times freezing proce <<
337 <<
338 What: /sys/power/suspend_stats/faile <<
339 Date: July 2019 <<
340 Contact: Kalesh Singh <kaleshsingh96@gma <<
341 Description: <<
342 The /sys/power/suspend_stats/f <<
343 number of times preparing all <<
344 a system PM transition failed. <<
345 <<
346 What: /sys/power/suspend_stats/faile <<
347 Date: July 2019 <<
348 Contact: Kalesh Singh <kaleshsingh96@gma <<
349 Description: <<
350 The /sys/power/suspend_stats/f <<
351 number of times executing "res <<
352 non-sysdev devices failed. <<
353 <<
354 What: /sys/power/suspend_stats/faile <<
355 Date: July 2019 <<
356 Contact: Kalesh Singh <kaleshsingh96@gma <<
357 Description: <<
358 The /sys/power/suspend_stats/f <<
359 the number of times executing <<
360 of devices failed. <<
361 <<
362 What: /sys/power/suspend_stats/faile <<
363 Date: July 2019 <<
364 Contact: Kalesh Singh <kaleshsingh96@gma <<
365 Description: <<
366 The /sys/power/suspend_stats/f <<
367 the number of times executing <<
368 of devices failed. <<
369 <<
370 What: /sys/power/suspend_stats/faile <<
371 Date: July 2019 <<
372 Contact: Kalesh Singh <kaleshsingh96@gma <<
373 Description: <<
374 The /sys/power/suspend_stats/f <<
375 the number of times executing <<
376 of all non-sysdev devices fail <<
377 <<
378 What: /sys/power/suspend_stats/faile <<
379 Date: July 2019 <<
380 Contact: Kalesh Singh <kaleshsingh96@gma <<
381 Description: <<
382 The /sys/power/suspend_stats/f <<
383 the number of times executing <<
384 of all devices failed. <<
385 <<
386 What: /sys/power/suspend_stats/faile <<
387 Date: July 2019 <<
388 Contact: Kalesh Singh <kaleshsingh96@gma <<
389 Description: <<
390 The /sys/power/suspend_stats/f <<
391 the number of times executing <<
392 of all devices failed. <<
393 <<
394 What: /sys/power/suspend_stats/last_ <<
395 Date: July 2019 <<
396 Contact: Kalesh Singh <kaleshsingh96@gma <<
397 Description: <<
398 The /sys/power/suspend_stats/l <<
399 the last device for which a su <<
400 <<
401 What: /sys/power/suspend_stats/last_ <<
402 Date: July 2019 <<
403 Contact: Kalesh Singh <kaleshsingh96@gma <<
404 Description: <<
405 The /sys/power/suspend_stats/l <<
406 the errno of the last failed a <<
407 system sleep state. <<
408 <<
409 What: /sys/power/suspend_stats/last_ <<
410 Date: July 2019 <<
411 Contact: Kalesh Singh <kaleshsingh96@gma <<
412 Description: <<
413 The /sys/power/suspend_stats/l <<
414 the last failed step in the su <<
415 <<
416 What: /sys/power/suspend_stats/last_ <<
417 Date: June 2023 <<
418 Contact: Mario Limonciello <mario.limonc <<
419 Description: <<
420 The /sys/power/suspend_stats/l <<
421 contains the duration of time <<
422 state in the most recent syste <<
423 This number is measured in mic <<
424 <<
425 What: /sys/power/suspend_stats/total <<
426 Date: June 2023 <<
427 Contact: Mario Limonciello <mario.limonc <<
428 Description: <<
429 The /sys/power/suspend_stats/t <<
430 contains the aggregate of time <<
431 state since the kernel was boo <<
432 is measured in microseconds. <<
433 <<
434 What: /sys/power/suspend_stats/max_h <<
435 Date: June 2023 <<
436 Contact: Mario Limonciello <mario.limonc <<
437 Description: <<
438 The /sys/power/suspend_stats/m <<
439 contains the maximum amount of <<
440 report for time spent in a har <<
441 cycles are longer than this ti <<
442 'total_hw_sleep' and 'last_hw_ <<
443 This number is measured in mic <<
444 <<
445 What: /sys/power/sync_on_suspend <<
446 Date: October 2019 <<
447 Contact: Jonas Meurer <jonas@freesources <<
448 Description: <<
449 This file controls whether or <<
450 filesystems during system susp <<
451 and before suspending devices) <<
452 <<
453 Writing a "1" to this file ena <<
454 disables it. Reads from the f <<
455 The default is "1" if the buil <<
456 flag is unset, or "0" otherwis <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.