Home
last modified time | relevance | path

Searched +full:data +full:- +full:mirror (Results 1 – 25 of 29) sorted by relevance

12

/Documentation/devicetree/bindings/display/
Dlvds.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - $ref: lvds-data-mapping.yaml#
13 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
14 - Thierry Reding <thierry.reding@gmail.com>
17 This binding extends the data mapping defined in lvds-data-mapping.yaml.
19 to accommodate for even more specialized data formats, since a variety of
20 data formats and layouts is used to drive LVDS displays.
23 data-mirror:
[all …]
/Documentation/admin-guide/device-mapper/
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
12 presents a virtual block device which makes all data appear immediately, and
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
21 For example, one could restore an application backup from a read-only copy,
26 When the cloning completes, the dm-clone table can be removed altogether and be
[all …]
Dkcopyd.rst5 Kcopyd provides the ability to copy a range of sectors from one block-device
6 to one or more other block-devices, with an asynchronous completion
7 notification. It is used by dm-snapshot and dm-mirror.
18 block-device along with the starting sector and size of the region. The source
30 completion callback routine, and a pointer to some context data for the copy::
Ddm-ima.rst2 dm-ima
6 (including the attestation service) interact with it - both during the
7 setup and during rest of the system run-time. They share sensitive data
9 may want to verify the current run-time state of the relevant kernel
10 subsystems before fully trusting the system with business-critical
11 data/workload.
18 impact the security profile of the block device, and in-turn, of the
24 fully trusting the system with business-critical data/workload.
28 various block devices -
30 - by device mapper itself, from within the kernel,
[all …]
Ddm-init.rst5 It is possible to configure a device-mapper device to act as the root device for
11 The second is to create one or more device-mappers using the module parameter
12 "dm-mod.create=" through the kernel boot command line argument.
14 The format is specified as a string of data separated by commas and optionally
15 semi-colons, where:
17 - a comma is used to separate fields like name, uuid, flags and table
19 - a semi-colon is used to separate devices.
23 …dm-mod.create=<name>,<uuid>,<minor>,<flags>,<table>[,<table>+][;<name>,<uuid>,<minor>,<flags>,<tab…
28 <uuid> ::= xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx | ""
35 `--concise` argument.
[all …]
Dcache.rst8 dm-cache is a device mapper target written by Joe Thornber, Heinz
12 dynamically migrating some of its data to a faster, smaller device
15 This device-mapper solution allows us to insert this caching at
16 different levels of the dm stack, for instance above the data device for
17 a thin-provisioning pool. Caching solutions that are integrated more
20 The target reuses the metadata library used in the thin-provisioning
23 The decision as to what data to migrate and when is left to a plug-in
46 Sub-devices
47 -----------
52 1. An origin device - the big, slow one.
[all …]
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/networking/device_drivers/ethernet/marvell/
Docteontx2.rst1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
12 - `Overview`_
13 - `Drivers`_
14 - `Basic packet flow`_
15 - `Devlink health reporters`_
16 - `Quality of service`_
23 PCI-compatible physical and virtual functions. Each functional block
31 - Network pool or buffer allocator (NPA)
32 - Network interface controller (NIX)
33 - Network parser CAM (NPC)
[all …]
/Documentation/arch/m68k/
Dbuddha-driver.rst8 ------------------------------------------------------------------------
11 Buddha-part of the Catweasel Zorro-II version
21 product number: 0 (42 for Catweasel Z-II)
23 Rom-vector: $1000
25 The card should be a Z-II board, size 64K, not for freemem
26 list, Rom-Vektor is valid, no second Autoconfig-board on the
30 as the Amiga Kickstart does: The lower nibble of the 8-Bit
36 otherwise your chance is only 1:16 to find the board :-).
38 The local memory-map is even active when mapped to $e8:
41 $0-$7e Autokonfig-space, see Z-II docs.
[all …]
/Documentation/filesystems/
Dfiemap.rst1 .. SPDX-License-Identifier: GPL-2.0
8 extent mappings. Instead of block-by-block mapping (such as bmap), fiemap
13 --------------
32 which the process would like mappings for. Extents returned mirror
33 those on disk - that is, the logical offset of the 1st returned extent
61 extended attribute lookup tree, instead of its data tree.
65 --------------
93 All offsets and lengths are in bytes and mirror those on disk. It is valid
112 for inline or tail-packed data can key on the specific flag. Software
113 which simply cares not to try operating on non-aligned extents
[all …]
Dubifs-authentication.rst1 .. SPDX-License-Identifier: GPL-2.0
17 is a lost smartphone where the attacker is unable to read personal data stored
24 binary to perform a malicious action when executed [DMC-CBC-ATTACK]. Since
28 Other full disk encryption systems like dm-crypt cover all filesystem metadata,
31 time. For dm-crypt and other filesystems that build upon the Linux block IO
32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
33 can be used to get full data authentication at the block layer.
34 These can also be combined with dm-crypt [CRYPTSETUP2].
44 ----------------
50 addition, it deals with flash-specific wear-leveling and transparent I/O error
[all …]
/Documentation/arch/arm/omap/
Ddss.rst7 TV-out and multiple display support, but there are lots of small improvements
10 The DSS2 driver (omapdss module) is in arch/arm/plat-omap/dss/, and the FB,
15 --------
19 - MIPI DPI (parallel) output
20 - MIPI DSI output in command mode
21 - MIPI DBI (RFBI) output
22 - SDI output
23 - TV output
24 - All pieces can be compiled as a module or inside kernel
25 - Use DISPC to update any of the outputs
[all …]
/Documentation/firmware-guide/acpi/apei/
Doutput_format.rst1 .. SPDX-License-Identifier: GPL-2.0
19 <section data>
30 <section data> :=
31 <generic processor section data> | <memory section data> | \
32 <pcie section data> | <null>
34 <generic processor section data> :=
55 [cache error][, TLB error][, bus error][, micro-architectural error]
57 <proc operation string>* := unknown or generic | data read | data write | \
63 <memory section data> :=
81 unknown | no error | single-bit ECC | multi-bit ECC | \
[all …]
/Documentation/w1/
Dw1-netlink.rst21 [struct cn_msg] - connector header.
22 Its length field is equal to size of the attached data
23 [struct w1_netlink_msg] - w1 netlink header.
24 __u8 type - message type.
37 __u8 status - error indication from kernel
38 __u16 len - size of data attached to this header data
40 __u8 id[8]; - slave unique device id
42 __u32 id; - master's id
43 __u32 res; - reserved
47 [struct w1_netlink_cmd] - command for given master or slave device.
[all …]
/Documentation/admin-guide/media/
Dfimc.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
13 data from LCD controller (FIMD) through the SoC internal writeback data
17 drivers/media/platform/samsung/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
[all …]
/Documentation/input/
Dgameport-programming.rst28 space (is above 0x1000), use that one, and don't map the ISA mirror.
34 Please also consider enabling the gameport on the card in the ->open()
35 callback if the io is mapped to ISA space - this way it'll occupy the io
37 ->close() callback. You also can select the io address in the ->open()
70 the driver doesn't have to measure them the old way - an ADC is built into
86 return -(mode != GAMEPORT_MODE_COOKED);
95 experimentation, it is the amount of noise in the ADC data. Perfect
97 See analog.c and input.c for handling of fuzz - the fuzz value determines
99 in the data.
105 examples 1+2 or 1+3. Gameports can support internal calibration - see below,
[all …]
/Documentation/bpf/libbpf/
Dlibbpf_naming_convention.rst1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
16 --------------------
26 -------
29 and functions to work with them. Objects are high-level abstractions
56 -------------------
63 ---
67 non-static libbpf symbols should have one of the prefixes mentioned in
72 -----------------
78 .. code-block:: c
83 to be a part of ABI what, in turn, improves both libbpf developer- and
[all …]
/Documentation/networking/
Drepresentors.rst1 .. SPDX-License-Identifier: GPL-2.0
9 used to control internal switching on SmartNICs. For the closely-related port
10 representors on physical (multi-port) switches, see
14 ----------
16 Since the mid-2010s, network cards have started offering more complex
17 virtualisation capabilities than the legacy SR-IOV approach (with its simple
18 MAC/VLAN-based switching model) can support. This led to a desire to offload
19 software-defined networks (such as OpenVSwitch) to these NICs to specify the
24 virtual switches and IOV devices. Just as each physical port of a Linux-
35 administrative commands) and a data plane object (one end of a virtual pipe).
[all …]
/Documentation/mm/
Dhmm.rst5 Provide infrastructure and helpers to integrate non-conventional memory (device
21 CPU page-table mirroring works and the purpose of HMM in this context. The
50 For flat data sets (array, grid, image, ...) this isn't too hard to achieve but
51 for complex data sets (list, tree, ...) it's hard to get right. Duplicating a
52 complex data set needs to re-map all the pointer relations between each of its
54 duplicate data set and addresses.
56 Split address space also means that libraries cannot transparently use data
58 might have to duplicate its input data set using the device specific memory
95 two-way cache coherency between CPU and device and allow all atomic operations the
115 allocate a buffer (or use a pool of pre-allocated buffers) and write GPU
[all …]
/Documentation/userspace-api/media/v4l/
Dcontrol.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 Devices typically have a number of user-settable controls such as
21 pre-defined control IDs have the prefix ``V4L2_CID_``, and are listed in
22 :ref:`control-id`. The ID is used when querying the attributes of a
27 the user is supposed to understand. When the purpose is non-intuitive
28 the driver writer should provide a user manual, a user interface plug-in
57 .. _control-id:
127 Whiteness for grey-scale devices. This is a synonym for
146 .. _v4l2-cid-hflip:
149 Mirror the picture horizontally.
[all …]
/Documentation/PCI/
Dpci.rst1 .. SPDX-License-Identifier: GPL-2.0
7 :Authors: - Martin Mares <mj@ucw.cz>
8 - Grant Grundler <grundler@parisc-linux.org>
11 Since each CPU architecture implements different chip-sets and PCI devices
18 by Jonathan Corbet, Alessandro Rubini, and Greg Kroah-Hartman.
26 "Linux PCI" <linux-pci@atrey.karlin.mff.cuni.cz> mailing list.
38 supporting hot-pluggable PCI, CardBus, and Express-Card in a single driver].
45 - Enable the device
46 - Request MMIO/IOP resources
47 - Set the DMA mask size (for both coherent and streaming DMA)
[all …]
/Documentation/driver-api/
Dmtdnand.rst10 The generic NAND driver supports almost all NAND and AG-AND based chips
31 --------------------------
37 - [MTD Interface]
43 - [NAND Interface]
48 - [GENERIC]
53 - [DEFAULT]
65 -------------------------------
71 - [INTERN]
77 - [REPLACEABLE]
86 - [BOARDSPECIFIC]
[all …]
/Documentation/admin-guide/RAS/
Dmain.rst1 .. SPDX-License-Identifier: GPL-2.0
37 -------------
43 it causes data loss or system downtime.
49 * I/O – add CRC checksums for transferred data;
51 Self-Monitoring, Analysis and Reporting Technology (SMART).
59 ---------------
72 * **Correctable Error (CE)** - the error detection mechanism detected and
76 * **Uncorrected Error (UE)** - the amount of errors happened above the error
77 correction threshold, and the system was unable to auto-correct.
79 * **Fatal Error** - when an UE error happens on a critical component of the
[all …]
/Documentation/admin-guide/
Ddevices.txt1 0 Unnamed devices (e.g. non-device mounts)
7 2 = /dev/kmem OBSOLETE - replaced by /proc/kcore
11 6 = /dev/core OBSOLETE - replaced by /proc/kcore
18 12 = /dev/oldmem OBSOLETE - replaced by /proc/vmcore
31 2 char Pseudo-TTY masters
37 Pseudo-tty's are named as follows:
40 the 1st through 16th series of 16 pseudo-ttys each, and
44 These are the old-style (BSD) PTY devices; Unix98
106 3 char Pseudo-TTY slaves
112 These are the old-style (BSD) PTY devices; Unix98
[all …]
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 …]

12