Home
last modified time | relevance | path

Searched +full:resume +full:- +full:offset (Results 1 – 25 of 32) sorted by relevance

12

/Documentation/devicetree/bindings/arm/hisilicon/controller/
Dsysctrl.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Wei Xu <xuwei5@hisilicon.com>
19 offset. In addition, the HiP01 system controller has some specific control
23 Hisilicon system controller --> hisilicon,sysctrl
24 HiP01 system controller --> hisilicon,hip01-sysctrl
25 Hi6220 system controller --> hisilicon,hi6220-sysctrl
26 Hi3519 system controller --> hisilicon,hi3519-sysctrl
29 - if:
[all …]
/Documentation/power/
Dswsusp-and-swap-files.rst13 already taken care of by the swap-handling code, but (2) has to be taken into
19 journaled, it cannot be mounted during resume from disk. For this reason to
21 and the offset from the beginning of the partition at which the swap file's
22 header is located. For convenience, this offset is expressed in <PAGE_SIZE>
35 offset, in <PAGE_SIZE> units, from the beginning of the partition which
40 resume=<swap_file_partition> resume_offset=<swap_file_offset>
43 and <swap_file_offset> is the offset of the swap header determined by the
45 by the same application that determines the swap file's header offset using the
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
[all …]
Duserland-swsusp.rst16 are going to develop your own suspend/resume utilities.
26 assumed to be in the resume mode. The device cannot be open for simultaneous
49 from it (0) (after resume the system finds itself finishing the
81 allocate a swap page from the resume partition
83 will contain the swap page offset if the call is successful)
90 set the resume partition and the offset (in <PAGE_SIZE>
94 containing the resume device specification and the offset); for swap
95 partitions the offset is always 0, but it is different from zero for
96 swap files (see Documentation/power/swsusp-and-swap-files.rst for
109 immediately enter the suspend-to-RAM state, so this call must always
[all …]
Dswsusp.rst11 If you touch anything on disk between suspend and resume...
14 If you do resume from initrd after your filesystems are mounted...
22 between suspend and resume, it may do something wrong. If you change
26 ( ) suspend/resume support is needed to make it safe.
29 they won't be accessible after resume and you may lose data, as though
35 You need to append resume=/dev/your_swap_partition to kernel command
36 line or specify it using /sys/power/resume.
39 If using a swapfile you can also specify a resume offset using
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 …]
Dpci.rst13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
53 to put the device that sent it into the full-power state. However, the PCI Bus
68 Thus in many situations both the native and the platform-based power management
72 --------------------------------
[all …]
/Documentation/devicetree/bindings/powerpc/4xx/
Dcpm.txt4 - compatible : compatible list, currently only "ibm,cpm"
5 - dcr-access-method : "native"
6 - dcr-reg : < DCR register range >
9 - er-offset : All 4xx SoCs with a CPM controller have
15 er-offset = <1>.
16 - unused-units : specifier consist of one cell. For each
20 - idle-doze : specifier consist of one cell. For each
24 - standby : specifier consist of one cell. For each
27 restored on resume.
28 - suspend : specifier consist of one cell. For each
[all …]
/Documentation/devicetree/bindings/arm/cpu-enable-method/
Dal,alpine-smp2 Secondary CPU enable-method "al,alpine-smp" binding
5 This document describes the "al,alpine-smp" method for
7 "al,alpine-smp" enable method should be defined in the
10 Enable method name: "al,alpine-smp"
12 Compatible CPUs: "arm,cortex-a15"
17 "al,alpine-cpu-resume" and "al,alpine-nb-service".
20 * Alpine CPU resume registers
22 The CPU resume register are used to define required resume address after
26 - compatible : Should contain "al,alpine-cpu-resume".
27 - reg : Offset and length of the register set for the device
[all …]
/Documentation/ABI/testing/
Dsysfs-power15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
21 See Documentation/admin-guide/pm/sleep-states.rst for more
39 See Documentation/admin-guide/pm/sleep-states.rst for more
47 suspend-to-disk mechanism. Reading from this file returns
51 'firmware' - means that the memory image will be saved to disk
55 'platform' - the memory image will be saved by the kernel and
59 'shutdown' - the memory image will be saved by the kernel and
62 'reboot' - the memory image will be saved by the kernel and
66 two testing modes of the suspend-to-disk mechanism: 'testproc'
[all …]
Dsysfs-bus-iio3 Contact: linux-iio@vger.kernel.org
11 Contact: linux-iio@vger.kernel.org
25 Contact: linux-iio@vger.kernel.org
31 Contact: linux-iio@vger.kernel.org
38 Contact: linux-iio@vger.kernel.org
44 The contents of the label are free-form, but there are some
51 * "proximity-wifi"
52 * "proximity-lte"
53 * "proximity-wifi-lte"
54 * "proximity-wifi-left"
[all …]
/Documentation/admin-guide/device-mapper/
Dvdo.rst1 .. SPDX-License-Identifier: GPL-2.0-only
3 dm-vdo
6 The dm-vdo (virtual data optimizer) device mapper target provides
7 block-level deduplication, compression, and thin provisioning. As a device
20 https://github.com/dm-vdo/vdo/
25 enter or come up in read-only mode. Because read-only mode is indicative of
26 data-loss, a positive action must be taken to bring vdo out of read-only
28 prepare a read-only vdo to exit read-only mode. After running this tool,
34 inspect a vdo target's on-disk metadata. Fortunately, these tools are
35 rarely needed except by dm-vdo developers.
[all …]
Dwritecache.rst14 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
49 applicable only to persistent memory - don't use the FUA
53 - some underlying devices perform better with fua, some
64 dm-writecache target and replace it with dm-linear or
79 1. error indicator - 0 if there was no error, otherwise error number
108 5. resume the device, so that it will use the linear
Ddm-raid.rst2 dm-raid
5 The device-mapper RAID (dm-raid) target provides a bridge from DM to MD.
6 It allows the MD RAID drivers to be accessed using a device-mapper
11 -----------------------
26 - Transitory layout
29 - rotating parity 0 with data continuation
32 - rotating parity N with data continuation
35 - rotating parity 0 with data restart
38 - rotating parity N with data restart
41 - rotating parity zero (left-to-right) with data restart
[all …]
/Documentation/arch/arm/samsung/
Dbootloader-interface.rst14 In the document "boot loader" means any of following: U-boot, proprietary
19 1. Non-Secure mode
24 Offset Value Purpose
33 0x28 0x0 or last value during resume (Exynos542x) System suspend
42 Offset Value Purpose
54 Offset Value Purpose
65 3. Other (regardless of secure/non-secure mode)
70 Offset Value Purpose
72 0x0908 Non-zero Secondary CPU boot up indicator
79 AFTR - ARM Off Top Running, a low power mode, Cortex cores and many other
[all …]
/Documentation/devicetree/bindings/clock/
Dst,stm32mp1-rcc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/st,stm32mp1-rcc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Gabriel Fernandez <gabriel.fernandez@foss.st.com>
14 RCC makes also power management (resume/supend and wakeup interrupt).
18 Documentation/devicetree/bindings/clock/clock-bindings.txt
24 dt-bindings/clock/stm32mp1-clks.h header and can be used in device
36 Where bit_offset is the bit offset within the register.
43 include/dt-bindings/reset-controller/stm32mp1-resets.h
[all …]
/Documentation/sound/soc/
Dcodec.rst11 Each codec class driver *must* provide the following features:-
14 2. Codec control IO - using RegMap API
20 Optionally, codec drivers can also provide:-
31 -------------------------------
49 .name = "wm8731-hifi",
68 ----------------
76 -------------------------
83 Defines a single control as follows:-
88 shift = control bit(s) offset in register
92 Other macros include:-
[all …]
/Documentation/hid/
Dhid-sensor.rst26 Logical Minimum(-32767)
30 Report Offset(16)
35 The report is indicating "sensor page (0x20)" contains an accelerometer-3D (0x73).
36 This accelerometer-3D has some fields. Here for example field 2 is motion intensity
37 (0x045f) with a logical minimum value of -32767 and logical maximum of 32767. The
51 - Core HID driver
52 - Individual sensor processing part (sensor drivers)
55 -----------
56 The core driver (hid-sensor-hub) registers as a HID driver. It parses
58 with name HID-SENSOR-xxxx (where xxxx is usage id from the specification).
[all …]
/Documentation/sound/kernel-api/
Dwriting-an-alsa-driver.rst11 Architecture) <http://www.alsa-project.org/>`__ driver. The document
19 low-level driver implementation details. It only describes the standard
26 -------
56 --------------
60 sub-directories contain different modules and are dependent upon the
74 This directory and its sub-directories are for the ALSA sequencer. This
76 as snd-seq-midi, snd-seq-virmidi, etc. They are compiled only when
85 -----------------
88 to be exported to user-space, or included by several files in different
94 -----------------
[all …]
/Documentation/arch/arm64/
Dbooting.rst13 (EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure
33 ---------------------------
46 -------------------------
50 The device tree blob (dtb) must be placed on an 8-byte boundary and must
59 ------------------------------
71 ------------------------
75 The decompressed kernel image contains a 64-byte header as follows::
79 u64 text_offset; /* Image load offset, little endian */
86 u32 res5; /* reserved (used for PE COFF offset) */
91 - As of v3.17, all fields are little endian unless stated otherwise.
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
73 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]
/Documentation/driver-api/media/drivers/
Dcx2341x-devel.rst1 .. SPDX-License-Identifier: GPL-2.0
7 -----------------------
12 .. note:: the memory long words are little-endian ('intel format').
21 .. code-block:: none
23 ivtvctl -O min=0x02000000,max=0x020000ff
26 register space :-).
35 .. code-block:: none
37 0x00000000-0x00ffffff Encoder memory space
38 0x00000000-0x0003ffff Encode.rom
39 ???-??? MPEG buffer(s)
[all …]
/Documentation/devicetree/bindings/input/
Diqs269a.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jeff LaBundy <jeff@labundy.com>
13 - $ref: input.yaml#
16 The Azoteq IQS269A is an 8-channel capacitive touch controller that features
17 additional Hall-effect and inductive sensing capabilities.
24 - azoteq,iqs269a
25 - azoteq,iqs269a-00
26 - azoteq,iqs269a-d0
[all …]
Diqs626a.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jeff LaBundy <jeff@labundy.com>
13 The Azoteq IQS626A is a 14-channel capacitive touch controller that features
14 additional Hall-effect and inductive sensing capabilities.
19 - $ref: touchscreen/touchscreen.yaml#
31 "#address-cells":
34 "#size-cells":
37 azoteq,suspend-mode:
[all …]
/Documentation/driver-api/firmware/
Dfallback-mechanisms.rst40 * Races upon resume from suspend. This is resolved by the firmware cache, but
97 important to re-iterate that no device is created if a direct filesystem lookup
113 -----------------------
114 .. kernel-doc:: drivers/base/firmware_loader/fallback.c
171 in non-traditional paths -- paths outside of the listing documented in the
184 the uevent flag means you want to opt-in for the firmware fallback mechanism
196 The logic behind using MAX_JIFFY_OFFSET for non-uevents is that a custom
212 the peripheral's Linux device-driver needs to access this firmware.
222 .. kernel-doc:: include/linux/efi_embedded_fw.h
225 The EFI embedded-fw code works by scanning all EFI_BOOT_SERVICES_CODE memory
[all …]
/Documentation/arch/powerpc/
Dkvm-nested.rst1 .. SPDX-License-Identifier: GPL-2.0
44 vCPU (except in the short sequence in the L0 on L1 -> L2 entry and L2
45 -> L1 exit).
74 - L1 and L0 negotiate capabilities with H_GUEST_{G,S}ET_CAPABILITIES()
77 - L1 requests the L0 create an L2 with H_GUEST_CREATE() and receives a token
79 - L1 requests the L0 create an L2 vCPU with H_GUEST_CREATE_VCPU()
81 - L1 and L0 communicate the vCPU state using the H_GUEST_{G,S}ET() hcall
83 - L1 requests the L0 runs the vCPU running H_GUEST_VCPU_RUN() hcall
85 - L1 deletes L2 with H_GUEST_DELETE()
99 --------------------------
[all …]
/Documentation/networking/dsa/
Ddsa.rst22 An Ethernet switch typically comprises multiple front-panel ports and one
27 gateways, or even top-of-rack switches. This host Ethernet controller will
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
46 - what port is this frame coming from
47 - what was the reason why this frame got forwarded
48 - how to send CPU originated traffic to specific ports
52 on Port-based VLAN IDs).
57 - the "cpu" port is the Ethernet switch facing side of the management
61 - the "dsa" port(s) are just conduits between two or more switches, and as such
[all …]

12