Lines Matching +full:suspend +full:- +full:to +full:- +full:ram
16 - 'freeze' (Suspend-to-Idle)
17 - 'standby' (Power-On Suspend)
18 - 'mem' (Suspend-to-RAM)
19 - 'disk' (Suspend-to-Disk)
21 Suspend-to-Idle is always supported. Suspend-to-Disk is always supported
22 too as long the kernel has been configured to support hibernation at all
24 for Suspend-to-RAM and Power-On Suspend depends on the capabilities of the
27 If one of the strings listed in /sys/power/state is written to it, the system
28 will attempt to transition into the corresponding sleep state. Refer to
29 Documentation/admin-guide/pm/sleep-states.rst for a description of each of
32 /sys/power/disk controls the operating mode of hibernation (Suspend-to-Disk).
33 Specifically, it tells the kernel what to do after creating a hibernation image.
37 - 'platform' (put the system into sleep using a platform-provided method)
38 - 'shutdown' (shut the system down)
39 - 'reboot' (reboot the system)
40 - 'suspend' (trigger a Suspend-to-RAM transition)
41 - 'test_resume' (resume-after-hibernation test mode)
46 mechanism to put the system to sleep after creating a hibernation image (ACPI
47 does that, for example). The 'suspend' option is available if Suspend-to-RAM
48 is supported. Refer to Documentation/power/basic-pm-debugging.rst for the
51 To select an option, write the string representing it to /sys/power/disk.
55 It can be written a string representing a non-negative integer that will be
56 used as a best-effort upper limit of the image size, in bytes. The hibernation
57 core will do its best to ensure that the image size will not exceed that number.
58 However, if that turns out to be impossible to achieve, a hibernation image will
60 writing '0' to this file will enforce hibernation images to be as small as
63 Reading from this file returns the current image size limit, which is set to
64 around 2/5 of available RAM by default.
66 /sys/power/pm_trace controls the PM trace mechanism saving the last suspend
69 It helps to debug hard lockups or reboots due to device driver failures that
70 occur during system suspend or resume (which is more common) more effectively.
72 If /sys/power/pm_trace contains '1', the fingerprint of each suspend/resume
75 storing it and it can be used later to identify the driver that caused the crash
76 to happen (see Documentation/power/s2ram.rst for more information).
78 Initially it contains '0' which may be changed to '1' by writing a string