Home
last modified time | relevance | path

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

12

/Documentation/networking/
Dtipc.rst1 .. SPDX-License-Identifier: GPL-2.0
10 TIPC (Transparent Inter Process Communication) is a protocol that is specially
11 designed for intra-cluster communication. It can be configured to transmit
18 -------------
20 - Cluster wide IPC service
23 transmitting data between cluster nodes? Where you yourself determine the
29 Welcome to the Transparent Inter Process Communication service, TIPC in short,
32 - Service Addressing
38 - Service Tracking
45 i.e., subscribing for availability/non-availability of cluster nodes.
[all …]
Deql.rst1 .. SPDX-License-Identifier: GPL-2.0
7 Simon "Guru Aleph-Null" Janes, simon@ncm.com
12 that lets you load-balance IP serial links (SLIP or uncompressed PPP)
27 together to work as one point-to-point link to increase your
32 The eql driver has only been tested with the Livingston PortMaster-2e
33 terminal server. I do not know if other terminal servers support load-
35 almost as well as the eql driver seems to do it (-- Unfortunately, in
36 my testing so far, the Livingston PortMaster 2e's load-balancing is a
40 TCP implementation is pretty fast though.--)
44 a load-balancing client 75% of the cost of the second line and 50% of
[all …]
/Documentation/devicetree/bindings/sound/
Dmicrochip,sama7g5-i2smcc.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/microchip,sama7g5-i2smcc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Microchip I2S Multi-Channel Controller
10 - Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
13 The I2SMCC complies with the Inter-IC Sound (I2S) bus specification and
15 multi-channel audio codecs. It consists of a receiver, a transmitter and a
19 multi-channel is supported by using multiple data pins, output and
23 "#sound-dai-cells":
[all …]
Drockchip-i2s.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/sound/rockchip-i2s.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The I2S bus (Inter-IC sound bus) is a serial link for digital
11 audio data transfer between devices in the system.
14 - Heiko Stuebner <heiko@sntech.de>
17 - $ref: dai-common.yaml#
22 - const: rockchip,rk3066-i2s
23 - items:
[all …]
/Documentation/driver-api/
Di2c.rst5 the "Inter-IC" bus, a simple bus protocol which is widely used where low
6 data rate communications suffice. Since it's also a licensed trademark,
7 some vendors use another name (such as "Two-Wire Interface", TWI) for
8 the same bus. I2C only needs two signals (SCL for clock, SDA for data),
12 I2C is a multi-master bus; open drain signaling is used to arbitrate
38 .. kernel-doc:: include/linux/i2c.h
41 .. kernel-doc:: drivers/i2c/i2c-boardinfo.c
44 .. kernel-doc:: drivers/i2c/i2c-core-base.c
47 .. kernel-doc:: drivers/i2c/i2c-core-smbus.c
Dconnector.rst1 .. SPDX-License-Identifier: GPL-2.0
7 Kernel connector - new netlink based userspace <-> kernel space easy
17 - socket();
18 - bind();
19 - send();
20 - recv();
25 netlink based networking for inter-process communication in a significantly
39 connector.h header for in-kernel usage. `void (*callback) (void *)` is a
51 __u16 len; /* Length of the following data */
53 __u8 data[0];
[all …]
/Documentation/devicetree/bindings/powerpc/nintendo/
Dwii.txt11 - model : Should be "nintendo,wii"
12 - compatible : Should be "nintendo,wii"
16 This node represents the multi-function "Hollywood" chip, which packages
21 - compatible : Should be "nintendo,hollywood"
30 - compatible : should be "nintendo,hollywood-vi","nintendo,flipper-vi"
31 - reg : should contain the VI registers location and length
32 - interrupts : should contain the VI interrupt
36 Represents the data and control interface between the main processor
41 - compatible : should be "nintendo,hollywood-pi","nintendo,flipper-pi"
42 - reg : should contain the PI registers location and length
[all …]
/Documentation/filesystems/nfs/
Dpnfs.rst5 The are several inter-related caches. We have layouts which can
6 reference multiple devices, each of which can reference multiple data servers.
7 Each data server can be referenced by multiple devices. Each device
15 The on-the-wire command LAYOUTGET corresponds to struct
18 segments in nfsi->layout, of type struct pnfs_layout_hdr.
24 Each header is also (when non-empty) put on a list associated with
39 data structure. The hlist size of 32 buckets needs better
47 data server cache
50 file driver devices refer to data servers, which are kept in a module
67 of these types there is a layout-driver with a common function-vectors
[all …]
/Documentation/userspace-api/media/v4l/
Dext-ctrls-codec-stateless.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _codec-stateless-controls:
18 .. _codec-stateless-control-id:
23 .. _v4l2-codec-stateless-h264:
27 bitstream) for the associated H264 slice data. This includes the
30 to :ref:`h264`, section 7.4.2.1.1 "Sequence Parameter Set Data
43 .. flat-table:: struct v4l2_ctrl_h264_sps
44 :header-rows: 0
45 :stub-columns: 0
48 * - __u8
[all …]
/Documentation/devicetree/bindings/media/
Dmediatek,mdp3-rdma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/mediatek,mdp3-rdma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matthias Brugger <matthias.bgg@gmail.com>
11 - Moudy Ho <moudy.ho@mediatek.com>
15 It contains one line buffer to store the sufficient pixel data, and
24 - enum:
25 - mediatek,mt8183-mdp3-rdma
26 - mediatek,mt8188-mdp3-rdma
[all …]
/Documentation/devicetree/bindings/spi/
Dspi-peripheral-props.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/spi/spi-peripheral-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Peripheral-specific properties for a SPI bus.
11 be common properties like spi-max-frequency, spi-cpha, etc. or they could be
12 controller specific like delay in clock or data lines, etc. These properties
13 need to be defined in the peripheral node because they are per-peripheral and
19 - Mark Brown <broonie@kernel.org>
27 - minimum: 0
[all …]
/Documentation/userspace-api/media/
Dglossary.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
23 An API designed to receive and transmit data via an HDMI
28 Data Unit
30 Unit of data transported by a bus. On parallel buses, the data unit
31 consists of one or more related samples while on serial buses the data
32 unit is logical. If the data unit is image data, it may also be called a
41 transfer data in and out of a Kernel driver.
58 **Field-programmable Gate Array**
63 See https://en.wikipedia.org/wiki/Field-programmable_gate_array.
72 together make a larger user-facing functional peripheral. For
[all …]
/Documentation/filesystems/
Dgfs2-glocks.rst1 .. SPDX-License-Identifier: GPL-2.0
13 2. A non-blocking bit lock, GLF_LOCK, which is used to prevent other
44 Glock mode Cache Metadata Cache data Dirty Data Dirty Metadata
61 go_sync Called before remote state change (e.g. to sync dirty data)
108 indicates that it is caching uptodate data.
118 5. Transaction glock (via gfs2_trans_begin) for non-read operations
126 is on a per-inode basis. Locking of rgrps is on a per rgrp basis.
130 ----------------
143 The per-glock counters are initialised to zero when the
144 glock is created. The per-glock statistics are lost when
[all …]
/Documentation/driver-api/media/drivers/
Dipu6.rst1 .. SPDX-License-Identifier: GPL-2.0
34 ------------------------
51 ---------
61 -------------------------------------
76 -----------------
80 Buttress with a copy of the SoC time, this counter maintains the up-to-date time
90 32-bit virtual address space. The IPU6 has MMU address translation hardware to
94 IPU6 driver. The IPU6 driver sets the level-1 page table base address to MMU
101 .. code-block:: none
113 generic PCI DMA ops to ask IOMMU to do the additional mapping if VT-d
[all …]
/Documentation/crypto/
Dasync-tx-api.rst1 .. SPDX-License-Identifier: GPL-2.0
32 bulk memory transfers/transforms with support for inter-transactional
43 xor-parity-calculations of the md-raid5 driver using the offload engines
54 operations to be submitted, like xor->copy->xor in the raid5 case. The
64 -----------------------------
72 ------------------------
85 datap (raid6_datap_recov) recover a raid6 data block and the p block
87 2data (raid6_2data_recov) recover 2 raid6 data blocks from the given
92 -------------------------
94 The return value is non-NULL and points to a 'descriptor' when the operation
[all …]
/Documentation/driver-api/dmaengine/
Dprovider.rst20 DMA-eligible devices to the controller itself. Whenever the device
26 byte of data from one buffer to another, until the transfer size has
31 cycle. For example, we may want to transfer as much data as the
34 that requires data to be written exactly 16 or 24 bits at a time. This
44 transfer into smaller sub-transfers.
47 that involve a single contiguous block of data. However, some of the
48 transfers we usually have are not, and want to copy data from
49 non-contiguous buffers to a contiguous buffer, which is called
50 scatter-gather.
53 scatter-gather. So we're left with two cases here: either we have a
[all …]
/Documentation/sound/soc/
Ddapm.rst11 management frameworks and, as such, can easily co-exist with them.
32 The graph for the STM32MP1-DK1 sound card is shown in picture:
34 .. kernel-figure:: dapm-graph.svg
121 Inter widget audio data buffer within a DSP.
132 Widget that encodes audio data from one format (usually PCM) to another
135 Widget that decodes audio data from a compressed format to an
139 (Widgets are defined in include/sound/soc-dapm.h)
142 There are convenience macros defined in soc-dapm.h that can be used to quickly
150 ---------------------
179 -------------------
[all …]
/Documentation/locking/
Dhwspinlock.rst12 For example, OMAP4 has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP,
17 A generic hwspinlock framework allows platform-independent drivers to use
18 the hwspinlock device in order to access data structures that are shared
22 This is necessary, for example, for Inter-processor communications:
23 on OMAP4, cpu-intensive multimedia tasks are offloaded by the host to the
26 To achieve fast message-based communications, a minimal kernel support
30 This communication is based on simple data structures that is shared between
32 module (remote processor directly places new messages in this shared data
35 A common hwspinlock interface makes it possible to have generic, platform-
67 Retrieve the global lock id for an OF phandle-based specific lock.
[all …]
Dlocktypes.rst1 .. SPDX-License-Identifier: GPL-2.0
15 - Sleeping locks
16 - CPU local locks
17 - Spinning locks
27 --------------
39 - mutex
40 - rt_mutex
41 - semaphore
42 - rw_semaphore
43 - ww_mutex
[all …]
/Documentation/admin-guide/media/
Dbuilding.rst1 .. SPDX-License-Identifier: GPL-2.0
8 distribution-specific source file or via the Kernel's main git tree\ [1]_.
12 - you're a braveheart and want to experiment with new stuff;
13 - if you want to report a bug;
14 - if you're developing new patches
23 https://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
50 Device Drivers --->
51 <M> Remote Controller support --->
54 [*] HDMI CEC drivers --->
55 <*> Multimedia support --->
[all …]
/Documentation/trace/
Dhistogram.rst11 aggregate trace event data into histograms. For information on
33 numeric fields - on an event hit, the value(s) will be added to a
35 in place of an explicit value field - this is simply a count of
45 useful for providing more fine-grained summaries of event data.
51 its histogram data will be shared with other triggers of the same
52 name, and trigger hits will update this common data. Only triggers
69 numeric fields are displayed as base-10 integers. This can be
76 .sym-offset display an address as a symbol and offset
83 .graph display a bar-graph of a value
91 - only the 'hex' modifier can be used for values (because values
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-usb10 This allows to avoid side-effects with drivers
28 drivers, non-authorized one are not. By default, wired
33 Contact: linux-usb@vger.kernel.org
67 What: /sys/bus/usb-serial/drivers/.../new_id
69 Contact: linux-usb@vger.kernel.org
72 extra bus folder "usb-serial" in sysfs; apart from that
97 If CONFIG_PM is set and a USB 2.0 lpm-capable device is plugged
113 If CONFIG_PM is set and a USB 3.0 lpm-capable device is plugged
141 attribute allows user-space to know whether the device is
145 an on-screen keyboard if the only wireless keyboard is
[all …]
/Documentation/arch/arm/
Dcluster-pm-race-avoidance.rst2 Cluster-wide Power-up/power-down race avoidance algorithm
16 ---------
29 cluster-level operations are only performed when it is truly safe to do
35 disabling those mechanisms may itself be a non-atomic operation (such as
38 power-down and power-up at the cluster level.
46 -----------
50 - DOWN
51 - COMING_UP
52 - UP
53 - GOING_DOWN
[all …]
/Documentation/core-api/
Dkernel-api.rst9 .. kernel-doc:: include/linux/list.h
22 ------------------
24 .. kernel-doc:: lib/vsprintf.c
27 .. kernel-doc:: include/linux/kstrtox.h
30 .. kernel-doc:: lib/kstrtox.c
33 .. kernel-doc:: lib/string_helpers.c
37 -------------------
39 .. kernel-doc:: include/linux/fortify-string.h
42 .. kernel-doc:: lib/string.c
45 .. kernel-doc:: include/linux/string.h
[all …]
/Documentation/
Dmemory-barriers.txt19 documentation at tools/memory-model/. Nevertheless, even this memory
37 Note also that it is possible that a barrier may be a no-op for an
48 - Device operations.
49 - Guarantees.
53 - Varieties of memory barrier.
54 - What may not be assumed about memory barriers?
55 - Address-dependency barriers (historical).
56 - Control dependencies.
57 - SMP barrier pairing.
58 - Examples of memory barrier sequences.
[all …]

12