Searched +full:suspend +full:- +full:to +full:- +full:ram (Results 1 – 25 of 311) sorted by relevance
12345678910>>...13
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/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::
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 …]
|
| 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 …]
|
| 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 …]
|
| 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 …]
|
| 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 …]
|
| D | suspend-and-cpuhotplug.rst | 2 Interaction of Suspend code (S3) with the CPU hotplug infrastructure
5 (C) 2011 - 2014 Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
8 I. Differences between CPU hotplug and Suspend-to-RAM
11 How does the regular CPU hotplug code differ from how the Suspend-to-RAM
14 Well, a picture is worth a thousand words... So ASCII art follows :-)
17 interactions involving the freezer and CPU hotplug and also tries to explain
21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
24 On a high level, the suspend-resume cycle goes like this::
26 |Freeze| -> |Disable nonboot| -> |Do suspend| -> |Enable nonboot| -> |Thaw |
32 Suspend call path
[all …]
|
| /linux-6.12.1/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 …]
|
| 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-6.12.1/arch/mips/include/asm/ |
| 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-6.12.1/Documentation/devicetree/bindings/soc/loongson/ |
| 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-6.12.1/arch/arm/mach-socfpga/ |
| 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-6.12.1/Documentation/devicetree/bindings/regulator/ |
| D | richtek,rtq2208.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Alina Yu <alina_yu@richtek.com>
14 multi-configurable synchronous buck converters and two LDOs.
16 Bucks support "regulator-allowed-modes" and "regulator-mode". The former defines the permitted
17 switching operation in normal mode; the latter defines the operation in suspend to RAM mode.
19 No matter the RTQ2208 is configured to normal or suspend to RAM mode, there are two switching
25 0 - Auto mode for power saving, which reducing the switching frequency at light load condition
26 to maintain high frequency.
[all …]
|
| /linux-6.12.1/include/linux/power/ |
| 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-6.12.1/arch/arm/mach-s3c/ |
| 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-6.12.1/drivers/soc/samsung/ |
| 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-6.12.1/drivers/soc/loongson/ |
| 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-6.12.1/drivers/gpu/drm/ci/xfails/ |
| D | msm-sc7180-trogdor-kingoftown-skips.txt | 1 # Suspend to RAM seems to be broken on this machine
2 .*suspend.*
22 kms_flip@2x-wf_vblank-ts-check
25 kms_cursor_crc@cursor-random-max-size
|
| D | i915-amly-skips.txt | 1 # Suspend to RAM seems to be broken on this machine
2 .*suspend.*
4 kms_plane_scaling@invalid-parameters
|
| D | panfrost-rk3399-skips.txt | 1 # Suspend to RAM seems to be broken on this machine
2 .*suspend.*
20 # Skip display functionality tests for GPU-only drivers
|
| D | panfrost-rk3288-skips.txt | 1 # Suspend to RAM seems to be broken on this machine
2 .*suspend.*
20 # Skip display functionality tests for GPU-only drivers
|
| D | i915-glk-skips.txt | 1 # Suspend to RAM seems to be broken on this machine
2 .*suspend.*
5 kms_plane_scaling@invalid-parameters
|
| D | i915-apl-skips.txt | 1 # Suspend to RAM seems to be broken on this machine
2 .*suspend.*
4 kms_plane_scaling@invalid-parameters
|
| D | i915-tgl-skips.txt | 1 # Suspend to RAM seems to be broken on this machine
2 .*suspend.*
8 kms_flip@absolute-wf_vblank@a-edp1
11 kms_plane_scaling@invalid-parameters
|
| D | i915-kbl-skips.txt | 1 # Suspend to RAM seems to be broken on this machine
2 .*suspend.*
5 kms_plane_scaling@invalid-parameters
|
12345678910>>...13