Lines Matching refs:to

4 The power management subsystem provides a unified sysfs interface to 
10 returns what states are supported, which is hard-coded to 'freeze',
11 'standby' (Power-On Suspend), 'mem' (Suspend-to-RAM), and 'disk'
12 (Suspend-to-Disk). 
14 Writing to this file one of those strings causes the system to
20 /sys/power/disk controls the operating mode of the suspend-to-disk
21 mechanism. Suspend-to-disk can be handled in several ways. We have a
22 few options for putting the system to sleep - using the platform driver
26 Additionally, /sys/power/disk can be used to turn on one of the two testing
27 modes of the suspend-to-disk mechanism: 'testproc' or 'test'.  If the
28 suspend-to-disk mechanism is in the 'testproc' mode, writing 'disk' to
29 /sys/power/state will cause the kernel to disable nonboot CPUs and freeze
31 in the 'test' mode, writing 'disk' to /sys/power/state will cause the kernel
32 to disable nonboot CPUs and freeze tasks, shrink memory, suspend devices, wait
34 we are able to look in the log messages and work out, for example, which code
42 Writing to this file will accept one of
51 the suspend-to-disk mechanism.  It can be written a string
53 limit of the image size, in bytes.  The suspend-to-disk mechanism will
54 do its best to ensure the image size will not exceed that number.  However,
55 if this turns out to be impossible, it will try to suspend anyway using the
56 smallest image possible.  In particular, if "0" is written to this file, the
60 is set to 2/5 of available RAM by default.
65 used to save the last PM event point if this file contains '1'.  Initially it
66 contains '0' which may be changed to '1' by writing a string representing a
69 To use this debugging feature you should attempt to suspend the machine, then
74 CAUTION: Using it will cause your machine's real-time (CMOS) clock to be
75 set to a random invalid time after a resume.