Searched +full:data +full:- +full:mapping (Results 1 – 25 of 315) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/display/ |
| D | lvds-data-mapping.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/lvds-data-mapping.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: LVDS Data Mapping
10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 LVDS is a physical layer specification defined in ANSI/TIA/EIA-644-A. Multiple
15 incompatible data link layers have been used over time to transmit image data
19 [JEIDA] "Digital Interface Standards for Monitor", JEIDA-59-1999, February
[all …]
|
| D | lvds.yaml | 1 # 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/trace/ |
| D | ring-buffer-map.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Tracefs ring-buffer memory mapping
11 Tracefs ring-buffer memory map provides an efficient method to stream data
12 as no memory copy is necessary. The application mapping the ring-buffer becomes
13 then a consumer for that ring-buffer, in a similar fashion to trace_pipe.
15 Memory mapping setup
17 The mapping works with a mmap() of the trace_pipe_raw interface.
19 The first system page of the mapping contains ring-buffer statistics and
20 description. It is referred to as the meta-page. One of the most important
21 fields of the meta-page is the reader. It contains the sub-buffer ID which can
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 2 dm-zoned
5 The dm-zoned device mapper target exposes a zoned block device (ZBC and
7 pattern constraints. In effect, it implements a drive-managed zoned
10 host-managed zoned block devices and can mitigate the potential
11 device-side performance degradation due to excessive random writes on
12 host-aware zoned block devices.
21 http://www.t13.org/Documents/UploadedDocuments/docs2015/di537r05-Zoned_Device_ATA_Command_Set_ZAC.p…
23 The dm-zoned implementation is simple and minimizes system overhead (CPU
25 host-managed disk with 256 MB zones, dm-zoned memory usage per disk
29 dm-zoned target devices are formatted and checked using the dmzadm
[all …]
|
| 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
26 problem. The first is to recognize duplicate data. The second is to avoid
27 storing multiple copies of those duplicates. Therefore, dm-vdo has two main
29 duplicate data, and a data store with a reference counted block map that
[all …]
|
| /Documentation/filesystems/iomap/ |
| D | design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
70 of mapping function calls into the filesystem across a larger amount of
71 data.
78 1. Obtain a space mapping via ``->iomap_begin``
80 2. For each sub-unit of work...
82 1. Revalidate the mapping and go back to (1) above, if necessary.
89 4. Release the mapping via ``->iomap_end``, if necessary
105 -----------
127 device pre-shutdown hook from returning before other threads have
130 * **filesystem mapping lock**: This synchronization primitive is
[all …]
|
| D | porting.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 into the filesystem to return a mapping for only that page.
27 This worked well enough for direct/indirect-mapped filesystems such
28 as ext2, but is very inefficient for extent-based filesystems such
34 3. Direct access to storage on memory-like devices (fsdax) is only
40 No ->write_begin(), ->write_end() or direct_IO
49 Build the kernel, run fstests with the ``-g all`` option across a wide
53 The recommended approach is first to implement ``->iomap_begin`` (and
54 ``->iomap_end`` if necessary) to allow iomap to obtain a read-only
55 mapping of a file range.
[all …]
|
| D | operations.rst | 1 .. SPDX-License-Identifier: GPL-2.0
32 mapping, managing uptodate and dirty state, or writeback of pagecache
35 linked lists of buffer heads instead of the per-folio bitmaps that iomap
42 -----------------------------------
61 --------------------------
63 The ``->iomap_begin`` function for pagecache operations may set the
67 .. code-block:: c
79 - ``get_folio``: Called to allocate and return an active reference to
83 This could be used to `set up per-folio filesystem state
84 <https://lore.kernel.org/all/20190429220934.10415-5-agruenba@redhat.com/>`_
[all …]
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | sgd,gktw70sdae4se.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Neil Armstrong <neil.armstrong@linaro.org>
11 - Thierry Reding <thierry.reding@gmail.com>
14 - $ref: panel-common.yaml#
15 - $ref: /schemas/display/lvds.yaml#
24 - compatible
29 - const: sgd,gktw70sdae4se
30 - const: panel-lvds
[all …]
|
| D | advantech,idk-1110wr.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/panel/advantech,idk-1110wr.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Advantech IDK-1110WR 10.1" WSVGA LVDS Display Panel
10 - Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 - $ref: panel-common.yaml#
15 - $ref: /schemas/display/lvds.yaml#
21 const: advantech,idk-1110wr
[all …]
|
| D | mitsubishi,aa104xd12.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 - $ref: panel-common.yaml#
15 - $ref: /schemas/display/lvds.yaml#
24 - compatible
29 - const: mitsubishi,aa104xd12
30 - const: panel-lvds
[all …]
|
| D | mitsubishi,aa121td01.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 - $ref: panel-common.yaml#
15 - $ref: /schemas/display/lvds.yaml#
24 - compatible
29 - const: mitsubishi,aa121td01
30 - const: panel-lvds
[all …]
|
| D | innolux,ee101ia-01d.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/panel/innolux,ee101ia-01d.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Innolux Corporation 10.1" EE101IA-01D WXGA (1280x800) LVDS panel
10 - Heiko Stuebner <heiko.stuebner@bq.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 - $ref: panel-common.yaml#
15 - $ref: /schemas/display/lvds.yaml#
21 const: innolux,ee101ia-01d
[all …]
|
| D | advantech,idk-2121wr.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/panel/advantech,idk-2121wr.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Advantech IDK-2121WR 21.5" Full-HD dual-LVDS panel
10 - Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 The IDK-2121WR from Advantech is a Full-HD dual-LVDS panel.
15 A dual-LVDS interface is a dual-link connection with even pixels traveling
20 dual-lvds-odd-pixels or dual-lvds-even-pixels).
[all …]
|
| /Documentation/filesystems/ |
| D | fiemap.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 extent mappings. Instead of block-by-block mapping (such as bmap), fiemap
13 --------------
19 * which to start mapping (in) */
20 __u64 fm_length; /* logical length of mapping which
33 those on disk - that is, the logical offset of the 1st returned extent
51 fm_extents[] to hold the file's current mapping. Note that there is
57 If this flag is set, the kernel will sync the file before mapping extents.
61 extended attribute lookup tree, instead of its data tree.
64 Extent Mapping
[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 …]
|
| /Documentation/core-api/ |
| D | dma-api-howto.rst | 2 Dynamic DMA mapping Guide
10 with example pseudo-code. For a concise description of the API, see
11 Documentation/core-api/dma-api.rst.
39 supports 64-bit addresses for main memory and PCI BARs, it may use an IOMMU
40 so devices only need to use 32-bit DMA addresses.
49 +-------+ +------+ +------+
52 C +-------+ --------> B +------+ ----------> +------+ A
53 | | mapping | | by host | |
54 +-----+ | | | | bridge | | +--------+
55 | | | | +------+ | | | |
[all …]
|
| D | dma-api.rst | 2 Dynamic DMA mapping using the generic device
8 of the API (and actual examples), see Documentation/core-api/dma-api-howto.rst.
11 Part II describes extensions for supporting non-consistent memory
13 non-consistent platforms (this is usually only legacy platforms) you
16 Part I - dma_API
17 ----------------
19 To get the dma_API, you must #include <linux/dma-mapping.h>. This
27 Part Ia - Using large DMA-coherent buffers
28 ------------------------------------------
76 Part Ib - Using small DMA-coherent buffers
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | ifork.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------------------
16 maps will be used to allocate data blocks to store the link target.
22 means of an (up to) three level 1-1 block map. To find the logical block
36 Note that with this block mapping scheme, it is necessary to fill out a
37 lot of mapping data even for a large contiguous file! This inefficiency
38 led to the creation of the extent mapping scheme, discussed below.
40 Notice also that a file using this mapping scheme cannot be placed
49 mapping is reduced to a single ``struct ext4_extent`` with
63 point to the file's data blocks. The root node of the extent tree is
[all …]
|
| /Documentation/devicetree/bindings/display/imx/ |
| D | ldb.txt | 1 Device-Tree bindings for LVDS Display Bridge (ldb)
6 The LVDS Display Bridge device tree node contains up to two lvds-channel
10 - #address-cells : should be <1>
11 - #size-cells : should be <0>
12 - compatible : should be "fsl,imx53-ldb" or "fsl,imx6q-ldb".
16 - gpr : should be <&gpr> on i.MX53 and i.MX6q.
17 The phandle points to the iomuxc-gpr region containing the LVDS
19 - clocks, clock-names : phandles to the LDB divider and selector clocks and to
21 Documentation/devicetree/bindings/clock/clock-bindings.txt
23 "di0_pll" - LDB LVDS channel 0 mux
[all …]
|
| /Documentation/mm/ |
| D | remap_file_pages.rst | 5 The remap_file_pages() system call is used to create a nonlinear mapping,
6 that is, a mapping in which the pages of the file are mapped into a
9 require the kernel to create additional VMA (Virtual Memory Area) data
12 Supporting of nonlinear mapping requires significant amount of non-trivial
14 nonlinear mapping work kernel need a way to distinguish normal page table
21 on 32-bit systems to map files bigger than can linearly fit into 32-bit
22 virtual address space. This use-case is not critical anymore since 64-bit
|
| D | highmem.rst | 18 The part of (physical) memory not covered by a permanent mapping is what we
30 +--------+ 0xffffffff
32 +--------+ 0xc0000000
36 +--------+ 0x00000000
39 time, but because we need virtual address space for other things - including
40 temporary maps to access the rest of the physical memory - the actual direct
54 * kmap_local_page(), kmap_local_folio() - These functions are used to create
64 These mappings are thread-local and CPU-local, meaning that the mapping
66 CPU while the mapping is active. Although preemption is never disabled by
68 CPU-hotplug until the mapping is disposed.
[all …]
|
| /Documentation/filesystems/xfs/ |
| D | xfs-online-fsck-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 Mapping of heading styles within this document:
8 Heading 3 uses "----"
25 - To help kernel distributors understand exactly what the XFS online fsck
28 - To help people reading the code to familiarize themselves with the relevant
31 - To help developers maintaining the system by capturing the reasons
59 - Provide a hierarchy of names through which application programs can associate
60 arbitrary blobs of data for any length of time,
62 - Virtualize physical storage media across those names, and
64 - Retrieve the named data blobs at any time.
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
7 mapping is made use of in conjunction with the mmap() system call, the shmat()
9 mapping is actually performed by the binfmt drivers, which call back into the
12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
19 (#) Anonymous mapping, MAP_PRIVATE
21 In the MMU case: VM regions backed by arbitrary pages; copy-on-write
24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
27 (#) Anonymous mapping, MAP_SHARED
[all …]
|
12345678910>>...13