| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 5 System Suspend Code Flows
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
20 the target sleep state is referred to as *system suspend* too (in the majority
25 The kernel code flows associated with the suspend and resume transitions for
27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows
28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and
31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states
33 boils down to the platform-specific actions carried out by the suspend and
35 available. Apart from that, the suspend and resume code flows for these sleep
37 *platform-dependent suspend* states in what follows.
[all …]
|
| D | sleep-states.rst | 23 hibernation and up to three variants of system suspend. The sleep states that
28 Suspend-to-Idle
31 This is a generic, pure software, light-weight variant of system suspend (also
43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
44 deeper system suspend variants to provide reduced resume latency. It is always
58 I/O devices into low-power states, which is done for :ref:`suspend-to-idle
61 allow more energy to be saved relative to :ref:`suspend-to-idle <s2idle>`, but
65 reduced relative to :ref:`suspend-to-idle <s2idle>` and it may be necessary to
70 core system suspend subsystem. On ACPI-based systems this state is mapped to
75 Suspend-to-RAM
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | swsusp.rst | 2 Swap suspend
11 If you touch anything on disk between suspend and resume...
20 problems. If your disk driver does not support suspend... (IDE does),
22 between suspend and resume, it may do something wrong. If you change
26 ( ) suspend/resume support is needed to make it safe.
28 If you have any filesystems on USB devices mounted before software suspend,
43 After preparing then you suspend by::
51 - If you would like to write hibernation image to swap and then suspend
54 echo suspend > /sys/power/disk; echo disk > /sys/power/state
56 - If you have SATA disks, you'll need recent kernels with SATA suspend
[all …]
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | swsusp.txt | 5 * If you touch anything on disk between suspend and resume...
13 * problems. If your disk driver does not support suspend... (IDE does),
15 * between suspend and resume, it may do something wrong. If you change
19 * (*) suspend/resume support is needed to make it safe.
21 * If you have any filesystems on USB devices mounted before software suspend,
36 After preparing then you suspend by
44 . If you would like to write hibernation image to swap and then suspend
47 echo suspend > /sys/power/disk; echo disk > /sys/power/state
49 . If you have SATA disks, you'll need recent kernels with SATA suspend
50 support. For suspend and resume to work, make sure your disk drivers
[all …]
|
| D | 00-INDEX | 6 - Debugging suspend and resume
12 - Testing suspend and resume support in device drivers
14 - How processes and controlled during suspend
28 - How to get suspend to ram working (and debug it when it isn't)
31 suspend-and-cpuhotplug.txt
32 - Explains the interaction between Suspend-to-RAM (S3) and CPU hotplug
34 - Using swap files with software suspend (to disk)
36 - How to use dm-crypt and software suspend (to disk) together
38 - Goals, implementation, and usage of software suspend (ACPI S3)
40 - How to trick software suspend (to disk) into working when it isn't
[all …]
|
| D | interface.txt | 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
22 for Suspend-to-RAM and Power-On Suspend depends on the capabilities of the
30 /sys/power/disk controls the operating mode of hibernation (Suspend-to-Disk).
38 'suspend' (trigger a Suspend-to-RAM transition)
45 does that, for example). The 'suspend' option is available if Suspend-to-RAM
64 /sys/power/pm_trace controls the PM trace mechanism saving the last suspend
[all …]
|
| D | drivers-testing.txt | 1 Testing suspend and resume support in device drivers
6 Unfortunately, to effectively test the support for the system-wide suspend and
7 resume transitions in a driver, it is necessary to suspend and resume a fully
10 (aka suspend to disk or STD) and suspend to RAM (STR), because each of these
14 Of course, for this purpose the test system has to be known to suspend and
16 resolve all suspend/resume-related problems in the test system before you start
18 for more information about the debugging of suspend/resume functionality.
22 Once you have resolved the suspend/resume-related problems with your test system
37 e) Try the test modes of suspend (see: Documentation/power/basic-pm-debugging.txt,
41 f) Attempt to suspend to RAM using the s2ram tool with the driver loaded
[all …]
|
| /kernel/linux/linux-5.10/kernel/power/ |
| D | Kconfig | 2 config SUSPEND config
3 bool "Suspend to RAM and standby"
9 suspend-to-RAM state (e.g. the ACPI S3 state).
12 bool "Enable freezer for suspend to RAM/standby" \
14 depends on SUSPEND
17 This allows you to turn off the freezer for suspend. If this is
18 done, no tasks are frozen for suspend to RAM/standby.
23 bool "Skip kernel's sys_sync() on suspend to RAM/standby"
24 depends on SUSPEND
29 of suspend, or they are content with invoking sync() from
[all …]
|
| /kernel/linux/linux-4.19/kernel/power/ |
| D | Kconfig | 1 config SUSPEND config
2 bool "Suspend to RAM and standby"
8 suspend-to-RAM state (e.g. the ACPI S3 state).
11 bool "Enable freezer for suspend to RAM/standby" \
13 depends on SUSPEND
16 This allows you to turn off the freezer for suspend. If this is
17 done, no tasks are frozen for suspend to RAM/standby.
22 bool "Skip kernel's sys_sync() on suspend to RAM/standby"
23 depends on SUSPEND
28 of suspend, or they are content with invoking sync() from
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/boot/dts/ |
| D | rk3288-evb-rk808.dts | 46 regulator-off-in-suspend;
57 regulator-on-in-suspend;
58 regulator-suspend-microvolt = <1000000>;
67 regulator-on-in-suspend;
78 regulator-on-in-suspend;
79 regulator-suspend-microvolt = <3300000>;
90 regulator-on-in-suspend;
91 regulator-suspend-microvolt = <3300000>;
102 regulator-off-in-suspend;
113 regulator-on-in-suspend;
[all …]
|
| D | rk3288-fennec.dts | 109 regulator-off-in-suspend;
120 regulator-on-in-suspend;
121 regulator-suspend-microvolt = <1000000>;
130 regulator-on-in-suspend;
141 regulator-on-in-suspend;
142 regulator-suspend-microvolt = <3300000>;
153 regulator-on-in-suspend;
154 regulator-suspend-microvolt = <3300000>;
165 regulator-off-in-suspend;
176 regulator-on-in-suspend;
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | rk3288-evb-rk808.dts | 47 regulator-off-in-suspend;
58 regulator-on-in-suspend;
59 regulator-suspend-microvolt = <1000000>;
68 regulator-on-in-suspend;
79 regulator-on-in-suspend;
80 regulator-suspend-microvolt = <3300000>;
91 regulator-on-in-suspend;
92 regulator-suspend-microvolt = <3300000>;
103 regulator-off-in-suspend;
114 regulator-on-in-suspend;
[all …]
|
| D | rk3036-kylin.dts | 147 regulator-off-in-suspend;
158 regulator-on-in-suspend;
159 regulator-suspend-microvolt = <1000000>;
168 regulator-on-in-suspend;
179 regulator-on-in-suspend;
180 regulator-suspend-microvolt = <3300000>;
191 regulator-on-in-suspend;
192 regulator-suspend-microvolt = <3300000>;
203 regulator-off-in-suspend;
214 regulator-on-in-suspend;
[all …]
|
| D | at91-sama5d27_wlsom1.dtsi | 72 regulator-on-in-suspend;
77 regulator-off-in-suspend;
91 regulator-on-in-suspend;
92 regulator-suspend-microvolt = <1200000>;
93 regulator-changeable-in-suspend;
98 regulator-on-in-suspend;
99 regulator-suspend-microvolt = <1200000>;
100 regulator-changeable-in-suspend;
114 regulator-on-in-suspend;
119 regulator-off-in-suspend;
[all …]
|
| /kernel/linux/linux-4.19/tools/power/pm-graph/ |
| D | sleepgraph.8 | 3 sleepgraph \- Suspend/Resume timing analysis
11 in optimizing their linux stack's suspend/resume time. Using a kernel
13 suspend and capture dmesg and ftrace data until resume is complete.
16 taking the most time in suspend/resume.
19 a suspend/resume.
21 Generates output files in subdirectory: suspend-yymmdd-HHMMSS
40 Mode to initiate for suspend e.g. standby, freeze, mem (default: mem).
46 e.g. suspend-{hostname}-{date}-{time}
64 During test, enable/disable runtime suspend for all devices. The test is delayed
65 by 5 seconds to allow runtime suspend changes to occur. The settings are restored
[all …]
|
| /kernel/linux/linux-5.10/tools/power/pm-graph/ |
| D | sleepgraph.8 | 3 sleepgraph \- Suspend/Resume timing analysis
11 in optimizing their linux stack's suspend/resume time. Using a kernel
13 suspend and capture dmesg and ftrace data until resume is complete.
16 taking the most time in suspend/resume.
19 a suspend/resume.
21 Generates output files in subdirectory: suspend-yymmdd-HHMMSS
40 Mode to initiate for suspend e.g. standby, freeze, mem (default: mem).
46 e.g. suspend-{hostname}-{date}-{time}
58 will execute the suspend via turbostat and collect data in the timeline log.
69 During test, enable/disable runtime suspend for all devices. The test is delayed
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/regulator/ |
| D | regulator.txt | 36 - regulator-state-mem sub-root node for Suspend-to-RAM mode
37 : suspend to memory, the device goes to sleep, but all data stored in memory,
39 - regulator-state-disk sub-root node for Suspend-to-DISK mode
40 : suspend to disk, this state operates similarly to Suspend-to-RAM,
43 - regulator-on-in-suspend: regulator should be on in suspend state.
44 - regulator-off-in-suspend: regulator should be off in suspend state.
45 - regulator-suspend-min-microvolt: minimum voltage may be set in
46 suspend state.
47 - regulator-suspend-max-microvolt: maximum voltage may be set in
48 suspend state.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 19 hibernation and up to three variants of system suspend. The sleep states that
24 Suspend-to-Idle
27 This is a generic, pure software, light-weight variant of system suspend (also
39 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
40 deeper system suspend variants to provide reduced resume latency. It is always
54 I/O devices into low-power states, which is done for :ref:`suspend-to-idle
57 allow more energy to be saved relative to :ref:`suspend-to-idle <s2idle>`, but
61 reduced relative to :ref:`suspend-to-idle <s2idle>` and it may be necessary to
66 core system suspend subsystem. On ACPI-based systems this state is mapped to
71 Suspend-to-RAM
[all …]
|
| /kernel/linux/linux-4.19/drivers/net/wireless/ath/wil6210/ |
| D | pm.c | 63 /* for STA-like interface, don't runtime suspend */ in wil_can_suspend_vif()
67 wil_dbg_pm(wil, "Delay suspend when connecting\n"); in wil_can_suspend_vif()
75 /* AP-like interface - can't suspend */ in wil_can_suspend_vif()
94 wil_dbg_pm(wil, "Deny any suspend - %s mode\n", in wil_can_suspend()
99 if (is_runtime && !wil->platform_ops.suspend) { in wil_can_suspend()
114 wil_dbg_pm(wil, "Delay suspend when resetting\n"); in wil_can_suspend()
119 wil_dbg_pm(wil, "Delay suspend during recovery\n"); in wil_can_suspend()
195 wil_dbg_pm(wil, "suspend keep radio on\n"); in wil_suspend_keep_radio_on()
200 /* Device collects crash dump, cancel the suspend */ in wil_suspend_keep_radio_on()
201 wil_dbg_pm(wil, "reject suspend while collecting crash dump\n"); in wil_suspend_keep_radio_on()
[all …]
|
| /kernel/linux/linux-4.19/tools/power/pm-graph/config/ |
| D | example.cfg | 2 # Generic S3 (Suspend to Mem) test
20 # Suspend Mode
26 output-dir: suspend-{hostname}-{date}-{time}
36 # Suspend/Resume Gap
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
44 # Sync filesystem before suspend
48 # Runtime suspend enable/disable
49 # Enable/disable runtime suspend for all devices, restore all after test (default: no-action)
66 # Command to execute in lieu of suspend (default: "")
81 # Back to Back Suspend/Resume
[all …]
|
| D | suspend-dev.cfg | 2 # Dev S3 (Suspend to Mem) test - includes src calls / kernel threads
9 # sudo ./sleepgraph.py -config config/suspend-dev.cfg
20 # Suspend Mode
26 output-dir: suspend-{hostname}-{date}-{time}-dev
36 # Suspend/Resume Gap
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
42 # Command to execute in lieu of suspend (default: "")
53 # Back to Back Suspend/Resume
54 # Run two suspend/resumes back to back (default: false)
57 # Back to Back Suspend Delay
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/wireless/ath/wil6210/ |
| D | pm.c | 52 /* for STA-like interface, don't runtime suspend */ in wil_can_suspend_vif()
56 wil_dbg_pm(wil, "Delay suspend when connecting\n"); in wil_can_suspend_vif()
64 /* AP-like interface - can't suspend */ in wil_can_suspend_vif()
83 wil_dbg_pm(wil, "Deny any suspend - %s mode\n", in wil_can_suspend()
88 if (is_runtime && !wil->platform_ops.suspend) { in wil_can_suspend()
103 wil_dbg_pm(wil, "Delay suspend when resetting\n"); in wil_can_suspend()
108 wil_dbg_pm(wil, "Delay suspend during recovery\n"); in wil_can_suspend()
184 wil_dbg_pm(wil, "suspend keep radio on\n"); in wil_suspend_keep_radio_on()
202 wil_dbg_pm(wil, "Pending TX data, reject suspend\n"); in wil_suspend_keep_radio_on()
208 wil_dbg_pm(wil, "Pending RX data, reject suspend\n"); in wil_suspend_keep_radio_on()
[all …]
|
| /kernel/linux/linux-5.10/tools/power/pm-graph/config/ |
| D | suspend.cfg | 2 # Generic S3 (Suspend to Mem) test
9 # sudo ./sleepgraph.py -config config/suspend.cfg
20 # Suspend Mode
26 output-dir: suspend-{hostname}-{date}-{time}
36 # Suspend/Resume Gap
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
42 # Command to execute in lieu of suspend (default: "")
53 # Back to Back Suspend/Resume
54 # Run two suspend/resumes back to back (default: false)
57 # Back to Back Suspend Delay
[all …]
|
| D | suspend-x2-proc.cfg | 2 # Proc S3 (Suspend to Mem) x2 test - includes user processes
9 # sudo ./sleepgraph.py -config config/suspend-proc.cfg
20 # Suspend Mode
26 output-dir: suspend-{hostname}-{date}-{time}-x2-proc
36 # Suspend/Resume Gap
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
42 # Command to execute in lieu of suspend (default: "")
53 # Back to Back Suspend/Resume
54 # Run two suspend/resumes back to back (default: false)
57 # Back to Back Suspend Delay
[all …]
|
| D | suspend-dev.cfg | 2 # Dev S3 (Suspend to Mem) test - includes src calls / kernel threads
9 # sudo ./sleepgraph.py -config config/suspend-dev.cfg
20 # Suspend Mode
26 output-dir: suspend-{hostname}-{date}-{time}-dev
36 # Suspend/Resume Gap
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
42 # Command to execute in lieu of suspend (default: "")
53 # Back to Back Suspend/Resume
54 # Run two suspend/resumes back to back (default: false)
57 # Back to Back Suspend Delay
[all …]
|