Searched +full:suspend +full:- +full:to +full:- +full:disk (Results 1 – 25 of 379) sorted by relevance
12345678910>>...16
| /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,
35 You need to append resume=/dev/your_swap_partition to kernel command
43 After preparing then you suspend by::
45 echo shutdown > /sys/power/disk; echo disk > /sys/power/state
47 - If you feel ACPI works pretty well on your system, you might try::
[all …]
|
| D | basic-pm-debugging.rst | 2 Debugging hibernation and suspend
7 1. Testing hibernation (aka suspend to disk or STD)
10 To check if hibernation works, you can try to hibernate in the "reboot" mode::
12 # echo reboot > /sys/power/disk
13 # echo disk > /sys/power/state
15 and the system should create a hibernation image, reboot, resume and get back to
17 hibernation is most likely to work correctly. Still, you need to repeat the
21 modes causes the PM core to skip some platform-related callbacks which on ACPI
22 systems might be necessary to make hibernation work. Thus, if your machine
23 fails to hibernate or resume in the "reboot" mode, you should try the
[all …]
|
| D | swsusp-dmcrypt.rst | 2 How to use dm-crypt and swsusp together
10 You know how dm-crypt works. If not, visit the following web page:
11 http://www.saout.de/misc/dm-crypt/
13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
14 You know how to create or how to modify an initrd.
16 Now your system is properly set up, your disk is encrypted except for
21 At this point you want to encrypt your swap, too. Still you want to
22 be able to suspend using swsusp. This, however, means that you
23 have to be able to either enter a passphrase or that you read
24 the key(s) from an external device like a pcmcia flash disk
[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,
28 You need to append resume=/dev/your_swap_partition to kernel command
36 After preparing then you suspend by
38 echo shutdown > /sys/power/disk; echo disk > /sys/power/state
42 echo platform > /sys/power/disk; echo disk > /sys/power/state
44 . If you would like to write hibernation image to swap and then suspend
[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
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
[all …]
|
| D | basic-pm-debugging.txt | 1 Debugging hibernation and suspend
4 1. Testing hibernation (aka suspend to disk or STD)
6 To check if hibernation works, you can try to hibernate in the "reboot" mode:
8 # echo reboot > /sys/power/disk
9 # echo disk > /sys/power/state
11 and the system should create a hibernation image, reboot, resume and get back to
13 hibernation is most likely to work correctly. Still, you need to repeat the
17 modes causes the PM core to skip some platform-related callbacks which on ACPI
18 systems might be necessary to make hibernation work. Thus, if your machine fails
19 to hibernate or resume in the "reboot" mode, you should try the "platform" mode:
[all …]
|
| D | 00-INDEX | 1 00-INDEX
2 - This file
3 apm-acpi.txt
4 - basic info about the APM and ACPI support.
5 basic-pm-debugging.txt
6 - Debugging suspend and resume
7 charger-manager.txt
8 - Battery charger management.
9 admin-guide/devices.rst
10 - How drivers interact with system-wide power management
[all …]
|
| D | swsusp-dmcrypt.txt | 4 How to use dm-crypt and swsusp together:
8 You know how dm-crypt works. If not, visit the following web page:
9 http://www.saout.de/misc/dm-crypt/
11 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
12 You know how to create or how to modify an initrd.
14 Now your system is properly set up, your disk is encrypted except for
19 At this point you want to encrypt your swap, too. Still you want to
20 be able to suspend using swsusp. This, however, means that you
21 have to be able to either enter a passphrase or that you read
22 the key(s) from an external device like a pcmcia flash disk
[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
17 testing the new driver. Please see Documentation/power/basic-pm-debugging.txt
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
23 without the new driver, you are ready to test it:
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-power | 6 provide a unified interface to the power management
15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
18 Writing one of the above strings to this file causes the system
19 to transition into the corresponding state, if available.
21 See Documentation/admin-guide/pm/sleep-states.rst for more
29 system suspend. Reading from it returns the available modes
32 to suspend the system (by writing "mem" to the /sys/power/state
35 Writing one of the above strings to this file causes the mode
36 represented by it to be used on subsequent attempts to suspend
[all …]
|
| D | sysfs-class-regulator | 17 power to the system (assuming no error prevents it).
20 supplying power to the system (unless some non-Linux
27 or microamps to determine configured regulator output levels.
46 "off" means the regulator is not supplying power to the
49 "on" means the regulator is supplying power to the system,
52 "error" indicates an out-of-regulation status such as being
53 disabled due to thermal shutdown, or voltage being unstable
61 not limited to control inputs from Linux. For example,
98 measured in microvolts (i.e. E-6 Volts), for regulators
101 NOTE: This value should not be used to determine the regulator
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-power | 6 provide a unified interface to the power management
15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
18 Writing one of the above strings to this file causes the system
19 to transition into the corresponding state, if available.
21 See Documentation/admin-guide/pm/sleep-states.rst for more
29 system suspend. Reading from it returns the available modes
32 to suspend the system (by writing "mem" to the /sys/power/state
35 Writing one of the above strings to this file causes the mode
36 represented by it to be used on subsequent attempts to suspend
[all …]
|
| D | sysfs-class-regulator | 17 power to the system (assuming no error prevents it).
20 supplying power to the system (unless some non-Linux
27 or microamps to determine configured regulator output levels.
38 - off
39 - on
40 - error
41 - fast
42 - normal
43 - idle
44 - standby
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/regulator/ |
| D | regulator.txt | 4 - regulator-name: A string used as a descriptive name for regulator outputs
5 - regulator-min-microvolt: smallest voltage consumers may set
6 - regulator-max-microvolt: largest voltage consumers may set
7 - regulator-microvolt-offset: Offset applied to voltages to compensate for voltage drops
8 - regulator-min-microamp: smallest current consumers may set
9 - regulator-max-microamp: largest current consumers may set
10 - regulator-input-current-limit-microamp: maximum input current regulator allows
11 - regulator-always-on: boolean, regulator should never be disabled
12 - regulator-boot-on: bootloader/firmware enabled regulator
13 - regulator-allow-bypass: allow the regulator to go into bypass mode
[all …]
|
| /kernel/linux/linux-4.19/kernel/power/ |
| D | Kconfig | 1 config SUSPEND config
2 bool "Suspend to RAM and standby"
5 ---help---
6 Allow the system to enter sleep states in which main memory is
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"
[all …]
|
| /kernel/linux/linux-5.10/kernel/power/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 config SUSPEND config
3 bool "Suspend to RAM and standby"
7 Allow the system to enter sleep states in which main memory is
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"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 Sleep states are global low-power states of the entire system in which user
22 the Linux kernel can support up to four system sleep states, including
23 hibernation and up to three variants of system suspend. The sleep states that
28 Suspend-to-Idle
29 ---------------
31 This is a generic, pure software, light-weight variant of system suspend (also
32 referred to as S2I or S2Idle). It allows more energy to be saved relative to
34 I/O devices into low-power states (possibly lower-power than available in the
38 The system is woken up from this state by in-band interrupts, so theoretically
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
14 regulator-name:
18 regulator-min-microvolt:
21 regulator-max-microvolt:
24 regulator-microvolt-offset:
25 description: Offset applied to voltages to compensate for voltage drops
[all …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 9 Sleep states are global low-power states of the entire system in which user
18 the Linux kernel can support up to four system sleep states, including
19 hibernation and up to three variants of system suspend. The sleep states that
24 Suspend-to-Idle
25 ---------------
27 This is a generic, pure software, light-weight variant of system suspend (also
28 referred to as S2I or S2Idle). It allows more energy to be saved relative to
30 I/O devices into low-power states (possibly lower-power than available in the
34 The system is woken up from this state by in-band interrupts, so theoretically
35 any devices that can cause interrupts to be generated in the working state can
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | suspend.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
100 * struct platform_suspend_ops - Callbacks for managing platform dependent
103 * @valid: Callback to determine if given system sleep state is supported by
106 * that it still may be impossible to enter given system sleep state if the
109 * assigned to this if the platform only supports mem sleep.
111 * @begin: Initialise a transition to given system sleep state.
112 * @begin() is executed right prior to suspending devices. The information
113 * conveyed to the platform code by @begin() should be disregarded by it as
117 * passed to @enter() is redundant and should be ignored.
122 * appropriate .suspend() method has been executed for each device) and
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | suspend.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
100 * struct platform_suspend_ops - Callbacks for managing platform dependent
103 * @valid: Callback to determine if given system sleep state is supported by
106 * that it still may be impossible to enter given system sleep state if the
109 * assigned to this if the platform only supports mem sleep.
111 * @begin: Initialise a transition to given system sleep state.
112 * @begin() is executed right prior to suspending devices. The information
113 * conveyed to the platform code by @begin() should be disregarded by it as
117 * passed to @enter() is redundant and should be ignored.
122 * appropriate .suspend() method has been executed for each device) and
[all …]
|
| /kernel/linux/linux-5.10/tools/power/pm-graph/config/ |
| D | suspend-x2-proc.cfg | 2 # Proc S3 (Suspend to Mem) x2 test - includes user processes
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/suspend-proc.cfg
14 # ---- General Options ----
20 # Suspend Mode
21 # e.g. standby, mem, freeze, disk (default: mem)
26 output-dir: suspend-{hostname}-{date}-{time}-x2-proc
29 # Use rtcwake to autoresume after X seconds, or off to disable (default: 15)
33 # add the dmesg and ftrace log to the html output (default: false)
36 # Suspend/Resume Gap
[all …]
|
| D | suspend-dev.cfg | 2 # Dev S3 (Suspend to Mem) test - includes src calls / kernel threads
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/suspend-dev.cfg
14 # ---- General Options ----
20 # Suspend Mode
21 # e.g. standby, mem, freeze, disk (default: mem)
26 output-dir: suspend-{hostname}-{date}-{time}-dev
29 # Use rtcwake to autoresume after X seconds, or off to disable (default: 15)
33 # add the dmesg and ftrace log to the html output (default: false)
36 # Suspend/Resume Gap
[all …]
|
| /kernel/linux/linux-4.19/tools/power/pm-graph/config/ |
| D | suspend-x2-proc.cfg | 2 # Proc S3 (Suspend to Mem) x2 test - includes user processes
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/suspend-proc.cfg
14 # ---- General Options ----
20 # Suspend Mode
21 # e.g. standby, mem, freeze, disk (default: mem)
26 output-dir: suspend-{hostname}-{date}-{time}-x2-proc
29 # Use rtcwake to autoresume after X seconds, or off to disable (default: 15)
33 # add the dmesg and ftrace log to the html output (default: false)
36 # Suspend/Resume Gap
[all …]
|
| D | suspend-dev.cfg | 2 # Dev S3 (Suspend to Mem) test - includes src calls / kernel threads
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/suspend-dev.cfg
14 # ---- General Options ----
20 # Suspend Mode
21 # e.g. standby, mem, freeze, disk (default: mem)
26 output-dir: suspend-{hostname}-{date}-{time}-dev
29 # Use rtcwake to autoresume after X seconds, or off to disable (default: 15)
33 # add the dmesg and ftrace log to the html output (default: false)
36 # Suspend/Resume Gap
[all …]
|
12345678910>>...16