Lines Matching +full:suspend +full:- +full:to +full:- +full:disk

14 'freeze' (Suspend-to-Idle)
15 'standby' (Power-On Suspend)
16 'mem' (Suspend-to-RAM)
17 'disk' (Suspend-to-Disk)
19 Suspend-to-Idle is always supported.  Suspend-to-Disk is always supported
20 too as long the kernel has been configured to support hibernation at all
22 for Suspend-to-RAM and Power-On Suspend depends on the capabilities of the
25 If one of the strings listed in /sys/power/state is written to it, the system
26 will attempt to transition into the corresponding sleep state.  Refer to
27 Documentation/admin-guide/pm/sleep-states.rst for a description of each of
30 /sys/power/disk controls the operating mode of hibernation (Suspend-to-Disk).
31 Specifically, it tells the kernel what to do after creating a hibernation image.
35 'platform' (put the system into sleep using a platform-provided method)
38 'suspend' (trigger a Suspend-to-RAM transition)
39 'test_resume' (resume-after-hibernation test mode)
44 mechanism to put the system to sleep after creating a hibernation image (ACPI
45 does that, for example).  The 'suspend' option is available if Suspend-to-RAM
46 is supported.  Refer to Documentation/power/basic-pm-debugging.txt for the
49 To select an option, write the string representing it to /sys/power/disk.
53 It can be written a string representing a non-negative integer that will be
54 used as a best-effort upper limit of the image size, in bytes.  The hibernation
55 core will do its best to ensure that the image size will not exceed that number.
56 However, if that turns out to be impossible to achieve, a hibernation image will
58 writing '0' to this file will enforce hibernation images to be as small as
61 Reading from this file returns the current image size limit, which is set to
64 /sys/power/pm_trace controls the PM trace mechanism saving the last suspend
67 It helps to debug hard lockups or reboots due to device driver failures that
68 occur during system suspend or resume (which is more common) more effectively.
70 If /sys/power/pm_trace contains '1', the fingerprint of each suspend/resume
73 storing it and it can be used later to identify the driver that caused the crash
74 to happen (see Documentation/power/s2ram.txt for more information).
76 Initially it contains '0' which may be changed to '1' by writing a string