| /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::
47 - If you feel ACPI works pretty well on your system, you might try::
51 - If you would like to write hibernation image to swap and then suspend
[all …]
|
| H A D | userland-swsusp.rst | 2 Documentation for userland software suspend interface
12 Now, to use the userland interface for software suspend you need special
13 utilities that will read/write the system memory snapshot from/to the
15 <http://suspend.sourceforge.net>. You may want to have a look at them if you
16 are going to develop your own suspend/resume utilities.
25 reading, it is considered to be in the suspend mode. Otherwise it is
26 assumed to be in the resume mode. The device cannot be open for simultaneous
27 reading and writing. It is also impossible to have the device open more than
39 and SNAPSHOT_ATOMIC_RESTORE to succeed
46 last argument of ioctl() should be a pointer to an int variable,
[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 …]
|
| 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::
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
38 (it is similar to the "reboot" mode, but it requires you to press the power
39 button to make the system resume).
[all …]
|
| H A D | charger-manager.rst | 7 Charger Manager provides in-kernel battery charger management that
8 requires temperature monitoring during suspend-to-RAM state
10 wants to look at the aggregated information of the multiple chargers.
12 Charger Manager is a platform_driver with power-supply-class entries.
13 An instance of Charger Manager (a platform-device created with Charger-Manager)
26 own power-supply-class and each power-supply-class can provide
28 aggregates charger-related information from multiple sources and
29 shows combined information as a single power-supply-class.
31 * Support for in suspend-to-RAM polling (with suspend_again callback)
32 While the battery is being charged and the system is in suspend-to-RAM,
[all …]
|
| H A D | freezing-of-tasks.rst | 11 kernel threads are controlled during hibernation or system-wide suspend (on some
17 There is one per-task flag (PF_NOFREEZE) and three per-task states
23 to system-wide suspend too).
26 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide
27 static key freezer_active (as opposed to a per-task flag or state) is used to
28 indicate whether the system is to undergo a freezing operation. And
30 try_to_freeze_tasks() that sends a fake signal to all user space processes, and
31 wakes up all the kernel threads. All freezable tasks must react to that by
32 calling try_to_freeze(), which results in a call to __refrigerator() (defined
33 in kernel/freezer.c), which changes the task's state to TASK_FROZEN, and makes
[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 …]
|
| H A D | suspend-flows.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 System Suspend Code Flows
12 At least one global system-wide transition needs to be carried out for the
13 system to get from the working state into one of the supported
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
15 transition to occur for this purpose, but the other sleep states, commonly
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
23 working state is referred to as *system resume*.
25 The kernel code flows associated with the suspend and resume transitions for
[all …]
|
| /linux/arch/mips/include/asm/ |
| H A D | pm.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
5 * PM helper macros for CPU power off (e.g. Suspend-to-RAM).
13 #include <asm/asm-offsets.h>
18 /* Save CPU state to stack for suspend to RAM */
38 /* Restore CPU state from stack after resume from RAM */
63 /* Get address of static suspend state into t1 */
68 /* Save important CPU state for early restoration to global data */
82 /* save stack pointer (pointing to GPRs) */
90 * Segment configuration must be restored prior to any access to
102 /* restore stack pointer (pointing to GPRs) */
[all …]
|
| /linux/Documentation/devicetree/bindings/soc/loongson/ |
| H A D | loongson,ls2k-pmc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/loongson/loongson,ls2k-pmc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Loongson-2 Power Manager controller
10 - Yinbo Zhu <zhuyinbo@loongson.cn>
15 - items:
16 - const: loongson,ls2k0500-pmc
17 - const: syscon
18 - items:
[all …]
|
| /linux/arch/arm/mach-socfpga/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
25 bool "Suspend to RAM on SOCFPGA"
27 Select this if you want to enable Suspend-to-RAM on SOCFPGA
|
| /linux/include/linux/power/ |
| H A D | charger-manager.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
7 * This framework enables to control and multiple chargers and to
8 * monitor charging even in the context of suspend-to-RAM with
45 * @wq: the workqueue to control charger according to the state of
48 * @nb: the notifier block to receive changed state from EXTCON
62 /* The charger-manager use Extcon framework */
72 * Set min/max current of regulator to protect over-current issue
73 * according to a kind of charger cable when cable is attached.
86 * Set if the charger-manager cannot control charger,
89 * the array of charger cables to enable/disable charger
[all …]
|
| /linux/arch/arm/mach-s3c/ |
| H A D | pm.c | 1 // SPDX-License-Identifier: GPL-2.0
4 // Copyright 2004-2008 Simtec Electronics
8 // S3C common power management (suspend to ram) support.
11 #include <linux/suspend.h>
19 #include <asm/suspend.h>
22 #include "regs-clock.h"
23 #include "regs-irq.h"
30 #include "pm-core.h"
36 /* The IRQ ext-int code goes here, it is too small to currently bother
44 unsigned long bit = 1L << IRQ_EINT_BIT(data->irq); in s3c_irqext_wake()
[all …]
|
| /linux/drivers/soc/samsung/ |
| H A D | s3c-pm-check.c | 1 // SPDX-License-Identifier: GPL-2.0
3 // originally in linux/arch/arm/plat-s3c24xx/pm.c
5 // Copyright (c) 2004-2008 Simtec Electronics
9 // S3C Power Mangament - suspend/resume memory corruption check.
12 #include <linux/suspend.h>
18 #include <linux/soc/samsung/s3c-pm.h>
21 #error CONFIG_SAMSUNG_PM_CHECK_CHUNKSIZE must be a positive non-zero value
24 /* suspend checking code...
29 * CONFIG_SAMSUNG_PM_CHECK_CHUNKSIZE defines the block-size for the CRC,
30 * increasing it will mean that the area corrupted will be less easy to spot,
[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/Documentation/ABI/testing/ |
| H A D | sysfs-class-rc | 6 The rc/ class sub-directory belongs to the Remote Controller
30 Writing "+proto" will add a protocol to the list of enabled
33 Writing "-proto" will remove a protocol from the list of enabled
50 Use in combination with /sys/class/rc/rcN/filter_mask to set the
56 This value may be reset to 0 if the current protocol is altered.
63 Sets the scancode filter mask of bits to compare.
64 Use in combination with /sys/class/rc/rcN/filter to set the bits
66 value. A value of 0 disables the filter to allow all valid
67 scancodes to be processed.
73 This value may be reset to 0 if the current protocol is altered.
[all …]
|
| /linux/arch/arm/mach-shmobile/ |
| H A D | suspend.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Suspend-to-RAM support code for SH-Mobile ARM
9 #include <linux/suspend.h>
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | microchip,mcp16502.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MCP16502 - High-Performance PMIC
10 - Andrei Simion <andrei.simion@microchip.com>
16 of High-Performance mode (HPM).
22 lpm-gpios:
26 suspend-to-ram, keeping the PMIC into HIBERNATE mode.
31 lvin-supply:
34 pvin1-supply:
[all …]
|
| /linux/kernel/power/ |
| H A D | suspend_test.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * kernel/power/suspend_test.c - Suspend to RAM and standby test facility.
14 * We test the system suspend code by setting an RTC wakealarm a short
18 * The time it takes is system-specific though, so when we test this
31 * during the irqs-are-off stages of the suspend/resume cycle... in suspend_test_start()
38 long nj = jiffies - suspend_test_start_time; in suspend_test_finish()
45 /* Warning on suspend means the RTC alarm period needs to be in suspend_test_finish()
46 * larger -- the system was sooo slooowwww to suspend that the in suspend_test_finish()
47 * alarm (should have) fired before the system went to sleep! in suspend_test_finish()
49 * Warning on either suspend or resume also means the system in suspend_test_finish()
[all …]
|
| /linux/drivers/memory/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
9 This option allows to enable specific memory controller drivers,
12 vary from memory tuning and frequency scaling to enabling
13 access to attached peripherals through memory bus.
42 Used to configure the EBI (external bus interface) when the device-
51 This driver provides access to the DPFE interface of Broadcom
53 provide current information about the system's RAM, for instance
55 for the DRAM's temperature. Slower refresh rate means cooler RAM,
56 higher refresh rate means hotter RAM.
63 This driver provides a way to configure the Broadcom STB memory
[all …]
|
| /linux/arch/arm/mach-mvebu/ |
| H A D | board-v7.c | 1 // SPDX-License-Identifier: GPL-2.0-only
8 * Gregory CLEMENT <gregory.clement@free-electrons.com>
9 * Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
18 #include <linux/dma-mapping.h>
23 #include <asm/hardware/cache-l2x0.h>
28 #include "armada-370-xp.h"
31 #include "mvebu-soc-id.h"
37 * Cortex-A based SOCs, not on PJ4B based ones.
42 of_find_compatible_node(NULL, NULL, "arm,cortex-a9-scu"); in mvebu_scu_enable()
56 * When returning from suspend, the platform goes through the
[all …]
|
| /linux/include/linux/ |
| H A D | pm.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * pm.h - Power management interface
22 * Callbacks for platform drivers to implement.
64 * struct dev_pm_ops - device PM callbacks.
66 * @prepare: The principal role of this callback is to prevent new children of
68 * subsystem and generally the rest of the kernel is supposed to prevent
69 * new calls to the probe method from being made too once @prepare() has
71 * registration of a child already in progress), it may return -EAGAIN, so
73 * been registered) to recover from the race condition.
74 * This method is executed for all kinds of suspend transitions and is
[all …]
|
| /linux/Documentation/devicetree/bindings/firmware/ |
| H A D | nvidia,tegra210-bpmp.txt | 3 The Boot and Power Management Processor (BPMP) is a co-processor found
4 in Tegra210 SoC. It is designed to handle the early stages of the boot
5 process as well as to assisting in entering deep low power state
6 (suspend to ram), and also offloading DRAM memory clock scaling on
12 - compatible
15 - "nvidia,tegra210-bpmp"
16 - reg: physical base address and length for HW synchornization primitives
17 1) base address and length to Tegra 'atomics' hardware
18 2) base address and length to Tegra 'semaphore' hardware
19 - interrupts: specifies the interrupt number for receiving messages ("rx")
[all …]
|
| /linux/Documentation/driver-api/usb/ |
| H A D | persist.rst | 1 .. _usb-persist:
3 USB device persistence during system suspend
13 According to the USB specification, when a USB bus is suspended the
14 bus must continue to supply suspend current (around 1-5 mA). This
16 detect connect-change events (devices being plugged in or unplugged).
20 required to behave as though the device has been unplugged. It's a
21 conservative approach; in the absence of suspend current the computer
22 has no way to know what has actually happened. Perhaps the same
26 By default, Linux behaves according to the spec. If a USB host
27 controller loses power during a system suspend, then when the system
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | writecache.rst | 6 doesn't cache reads because reads are supposed to be cached in page cache
7 in normal RAM.
14 1. type of the cache device - "p" or "s"
15 - p - persistent memory
16 - s - SSD
25 offset from the start of cache device in 512-byte sectors
45 applicable only to persistent memory - use the FUA flag
46 when writing data from persistent memory back to the
49 applicable only to persistent memory - don't use the FUA
53 - some underlying devices perform better with fua, some
[all …]
|