Home
last modified time | relevance | path

Searched +full:suspend +full:- +full:to +full:- +full:ram (Results 1 – 25 of 34) sorted by relevance

12

/Documentation/power/
Dinterface.rst16 - 'freeze' (Suspend-to-Idle)
17 - 'standby' (Power-On Suspend)
18 - 'mem' (Suspend-to-RAM)
19 - 'disk' (Suspend-to-Disk)
21 Suspend-to-Idle is always supported. Suspend-to-Disk is always supported
22 too as long the kernel has been configured to support hibernation at all
24 for Suspend-to-RAM and Power-On Suspend depends on the capabilities of the
27 If one of the strings listed in /sys/power/state is written to it, the system
28 will attempt to transition into the corresponding sleep state. Refer to
29 Documentation/admin-guide/pm/sleep-states.rst for a description of each of
[all …]
Dswsusp.rst2 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 …]
Ddrivers-testing.rst2 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 …]
Duserland-swsusp.rst2 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 …]
Dcharger-manager.rst7 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 …]
Dsuspend-and-cpuhotplug.rst2 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 …]
Dbasic-pm-debugging.rst2 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 …]
Dfreezing-of-tasks.rst11 kernel threads are controlled during hibernation or system-wide suspend (on some
17 There are three per-task flags used for that, PF_NOFREEZE, PF_FROZEN
21 suspend state as well as before a hibernation image is created (in what follows
22 we only consider hibernation, but the description also applies to suspend).
25 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide
26 variable system_freezing_cnt (as opposed to a per-task flag) is used to indicate
27 whether the system is to undergo a freezing operation. And freeze_processes()
29 fake signal to all user space processes, and wakes up all the kernel threads.
30 All freezable tasks must react to that by calling try_to_freeze(), which
31 results in a call to __refrigerator() (defined in kernel/freezer.c), which sets
[all …]
Druntime_pm.rst5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 put their PM-related work items. It is strongly recommended that pm_wq be
19 used for queuing all work items related to runtime PM, because this allows
20 them to be synchronized with system-wide power transitions (suspend to RAM,
34 device drivers are encouraged to use these functions.
53 The ->runtime_suspend(), ->runtime_resume() and ->runtime_idle() callbacks
57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
60 2. Device type of the device, if both dev->type and dev->type->pm are present.
62 3. Device class of the device, if both dev->class and dev->class->pm are
65 4. Bus type of the device, if both dev->bus and dev->bus->pm are present.
[all …]
/Documentation/admin-guide/pm/
Dsleep-states.rst1 .. 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 …]
/Documentation/arm/samsung-s3c24xx/
Dsuspend.rst2 S3C24XX Suspend Support
7 ------------
9 The S3C24XX supports a low-power suspend mode, where the SDRAM is kept
10 in Self-Refresh mode, and all but the essential peripheral blocks are
16 ------------
24 4) Any peripherals that are going to be powered down at the same
25 time require suspend/resume support.
29 --------
31 The S3C2410 user manual defines the process of sending the CPU to
33 is to set the GSTATUS3 register to the physical address of the
[all …]
Doverview.rst8 ------------
10 The Samsung S3C24XX range of ARM9 System-on-Chip CPUs are supported
16 corresponding code has been removed after a while. If someone wishes to
21 included under the arch/arm/mach-s3c2416 directory. Note, while core
27 -------------
38 ------
41 arch/arm/plat-s3c24xx with headers in include/asm-arm/plat-s3c24xx.
42 This directory should be kept to items shared between the platform
43 code (arch/arm/plat-s3c24xx) and the arch/arm/mach-s3c24* code.
47 in arch/arm/mach-s3c2410 and S3C2440 in arch/arm/mach-s3c2440
[all …]
Ds3c2412.rst6 ------------
8 The S3C2412 is part of the S3C24XX range of ARM9 System-on-Chip CPUs
9 from Samsung. This part has an ARM926-EJS core, capable of running up
10 to 266MHz (see data-sheet for more information)
14 -----
16 The core clock code provides a set of clocks to the drivers, and allows
21 -----
23 No support for suspend/resume to RAM in the current system.
27 ---
33 ----
[all …]
/Documentation/devicetree/bindings/regulator/
Dmcp16502-regulator.txt4 - compatible: "microchip,mcp16502"
5 - reg: I2C slave address
6 - lpm-gpios: GPIO for LPM pin. Note that this GPIO *must* remain high during
7 suspend-to-ram, keeping the PMIC into HIBERNATE mode.
8 - regulators: A node that houses a sub-node for each regulator within
9 the device. Each sub-node is identified using the node's
10 name. The content of each sub-node is defined by the
14 1) VDD_IO - Buck (1.2 - 3.7 V)
15 2) VDD_DDR - Buck (0.6 - 1.85 V)
16 3) VDD_CORE - Buck (0.6 - 1.85 V)
[all …]
Dregulator.yaml1 # 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 …]
/Documentation/devicetree/bindings/firmware/
Dnvidia,tegra210-bpmp.txt3 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 …]
/Documentation/ABI/testing/
Dsysfs-devices-power6 allowing the user space to check and modify some power
14 space to check if the device is enabled to wake up the system
15 from sleep states, such as the memory sleep state (suspend to
16 RAM) and hibernation (suspend to disk), and to enable or disable
17 it to do that as desired.
20 used to activate the system from a sleep state. Such devices
24 + "enabled\n" to issue the events;
25 + "disabled\n" not to do so;
29 "disabled" to it.
33 be enabled to wake up the system from sleep states.
[all …]
Dsysfs-class-rc6 The rc/ class sub-directory belongs to the Remote Controller
27 Writing "+proto" will add a protocol to the list of enabled
29 Writing "-proto" will remove a protocol from the list of enabled
42 Use in combination with /sys/class/rc/rcN/filter_mask to set the
47 This value may be reset to 0 if the current protocol is altered.
54 Sets the scancode filter mask of bits to compare.
55 Use in combination with /sys/class/rc/rcN/filter to set the bits
57 value. A value of 0 disables the filter to allow all valid
58 scancodes to be processed.
62 This value may be reset to 0 if the current protocol is altered.
[all …]
Dsysfs-power6 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 …]
/Documentation/admin-guide/device-mapper/
Dwritecache.rst6 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"
16 - p - persistent memory
17 - s - SSD
26 offset from the start of cache device in 512-byte sectors
46 applicable only to persistent memory - use the FUA flag
47 when writing data from persistent memory back to the
50 applicable only to persistent memory - don't use the FUA
54 - some underlying devices perform better with fua, some
[all …]
/Documentation/media/uapi/rc/
Drc-sysfs-nodes.rst1 .. Permission is granted to copy, distribute and/or modify this
4 .. Foundation, with no Invariant Sections, no Front-Cover Texts
5 .. and no Back-Cover Texts. A copy of the license is included at
6 .. Documentation/media/uapi/fdl-appendix.rst.
8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
16 As defined at ``Documentation/ABI/testing/sysfs-class-rc``, those are
25 The ``/sys/class/rc/`` class sub-directory belongs to the Remote
50 Writing "+proto" will add a protocol to the list of enabled protocols.
52 Writing "-proto" will remove a protocol from the list of enabled
70 Use in combination with ``/sys/class/rc/rcN/filter_mask`` to set the
[all …]
/Documentation/driver-api/usb/
Dpersist.rst1 .. _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 …]
/Documentation/fb/
Dlxfb.rst12 * No need to use AMD's VSA code (or other VESA emulation layer) in the
17 * Most important: boot logo :-)
24 How to use it?
37 XF68_FBDev should generally work fine, but it is non-accelerated.
43 You can pass kernel command line options to lxfb with lxfb.<option>.
49 <x>x<y>[-<bpp>][@<refresh>]
50 vram size of video ram (normally auto-detected)
51 vt_switch enable vt switching during suspend/resume. The vt
Dgxfb.rst11 * No need to use AMD's VSA code (or other VESA emulation layer) in the
16 * Most important: boot logo :-)
23 How to use it?
36 XF68_FBDev should generally work fine, but it is non-accelerated.
42 You can pass kernel command line options to gxfb with gxfb.<option>.
48 <x>x<y>[-<bpp>][@<refresh>]
49 vram size of video ram (normally auto-detected)
50 vt_switch enable vt switching during suspend/resume. The vt
/Documentation/admin-guide/
Dkernel-parameters.rst3 The kernel's command-line parameters
12 The kernel parses parameters from the kernel command line up to "``--``";
14 parameter gets passed to init: parameters with '=' go into init's
15 environment, others are passed as command line arguments to init.
16 Everything after "``--``" is passed as an argument to init.
24 Parameters for modules which are built into the kernel need to be
32 log_buf_len=1M print-fatal-signals=1
36 log-buf-len=1M print_fatal_signals=1
38 Double-quotes can be used to protect spaces in values, e.g.::
43 ----------
[all …]

12