/linux/Documentation/power/ |
H A 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 …]
|
H A 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 …]
|
H A 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 …]
|
H A D | drivers-testing.rst | 2 Testing suspend and resume support in device drivers 10 Unfortunately, to effectively test the support for the system-wide suspend and 11 resume transitions in a driver, it is necessary to suspend and resume a fully 14 (aka suspend to disk or STD) and suspend to RAM (STR), because each of these 18 Of course, for this purpose the test system has to be known to suspend and 20 resolve all suspend/resume-related problems in the test system before you start 21 testing the new driver. Please see Documentation/power/basic-pm-debugging.rst 22 for more information about the debugging of suspend/resume functionality. 27 Once you have resolved the suspend/resume-related problems with your test system 28 without the new driver, you are ready to test it: [all …]
|
/linux/Documentation/ABI/testing/ |
H A 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 …]
|
H A 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 …]
|
/linux/kernel/power/ |
H A 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 …]
|
/linux/Documentation/admin-guide/pm/ |
H A 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 …]
|
/linux/Documentation/devicetree/bindings/regulator/ |
H A 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 …]
|
H A D | maxim,max77802.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Javier Martinez Canillas <javier@dowhile0.org> 11 - Krzysztof Kozlowski <krzk@kernel.org> 17 The Maxim MAX77686 provides 10 high-efficiency Buck and 32 Low-DropOut (LDO) 23 Certain regulators support "regulator-initial-mode" and "regulator-mode". 24 The valid modes list is defined in the dt-bindings/regulator/maxim,max77802.h 26 1 - Normal regulator voltage output mode. 27 3 - Low Power which reduces the quiescent current down to only 1uA [all …]
|
/linux/arch/arm64/boot/dts/rockchip/ |
H A D | rk3568-qnap-ts433.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 4 * Copyright (c) 2024 Uwe Kleine-König 7 /dts-v1/; 9 #include <dt-bindings/input/input.h> 10 #include <dt-bindings/leds/common.h> 11 #include <dt-bindings/gpio/gpio.h> 15 model = "Qnap TS-433-4G NAS System 4-Bay"; 25 stdout-path = "serial2:115200n8"; 29 compatible = "gpio-keys"; 30 pinctrl-0 = <©_button_pin>, <&reset_button_pin>; [all …]
|
/linux/include/linux/ |
H A D | suspend.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 44 * struct platform_suspend_ops - Callbacks for managing platform dependent 47 * @valid: Callback to determine if given system sleep state is supported by 50 * that it still may be impossible to enter given system sleep state if the 53 * assigned to this if the platform only supports mem sleep. 55 * @begin: Initialise a transition to given system sleep state. 56 * @begin() is executed right prior to suspending devices. The information 57 * conveyed to the platform code by @begin() should be disregarded by it as 61 * passed to @enter() is redundant and should be ignored. 66 * appropriate .suspend() method has been executed for each device) and [all …]
|
/linux/drivers/md/ |
H A D | dm.c | 1 // SPDX-License-Identifier: GPL-2.0-only 4 * Copyright (C) 2004-2008 Red Hat, Inc. All rights reserved. 9 #include "dm-core.h" 10 #include "dm-rq.h" 11 #include "dm-uevent.h" 12 #include "dm-ima.h" 14 #include <linux/bio-integrity.h> 33 #include <linux/blk-crypto.h> 34 #include <linux/blk-crypto-profile.h> 47 * dm_io into one list, and reuse bio->bi_private as the list head. Before [all …]
|
/linux/tools/power/pm-graph/config/ |
H A 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 …]
|
H A 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 …]
|
H A D | suspend.cfg | 2 # Generic S3 (Suspend to Mem) test 5 # all the tool arguments so that they don't have to be given on the 9 # sudo ./sleepgraph.py -config config/suspend.cfg 14 # ---- General Options ---- 20 # Suspend Mode 21 # e.g. standby, mem, freeze, disk (default: mem) 26 output-dir: suspend-{hostname}-{date}-{time} 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 …]
|
H A D | suspend-callgraph.cfg | 2 # Full Callgraph for S3 (Suspend to Mem) test 5 # all the tool arguments so that they don't have to be given on the 9 # sudo ./sleepgraph.py -config config/suspend.cfg 15 # ---- General Options ---- 21 # Suspend Mode 22 # e.g. standby, mem, freeze, disk (default: mem) 27 output-dir: suspend-{hostname}-{date}-{time}-cg 30 # Use rtcwake to autoresume after X seconds, or off to disable (default: 15) 34 # add the dmesg and ftrace log to the html output (default: false) 37 # Suspend/Resume Gap [all …]
|
H A D | freeze-dev.cfg | 2 # Dev S2 (Freeze) 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/freeze-dev.cfg 14 # ---- General Options ---- 20 # Suspend Mode 21 # e.g. standby, mem, freeze, disk (default: mem) 26 output-dir: freeze-{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 …]
|
H A D | standby-dev.cfg | 2 # Dev S1 (Standby) 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/standby-dev.cfg 14 # ---- General Options ---- 20 # Suspend Mode 21 # e.g. standby, mem, freeze, disk (default: mem) 26 output-dir: standby-{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 …]
|
H A D | standby-callgraph.cfg | 5 # all the tool arguments so that they don't have to be given on the 9 # sudo ./sleepgraph.py -config config/standby-callgraph.cfg 15 # ---- General Options ---- 21 # Suspend Mode 22 # e.g. standby, mem, freeze, disk (default: mem) 27 output-dir: standby-{hostname}-{date}-{time}-cg 30 # Use rtcwake to autoresume after X seconds, or off to disable (default: 15) 34 # add the dmesg and ftrace log to the html output (default: false) 37 # Suspend/Resume Gap 38 # insert a small visible gap between suspend and resume on the timeline (default: false) [all …]
|
H A D | freeze-callgraph.cfg | 5 # all the tool arguments so that they don't have to be given on the 9 # sudo ./sleepgraph.py -config config/freeze-callgraph.cfg 15 # ---- General Options ---- 21 # Suspend Mode 22 # e.g. standby, mem, freeze, disk (default: mem) 27 output-dir: freeze-{hostname}-{date}-{time}-cg 30 # Use rtcwake to autoresume after X seconds, or off to disable (default: 15) 34 # add the dmesg and ftrace log to the html output (default: false) 37 # Suspend/Resume Gap 38 # insert a small visible gap between suspend and resume on the timeline (default: false) [all …]
|
H A D | freeze.cfg | 5 # all the tool arguments so that they don't have to be given on the 9 # sudo ./sleepgraph.py -config config/freeze.cfg 14 # ---- General Options ---- 20 # Suspend Mode 21 # e.g. standby, mem, freeze, disk (default: mem) 26 output-dir: freeze-{hostname}-{date}-{time} 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 37 # insert a small visible gap between suspend and resume on the timeline (default: false) [all …]
|
H A D | standby.cfg | 5 # all the tool arguments so that they don't have to be given on the 9 # sudo ./sleepgraph.py -config config/standby.cfg 14 # ---- General Options ---- 20 # Suspend Mode 21 # e.g. standby, mem, freeze, disk (default: mem) 26 output-dir: standby-{hostname}-{date}-{time} 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 37 # insert a small visible gap between suspend and resume on the timeline (default: false) [all …]
|
/linux/drivers/soc/loongson/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0+ 3 # Loongson-2 series SoC drivers 7 tristate "Loongson-2 SoC Global UtiliTieS (GUTS) register block" 14 controller, and clock control. This patch adds a driver to manage 15 and access global utilities block for LoongArch architecture Loongson-2 21 bool "Loongson-2 SoC Power Management Controller Driver" 25 The Loongson-2's power management controller was ACPI, supports ACPI 26 S2Idle (Suspend To Idle), ACPI S3 (Suspend To RAM), ACPI S4 (Suspend To 27 Disk), ACPI S5 (Soft Shutdown) and supports multiple wake-up methods 28 (USB, GMAC, PWRBTN, etc.). This driver was to add power management [all …]
|
/linux/tools/power/pm-graph/ |
H A D | README | 8 pm-graph: suspend/resume/boot timing analysis tools 11 …Home Page: https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/overvi… 13 Report bugs/issues at bugzilla.kernel.org Tools/pm-graph 14 - https://bugzilla.kernel.org/buglist.cgi?component=pm-graph&product=Tools 17 - Getting Started: 20 - Feature Summary: 21 https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/features.html 23 - upstream version in git: 24 git clone https://github.com/intel/pm-graph/ 27 - Overview [all …]
|