Home
last modified time | relevance | path

Searched +full:layer +full:- +full:buffer +full:- +full:offset (Results 1 – 25 of 43) sorted by relevance

12

/Documentation/devicetree/bindings/display/
Dxylon,logicvc-display.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/display/xylon,logicvc-display.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Paul Kocialkowski <paul.kocialkowski@bootlin.com>
16 with Xilinx Zynq-7000 SoCs and Xilinx FPGAs.
20 synthesis time. As a result, many of the device-tree bindings are meant to
24 Layers are declared in the "layers" sub-node and have dedicated configuration.
25 In version 3 of the controller, each layer has fixed memory offset and address
32 - xylon,logicvc-3.02.a-display
[all …]
/Documentation/networking/
Dstrparser.rst1 .. SPDX-License-Identifier: GPL-2.0
11 application layer protocol running over a data stream. The stream
12 parser works in conjunction with an upper layer in the kernel to provide
13 kernel support for application layer messages. For instance, Kernel
47 strparser that is allocated by the upper layer. sk is the TCP
57 and no new messages are delivered to the upper layer.
71 error, and it is called from the upper layer to stop parsing
98 The upper layer calls strp_tcp_data_ready when data is ready on
102 buffer and message timeout is the receive timeout for the socket.
122 in the stream. The upper layer must implement this function. It
[all …]
Dtls.rst10 Transport Layer Security (TLS) is a Upper Layer Protocol (ULP) that runs over
11 TCP. TLS provides end-to-end data integrity and confidentiality.
17 -------------------------
21 .. code-block:: c
29 data-path to the kernel. There is a separate socket option for moving
32 .. code-block:: c
65 ----------------------------
71 .. code-block:: c
76 send() data is directly encrypted from the userspace buffer provided
77 to the encrypted kernel send buffer if possible.
[all …]
Doa-tc6-framework.rst1 .. SPDX-License-Identifier: GPL-2.0+
4 OPEN Alliance 10BASE-T1x MAC-PHY Serial Interface (TC6) Framework Support
8 ------------
11 single pair of conductors. The 10BASE-T1L (Clause 146) is a long reach
12 PHY supporting full duplex point-to-point operation over 1 km of single
13 balanced pair of conductors. The 10BASE-T1S (Clause 147) is a short reach
14 PHY supporting full / half duplex point-to-point operation over 15 m of
18 Furthermore, the IEEE 802.3cg project defines the new Physical Layer
21 works in conjunction with the 10BASE-T1S PHY operating in multidrop mode.
23 The aforementioned PHYs are intended to cover the low-speed / low-cost
[all …]
Dtimestamping.rst1 .. SPDX-License-Identifier: GPL-2.0
43 -------------------------------------------------------------
59 -------------------------------------------------------------------
72 ----------------------------------------------------------------------
130 a timestamp is generated at each layer. This allows for fine
135 Request tx timestamps when all data in the send buffer has been
138 over-report measurement, because the timestamp is generated when all
139 data up to and including the buffer at send() was acknowledged: the
181 is derived from a per-socket u32 counter (that wraps). For datagram
208 a timestamp with counter N-1. SOF_TIMESTAMPING_OPT_ID_TCP
[all …]
Dip-sysctl.rst1 .. SPDX-License-Identifier: GPL-2.0
10 ip_forward - BOOLEAN
11 - 0 - disabled (default)
12 - not 0 - enabled
20 ip_default_ttl - INTEGER
25 ip_no_pmtu_disc - INTEGER
27 fragmentation-required ICMP is received, the PMTU to this
38 accept fragmentation-needed errors if the underlying protocol
48 Possible values: 0-3
52 min_pmtu - INTEGER
[all …]
/Documentation/core-api/
Dswiotlb.rst1 .. SPDX-License-Identifier: GPL-2.0
7 swiotlb is a memory buffer allocator used by the Linux kernel DMA layer. It is
9 buffer because of hardware limitations or other requirements. In such a case,
10 the DMA layer calls swiotlb to allocate a temporary memory buffer that conforms
11 to the limitations. The DMA is done to/from this temporary memory buffer, and
12 the CPU copies the data between the temporary buffer and the original target
13 memory buffer. This approach is generically called "bounce buffering", and the
14 temporary memory buffer is called a "bounce buffer".
17 the DMA layer of the DMA attributes of the devices they are managing, and use
19 These APIs use the device DMA attributes and kernel-wide settings to determine
[all …]
/Documentation/userspace-api/media/v4l/
Dext-ctrls-codec.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _codec-controls:
24 .. _mpeg-control-id:
27 -----------------
35 .. _v4l2-mpeg-stream-type:
40 enum v4l2_mpeg_stream_type -
41 The MPEG-1, -2 or -4 output stream type. One cannot assume anything
48 .. flat-table::
49 :header-rows: 0
50 :stub-columns: 0
[all …]
Dlibv4l-introduction.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _libv4l-introduction:
10 libv4l is a collection of libraries which adds a thin abstraction layer
11 on top of video4linux2 devices. The purpose of this (thin) layer is to
17 :ref:`v4l2grab <v4l2grab-example>`.
28 :ref:`V4L2_PIX_FMT_BGR24 <V4L2-PIX-FMT-BGR24>`,
29 :ref:`V4L2_PIX_FMT_NV12_16L16 <V4L2-PIX-FMT-NV12-16L16>`,
30 :ref:`V4L2_PIX_FMT_JPEG <V4L2-PIX-FMT-JPEG>`,
31 :ref:`V4L2_PIX_FMT_MJPEG <V4L2-PIX-FMT-MJPEG>`,
32 :ref:`V4L2_PIX_FMT_MR97310A <V4L2-PIX-FMT-MR97310A>`,
[all …]
Dhist-v4l2.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _hist-v4l2:
21 1998-08-20: First version.
23 1998-08-27: The :c:func:`select()` function was introduced.
25 1998-09-10: New video standard interface.
27 1998-09-18: The ``VIDIOC_NONCAP`` ioctl was replaced by the otherwise
36 1998-09-28: Revamped video standard. Made video controls individually
39 1998-10-02: The ``id`` field was removed from
47 1998-11-08: Many minor changes. Most symbols have been renamed. Some
50 1998-11-12: The read/write direction of some ioctls was misdefined.
[all …]
/Documentation/filesystems/iomap/
Ddesign.rst1 .. SPDX-License-Identifier: GPL-2.0
23 1. A lower layer that provides an iterator over ranges of file offsets.
24 This layer tries to obtain mappings of each file ranges to storage
28 2. An upper layer that acts upon the space mappings provided by the
29 lower layer iterator.
31 The iteration can involve mappings of file's logical offset ranges to
32 physical extents, but the storage layer information is not necessarily
78 1. Obtain a space mapping via ``->iomap_begin``
80 2. For each sub-unit of work...
89 4. Release the mapping via ``->iomap_end``, if necessary
[all …]
/Documentation/networking/device_drivers/ethernet/netronome/
Dnfp.rst1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
14 - `Overview`_
15 - `Acquiring Firmware`_
16 - `Devlink Info`_
17 - `Configure Device`_
18 - `Statistics`_
25 are also incorporated in the companies' family of Agilio SmartNICs. The SR-IOV
35 Firmware files on the host filesystem contain card type (`AMDA-*` string), media
40 `linux-firmware.git` repository.
46 -----------------
[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/gpu/
Ddrm-mm.rst6 frame buffers, textures, vertices and other graphics-related data. Given
13 manager to be developed and tried to be a one-size-fits-them all
20 GEM started as an Intel-sponsored project in reaction to TTM's
22 providing a solution to every graphics memory-related problems, GEM
31 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_module.c
34 .. kernel-doc:: include/drm/ttm/ttm_caching.h
38 ---------------------------
40 .. kernel-doc:: include/drm/ttm/ttm_device.h
43 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_device.c
47 --------------------------------
[all …]
/Documentation/trace/
Dkprobetrace.rst2 Kprobe-based Event Tracing
8 --------
9 These events are similar to tracepoint-based events. Instead of tracepoints,
13 Unlike the tracepoint-based event, this can be added and removed
28 -------------------------
34 -:[GRP/][EVENT] : Clear a probe
40 SYM[+offs] : Symbol+offset where the probe is inserted.
50 @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol)
56 +|-[u]OFFS(FETCHARG) : Fetch memory at FETCHARG +|- OFFS address.(\*3)(\*4)
61 (x8/x16/x32/x64), VFS layer common type(%pd/%pD), "char",
[all …]
Devents.rst17 tracing information is saved into the tracing buffer, and how the
24 ---------------------------------
59 ---------------------------
82 - 0 - all events this file affects are disabled
83 - 1 - all events this file affects are enabled
84 - X - there is a mixture of events enabled and disabled
85 - ? - this file does not affect any event
88 ---------------
92 trace_event=[event-list]
94 event-list is a comma separated list of events. See section 2.1 for event
[all …]
/Documentation/filesystems/
Dcoda.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Coda Kernel-Venus Interface
10 Coda -- this document describes the client kernel-Venus interface.
35 level filesystem code needed for the operation of the Coda file sys-
45 3. The message layer
102 filesystem, requests are directed at the filesystem layer in the
124 leads to an almost natural environment for implementing a kernel-level
148 filesystem (VFS) layer, which is named I/O Manager in NT and IFS
153 pre-processing, the VFS starts invoking exported routines in the FS
158 The FS layer for Coda must expose and implement several interfaces.
[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 --------------
58 This directory contains the middle layer which is the heart of ALSA
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
[all …]
/Documentation/target/
Dtcmu-design.rst19 2) Writing a user pass-through handler
29 TCM is another name for LIO, an in-kernel iSCSI target (server).
38 built-in modules are implemented entirely as kernel code.
41 ----------
52 use case that other non-kernel target solutions, such as tgt, are able
55 in these non-traditional networked storage systems, while still only
65 kernel, another approach is to create a userspace pass-through
70 --------
75 (Filesystem in Userspace), but at the SCSI layer instead of the
76 filesystem layer. A SUSE, if you will.
[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/userspace-api/
Dperf_ring_buffer.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Perf ring buffer
11 2. Ring buffer implementation
13 2.2 Ring buffer for different tracing modes
15 2.2.2 Per-thread mode
16 2.2.3 Per-CPU mode
18 2.3 Accessing buffer
19 2.3.1 Producer-consumer model
21 2.3.3 Writing samples into buffer
22 2.3.4 Reading samples from buffer
[all …]
/Documentation/block/
Dublk.rst1 .. SPDX-License-Identifier: GPL-2.0
13 new virtual block device such as ublk-qcow2 (there are several attempts of
18 - They can be written many programming languages.
19 - They can use libraries that are not available in the kernel.
20 - They can be debugged with tools familiar to application developers.
21 - Crashes do not kernel panic the machine.
22 - Bugs are likely to have a lower security impact than bugs in kernel
24 - They can be installed and updated independently of the kernel.
25 - They can be used to simulate block device easily with user specified
42 ``/dev/ublkb*`` is driven by blk-mq request-based driver. Each request is
[all …]
/Documentation/networking/device_drivers/ethernet/intel/
Di40e.rst1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 1999-2018 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Intel(R) Ethernet Flow Director
16 - Additional Configurations
17 - Known Issues
18 - Support
47 ----------------------
49 …intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-m…
[all …]
Dice.rst1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 2018-2021 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Important Notes
16 - Additional Features & Configurations
17 - Performance Optimization
28 This driver supports XDP (Express Data Path) and AF_XDP zero-copy. Note that
43 -------------------------------------------
54 1) Make sure that your system's physical memory is in a high-performance
[all …]
/Documentation/arch/powerpc/
Dcxl.rst28 +----------+ +---------+
34 +----------+ +---------+
36 | +------+ | PSL |
37 | | CAPP |<------>| |
38 +---+------+ PCIE +---------+
46 The POWER Service Layer (PSL) and the Accelerator Function Unit
65 - POWER8 and PSL Version 8 are compliant to the CAIA Version 1.0.
66 - POWER9 and PSL Version 9 are compliant to the CAIA Version 2.0.
105 the kernel can determine the offset and size of the per context
123 The WED is a 64-bit parameter passed to the AFU when a context is
[all …]

12