Searched +full:mode +full:- +full:recovery (Results 1 – 25 of 77) sorted by relevance
1234
| /Documentation/devicetree/bindings/power/reset/ |
| D | reboot-mode.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/reboot-mode.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic reboot mode core map
10 - Andy Yan <andy.yan@rock-chips.com>
13 This driver get reboot mode arguments and call the write
18 All mode properties are vendor specific, it is a indication to tell
20 as mode-xxx = <magic> (xxx is mode name, magic should be a non-zero value).
23 - normal: Normal reboot mode, system reboot with command "reboot".
[all …]
|
| D | nvmem-reboot-mode.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/nvmem-reboot-mode.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic NVMEM reboot mode
10 - Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
13 This driver gets the reboot mode magic value from the reboot-mode driver
14 and stores it in the NVMEM cell named "reboot-mode". The bootloader can
19 const: nvmem-reboot-mode
21 nvmem-cells:
[all …]
|
| D | syscon-reboot-mode.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/power/reset/syscon-reboot-mode.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic SYSCON reboot mode driver
10 - Sebastian Reichel <sre@kernel.org>
13 This driver gets reboot mode magic value from reboot-mode driver
17 parental dt-node plus the offset. So the SYSCON reboot-mode node
18 should be represented as a sub-node of a "syscon", "simple-mfd" node.
22 const: syscon-reboot-mode
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,sta32x.txt | 7 - compatible: "st,sta32x"
8 - reg: the I2C address of the device for I2C
9 - reset-gpios: a GPIO spec for the reset pin. If specified, it will be
12 - power-down-gpios: a GPIO spec for the power down pin. If specified,
16 - Vdda-supply: regulator spec, providing 3.3V
17 - Vdd3-supply: regulator spec, providing 3.3V
18 - Vcc-supply: regulator spec, providing 5V - 26V
22 - clocks, clock-names: Clock specifier for XTI input clock.
24 and disabled when it is removed. The 'clock-names' must be set to 'xti'.
26 - st,output-conf: number, Selects the output configuration:
[all …]
|
| D | st,sta350.txt | 7 - compatible: "st,sta350"
8 - reg: the I2C address of the device for I2C
9 - reset-gpios: a GPIO spec for the reset pin. If specified, it will be
12 - power-down-gpios: a GPIO spec for the power down pin. If specified,
16 - vdd-dig-supply: regulator spec, providing 3.3V
17 - vdd-pll-supply: regulator spec, providing 3.3V
18 - vcc-supply: regulator spec, providing 5V - 26V
22 - st,output-conf: number, Selects the output configuration:
23 0: 2-channel (full-bridge) power, 2-channel data-out
24 1: 2 (half-bridge). 1 (full-bridge) on-board power
[all …]
|
| D | cs35l32.txt | 5 - compatible : "cirrus,cs35l32"
7 - reg : the I2C address of the device for I2C. Address is determined by the level
10 - VA-supply, VP-supply : power supplies for the device,
15 - reset-gpios : a GPIO spec for the reset pin. If specified, it will be
18 - cirrus,boost-manager : Boost voltage control.
19 0 = Automatically managed. Boost-converter output voltage is the higher
21 1 = Automatically managed irrespective of audio, adapting for low-power
22 dissipation when LEDs are ON, and operating in Fixed-Boost Bypass Mode
24 2 = (Default) Boost voltage fixed in Bypass Mode (VBST = VP).
27 - cirrus,sdout-datacfg : Data configuration for dual CS35L32 applications only.
[all …]
|
| /Documentation/mm/ |
| D | hwpoison.rst | 9 (``MCA recovery``). This requires the OS to declare a page "poisoned",
41 The code consists of a the high level handler in mm/memory-failure.c,
46 of applications. KVM support requires a recent qemu-kvm release.
54 Failure recovery modes
57 There are two (actually three) modes memory failure recovery can be in:
60 All memory failures cause a panic. Do not attempt recovery.
67 This is the mode used by KVM qemu.
81 Enable early kill mode globally
84 Set early/late kill mode/revert to system default
89 arg2 defines thread specific mode
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | cortina.txt | 2 ---------------------------------------
7 devices, equipped with clock and data recovery (CDR) circuits. These
10 "ethernet-phy-id" compatible.
12 Since the driver only implements polling mode support, interrupts info
18 compatible = "ethernet-phy-id13e5.1002";
|
| /Documentation/driver-api/md/ |
| D | raid5-cache.rst | 7 caches data to the RAID disks. The cache can be in write-through (supported
8 since 4.4) or write-back mode (supported since 4.10). mdadm (supported since
9 3.4) has a new option '--write-journal' to create array with cache. Please
11 in write-through mode. A user can switch it to write-back mode by::
13 echo "write-back" > /sys/block/md0/md/journal_mode
15 And switch it back to write-through mode by::
17 echo "write-through" > /sys/block/md0/md/journal_mode
22 write-through mode
25 This mode mainly fixes the 'write hole' issue. For RAID 4/5/6 array, an unclean
34 The write-through cache will cache all data on cache disk first. After the data
[all …]
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | qcom,pm8916-wdt.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/watchdog/qcom,pm8916-wdt.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
13 - $ref: watchdog.yaml#
17 const: qcom,pm8916-wdt
23 - compatible
24 - interrupts
29 - |
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 1 # 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:
28 regulator-min-microamp:
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-chromeos-acpi | 9 0 Read only (recovery) firmware.
21 0 Recovery.
37 2 Recovery button was pressed.
38 4 Recovery button was pressed (EC firmware).
56 Returns firmware version for the read-only portion of the
76 1 Recovery button.
77 2 Developer mode switch.
121 Returns the SHA-1 or SHA-256 hash that is read out of the
132 Returns offset in CMOS bank 0 of the verified boot non-volatile
142 Return the size in bytes of the verified boot non-volatile
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-mhi | 28 a reset of last resort, and will require a complete re-init.
29 This can be useful as a method of recovery if the device is
30 non-responsive, or as a means of loading new firmware as a
37 Description: Writing a non-zero value to this file will force devices to
38 enter EDL (Emergency Download) mode. This entry only exists for
39 devices capable of entering the EDL mode using the standard EDL
41 mode, the flash programmer image can be downloaded to the
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 10 ----------------------------------
13 faults. There may be fancier recovery schemes that are appropriate in
14 some cases, such as re-initializing (and maybe resetting). After such
15 recovery, triggered by a fault report, there is no error.
27 -------------------------
29 some positive number indicating a non-fault return. The specific
31 though most Linux systems use <asm-generic/errno*.h> numbering.
48 transmit mode: some other master was transmitting different
67 SMBus adapter) needs some fault recovery (such as resetting),
119 or SMBus (or chip-specific) protocol specifications. One
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
4 Design of dm-vdo
7 The dm-vdo (virtual data optimizer) target provides inline deduplication,
8 compression, zero-block elimination, and thin provisioning. A dm-vdo target
12 production environments ever since. It was made open-source in 2017 after
14 dm-vdo. For usage, see vdo.rst in the same directory as this file.
25 The design of dm-vdo is based on the idea that deduplication is a two-part
27 storing multiple copies of those duplicates. Therefore, dm-vdo has two main
34 -------------------
41 design attempts to be lock-free.
[all …]
|
| D | vdo.rst | 1 .. 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/
24 error (either during normal operation or crash recovery) the target will
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
27 mode. The 'vdoforcerebuild' tool, available from the same repo, is used to
28 prepare a read-only vdo to exit read-only mode. After running this tool,
[all …]
|
| D | dm-integrity.rst | 2 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
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
20 disk encryption - if the attacker modifies the encrypted device, an I/O
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | chromeos-acpi-device.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 .. flat-table:: Supported ACPI Objects
13 :header-rows: 1
15 * - Object
16 - Description
18 * - CHSW
19 - Chrome OS switch positions
21 * - HWID
22 - Chrome OS hardware ID
24 * - FWID
[all …]
|
| /Documentation/devicetree/bindings/bus/ |
| D | qcom,ebi2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 external memory (such as NAND or other memory-mapped peripherals) whereas
25 Also CS1 and CS2 has -A and -B signals. Why they have that is unclear to me.
31 CS0 GPIO134 0x1a800000-0x1b000000 (8MB)
32 CS1 GPIO39 (A) / GPIO123 (B) 0x1b000000-0x1b800000 (8MB)
33 CS2 GPIO40 (A) / GPIO124 (B) 0x1b800000-0x1c000000 (8MB)
34 CS3 GPIO133 0x1d000000-0x25000000 (128 MB)
35 CS4 GPIO132 0x1c800000-0x1d000000 (8MB)
[all …]
|
| /Documentation/arch/powerpc/ |
| D | cxlflash.rst | 12 purpose co-processors which can read or write an application's
14 an adapter running in CAPI mode does not require the data buffers to
33 special path for user space access, and performing error recovery. It
40 - Any flash device (LUN) can be configured to be accessed as a
41 regular disk device (i.e.: /dev/sdc). This is the default mode.
43 - Any flash device (LUN) can be configured to be accessed from
44 user space with a special block library. This mode further
47 or physical LUN access) or access to a kernel/AFU-mediated
67 +-------------------------------+
71 +-------------------------------+
[all …]
|
| /Documentation/tee/ |
| D | op-tee.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 OP-TEE (Open Portable Trusted Execution Environment)
7 The OP-TEE driver handles OP-TEE [1] based TEEs. Currently it is only the ARM
8 TrustZone based OP-TEE solution that is supported.
10 Lowest level of communication with OP-TEE builds on ARM SMC Calling
11 Convention (SMCCC) [2], which is the foundation for OP-TEE's SMC interface
12 [3] used internally by the driver. Stacked on top of that is OP-TEE Message
15 OP-TEE SMC interface provides the basic functions required by SMCCC and some
16 additional functions specific for OP-TEE. The most interesting functions are:
18 - OPTEE_SMC_FUNCID_CALLS_UID (part of SMCCC) returns the version information
[all …]
|
| /Documentation/filesystems/ |
| D | nilfs2.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 NILFS2 is a log-structured file system (LFS) supporting continuous
11 like conventional LFS, it achieves quick recovery after system
21 full. Each snapshot is mountable as a read-only file system
25 The userland tools are included in nilfs-utils package, which is
33 :List info: http://vger.kernel.org/vger-lists.html#linux-nilfs
40 - atime
41 - extended attributes
42 - POSIX ACLs
43 - quotas
[all …]
|
| /Documentation/admin-guide/ |
| D | md.rst | 5 ---------------------------------
49 -1 linear mode
50 0 striped mode
58 (raid-0 and raid-1 only)
78 --------------------------------------
87 that all auto-detected arrays are assembled as partitionable.
90 -------------------------------------------
102 mdadm --assemble --force ....
112 md-mod.start_dirty_degraded=1
116 ------------------
[all …]
|
| /Documentation/filesystems/nfs/ |
| D | reexport.rst | 5 --------
15 ---------------------------------
18 filesystem. You can use "uuidgen -r" to generate a unique argument.
25 Reboot recovery
26 ---------------
28 The NFS protocol's normal reboot recovery mechanisms don't work for the
34 -----------------
40 The result must fit into the RFC-mandated filehandle size limits:
42 +-------+-----------+
44 +-------+-----------+
[all …]
|
| /Documentation/arch/parisc/ |
| D | registers.rst | 2 Register Usage for Linux/PA-RISC
11 -----------------
14 CR 0 (Recovery Counter) used for ptrace
15 CR 1-CR 7(undefined) unused
16 CR 8 (Protection ID) per-process value*
23 CR17-CR22 interruption parameters
39 Space Registers (kernel mode)
40 -----------------------------
44 SR4-SR7 set to 0
50 Space Registers (user mode)
[all …]
|
1234