Home
last modified time | relevance | path

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

12

/Documentation/power/
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::
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 …]
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 …]
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::
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 …]
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 …]
Dswsusp-dmcrypt.rst2 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 …]
Dswsusp-and-swap-files.rst2 Using swap files with software suspend (swsusp)
13 already taken care of by the swap-handling code, but (2) has to be taken into
18 filesystem holding the swap file to be mounted, and if this filesystem is
19 journaled, it cannot be mounted during resume from disk. For this reason to
25 In order to use a swap file with swsusp, you need to:
38 3) Add the following parameters to the kernel command line::
50 Use a userland suspend application that will set the partition and offset
52 Documentation/power/userland-swsusp.rst (this is the only method to suspend
53 to a swap file allowing the resume to be initiated from an initrd or initramfs
57 partition. In particular, the swap file has to be active (ie. be present in
[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 …]
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 …]
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/ABI/testing/
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 …]
Dsysfs-class-regulator17 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 …]
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 …]
/Documentation/devicetree/bindings/regulator/
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/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/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 …]
/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/scsi/
DNinjaSCSI.txt2 WorkBiT NinjaSCSI-3/32Bi driver for Linux
5 This is Workbit corp.'s(http://www.workbit.co.jp/) NinjaSCSI-3
10 pcmcia-cs: 3.1.27
11 gcc: gcc-2.95.4
12 PC card: I-O data PCSC-F (NinjaSCSI-3)
13 I-O data CBSC-II in 16 bit mode (NinjaSCSI-32Bi)
14 SCSI device: I-O data CDPS-PX24 (CD-ROM drive)
15 Media Intelligent MMO-640GT (Optical disk drive)
18 [1] Check your PC card is true "NinjaSCSI-3" card.
19 If you installed pcmcia-cs already, pcmcia reports your card as UNKNOWN
[all …]
/Documentation/devicetree/bindings/leds/
Dleds-gpio.txt1 LEDs connected to GPIO lines
4 - compatible : should be "gpio-leds".
6 Each LED is represented as a sub-node of the gpio-leds device. Each
9 LED sub-node properties:
10 - gpios : Should specify the LED's GPIO, see "gpios property" in
13 - function : (optional)
15 - color : (optional)
17 - label : (optional)
19 - linux,default-trigger : (optional)
21 - default-state: (optional) The initial state of the LED.
[all …]
/Documentation/driver-api/pm/
Ddevices.rst1 .. SPDX-License-Identifier: GPL-2.0
18 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
26 management (PM) code is also driver-specific. Most drivers will do very
30 This writeup gives an overview of how drivers interact with system-wide
32 shared by everything that hooks up to the driver model core. Read it as
33 background for the domain-specific work you'd do with any specific driver.
39 Drivers will use one or both of these models to put devices into low-power
44 Drivers can enter low-power states as part of entering system-wide
45 low-power states like "suspend" (also known as "suspend-to-RAM"), or
47 "suspend-to-disk").
[all …]
/Documentation/admin-guide/device-mapper/
Dthin-provisioning.rst8 This document describes a collection of device-mapper targets that
9 between them implement thin-provisioning and snapshots.
11 The main highlight of this implementation, compared to the previous
12 implementation of snapshots, is that it allows many virtual devices to
14 allows the sharing of data between volumes, thus reducing disk usage.
20 implementation uses a single data structure to avoid this degradation
25 administrator some freedom, for example to:
27 - Improve metadata resilience by storing metadata on a mirrored volume
28 but data on a non-mirrored one.
30 - Improve performance by storing the metadata on SSD.
[all …]
Ddm-integrity.rst2 dm-integrity
5 The dm-integrity target emulates a block device that has additional
6 per-sector tags that can be used for storing integrity information.
9 writing the sector and the integrity tag must be atomic - i.e. in case of
12 To guarantee write atomicity, the dm-integrity target uses journal, it
14 and then copies the data and integrity tags to their respective location.
16 The dm-integrity target can be used with the dm-crypt target - in this
17 situation the dm-crypt target creates the integrity data and passes them
18 to the dm-integrity target via bio_integrity_payload attached to the bio.
19 In this mode, the dm-crypt and dm-integrity targets provide authenticated
[all …]
Ddm-clone.rst1 .. SPDX-License-Identifier: GPL-2.0-only
4 dm-clone
10 dm-clone is a device mapper target which produces a one-to-one copy of an
11 existing, read-only source device into a writable destination device: It
15 The main use case of dm-clone is to clone a potentially remote, high-latency,
16 read-only, archival-type block device into a writable, fast, primary-type device
17 for fast, low-latency I/O. The cloned device is visible/mountable immediately
18 and the copy of the source device to the destination device happens in the
21 For example, one could restore an application backup from a read-only copy,
24 without waiting for the restore to complete.
[all …]
/Documentation/media/uapi/v4l/
Duserp.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
22 with the memory type set to ``V4L2_MEMORY_USERPTR``.
26 can reside for example in virtual or shared memory. Only pointers to
27 data are exchanged, these pointers and meta-information are passed in
29 :c:type:`v4l2_plane` in the multi-planar API case). The
39 .. code-block:: c
[all …]
/Documentation/driver-api/md/
Dmd-cluster.rst5 The cluster MD is a shared-device RAID for a cluster, it supports
9 1. On-disk format
12 Separate write-intent-bitmaps are used for each cluster node.
14 and may not yet have finished. The on-disk layout is::
17 -------------------------------------------------------------------
24 one node writes to any given block at a time, so a write request will
26 - set the appropriate bit (if not already set)
27 - commit the write to all mirrors
28 - schedule the bit to be cleared after a timeout.
30 Reads are just handled normally. It is up to the filesystem to ensure
[all …]
/Documentation/mic/
Dmic_overview.rst5 An Intel MIC X100 device is a PCIe form factor add-in coprocessor
11 transfers control to the card OS downloaded from the host driver. The
12 host driver supports OSPM suspend and resume operations. It shuts down
13 the card during suspend and reboots the card OS during resume.
17 Since it is a PCIe card, it does not have the ability to host hardware
19 on X100 coprocessors thus enabling a self-bootable equivalent
21 leverages the standard virtio framework for network, disk and console
24 backends or devices on the host which are used to probe virtio drivers
26 in the kernel is used to access virtio rings from the host. The card
27 VOP driver allows card virtio drivers to communicate with their user
[all …]

12