| /kernel/linux/linux-5.10/drivers/media/cec/platform/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
14 The CEC bus is present in the HDMI connector and enables communication
15 between compatible devices.
25 CEC bus is present in the HDMI connector and enables communication
37 This driver if for the new AO-CEC module found in G12A SoCs,
38 usually named AO_CEC_B in documentation.
40 CEC bus is present in the HDMI connector and enables communication
41 between compatible devices.
44 tristate "Generic GPIO-based CEC driver"
51 This is a generic GPIO-based CEC driver.
[all …]
|
| /kernel/linux/linux-5.10/drivers/mailbox/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
5 Mailbox is a framework to control hardware communication between
6 on-chip processors through queued messages and interrupt driven
17 used in Secure mode only.
33 which can be used in Secure mode only.
41 send short messages between Highbank's A9 cores and the EnergyCore
51 running on the Cortex-M3 rWTM secure processor of the Armada 37xx
60 interprocessor communication involving DSP, IVA1.0 and IVA2 in
61 OMAP2/3; or IPU, IVA HD and DSP in OMAP4/5. Say Y here if you
77 This driver provides support for inter-processor communication
[all …]
|
| /kernel/linux/linux-4.19/drivers/mailbox/ |
| D | Kconfig | 4 Mailbox is a framework to control hardware communication between
5 on-chip processors through queued messages and interrupt driven
16 used in Secure mode only.
32 which can be used in Secure mode only.
40 send short messages between Highbank's A9 cores and the EnergyCore
49 interprocessor communication involving DSP, IVA1.0 and IVA2 in
50 OMAP2/3; or IPU, IVA HD and DSP in OMAP4/5. Say Y here if you
66 This driver provides support for inter-processor communication
67 between CPU cores and MCU processor on Some Rockchip SOCs.
77 between the OS and a platform such as the BMC. This medium
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | percpu-refcount.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
7 * This implements a refcount with similar semantics to atomic_t - atomic_inc(),
8 * atomic_dec_and_test() - but percpu.
10 * There's one important difference between percpu refs and normal atomic_t
15 * The refcount will have a range of 0 to ((1U << 31) - 1), i.e. one bit less
16 * than an atomic_t - this is because of the way shutdown works, see
20 * refcount hitting 0 - it can't, if it was in percpu mode. percpu_ref_kill()
21 * puts the ref back in single atomic_t mode, collecting the per cpu refs and
32 * In the aio code, kill_ioctx() is called when we wish to destroy a kioctx; it
44 * once - percpu_ref_kill() does this for you, it returns true once and false if
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | percpu-refcount.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
7 * This implements a refcount with similar semantics to atomic_t - atomic_inc(),
8 * atomic_dec_and_test() - but percpu.
10 * There's one important difference between percpu refs and normal atomic_t
15 * The refcount will have a range of 0 to ((1U << 31) - 1), i.e. one bit less
16 * than an atomic_t - this is because of the way shutdown works, see
20 * refcount hitting 0 - it can't, if it was in percpu mode. percpu_ref_kill()
21 * puts the ref back in single atomic_t mode, collecting the per cpu refs and
32 * In the aio code, kill_ioctx() is called when we wish to destroy a kioctx; it
44 * once - percpu_ref_kill() does this for you, it returns true once and false if
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/ |
| D | device_connection.rst | 6 ------------
15 Device connections are generic descriptions of any type of connection between
18 Device connections alone do not create a dependency between the two devices.
20 A dependency between the two devices exists only if one of the two endpoint
22 defined in firmware (not yet supported) or they can be built-in.
25 -----
27 Device connections should exist before device ``->probe`` callback is called for
28 either endpoint device in the description. If the connections are defined in
30 descriptions are "built-in", and need to be added separately.
34 is needed if there are multiple connections between the two devices.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | field-order.rst | 1 .. -*- coding: utf-8; mode: rst -*-
3 .. _field-order:
9 We have to distinguish between progressive and interlaced video.
13 odd and even field are transmitted, and due to a small delay between
22 fields are in fact captured at two different instances in time. An
23 object on screen may well move between one field and the next. For
29 combine to frames. We distinguish between top (aka odd) and bottom (aka
43 determined by the video standard. Hence the distinction between temporal
62 .. flat-table::
63 :header-rows: 0
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 4 provide a glue-less interface to a variety of asynchronous memory devices like
11 Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
12 OMAP-L138 (DA850) - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
13 Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
17 - compatible: "ti,davinci-aemif"
18 "ti,keystone-aemif"
19 "ti,da850-aemif"
21 - reg: contains offset/length value for AEMIF control registers
24 - #address-cells: Must be 2. The partition number has to be encoded in the
25 first address cell and it may accept values 0..N-1
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 4 provide a glue-less interface to a variety of asynchronous memory devices like
11 Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
12 OMAP-L138 (DA850) - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
13 Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
17 - compatible: "ti,davinci-aemif"
18 "ti,keystone-aemif"
19 "ti,da850-aemif"
21 - reg: contains offset/length value for AEMIF control registers
24 - #address-cells: Must be 2. The partition number has to be encoded in the
25 first address cell and it may accept values 0..N-1
[all …]
|
| /kernel/linux/linux-5.10/Documentation/input/ |
| D | multi-touch-protocol.rst | 4 Multi-touch (MT) Protocol
7 :Copyright: |copy| 2009-2010 Henrik Rydberg <rydberg@euromail.se>
11 ------------
13 In order to utilize the full power of the new multi-touch and multi-user
15 objects in direct contact with the device surface, is needed. This
16 document describes the multi-touch (MT) protocol which allows kernel
30 --------------
34 packet. Since these events are ignored by current single-touch (ST)
36 in an existing driver.
48 All drivers mark the end of a multi-touch transfer by calling the usual
[all …]
|
| /kernel/linux/linux-4.19/Documentation/input/ |
| D | multi-touch-protocol.rst | 4 Multi-touch (MT) Protocol
7 :Copyright: |copy| 2009-2010 Henrik Rydberg <rydberg@euromail.se>
11 ------------
13 In order to utilize the full power of the new multi-touch and multi-user
15 objects in direct contact with the device surface, is needed. This
16 document describes the multi-touch (MT) protocol which allows kernel
30 --------------
34 packet. Since these events are ignored by current single-touch (ST)
36 in an existing driver.
48 All drivers mark the end of a multi-touch transfer by calling the usual
[all …]
|
| /kernel/linux/linux-5.10/net/dccp/ccids/lib/ |
| D | packet_history.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
4 * Copyright (c) 2005-7 The University of Waikato, Hamilton, New Zealand.
10 * or e-mail Ian McDonald - ian.mcdonald@jandi.co.nz
14 * Copyright (c) 2003 Nils-Erik Mattsson, Joacim Haggmark, Magnus Erixzon
17 * and to make it work as a loadable module in the DCCP stack written by
38 return tfrc_tx_hist_slab == NULL ? -ENOBUFS : 0; in tfrc_tx_packet_history_init()
54 return -ENOBUFS; in tfrc_tx_hist_add()
55 entry->seqno = seqno; in tfrc_tx_hist_add()
56 entry->stamp = ktime_get_real(); in tfrc_tx_hist_add()
57 entry->next = *headp; in tfrc_tx_hist_add()
[all …]
|
| /kernel/linux/linux-4.19/net/dccp/ccids/lib/ |
| D | packet_history.c | 3 * Copyright (c) 2005-7 The University of Waikato, Hamilton, New Zealand.
9 * or e-mail Ian McDonald - ian.mcdonald@jandi.co.nz
13 * Copyright (c) 2003 Nils-Erik Mattsson, Joacim Haggmark, Magnus Erixzon
16 * and to make it work as a loadable module in the DCCP stack written by
26 * This program is distributed in the hope that it will be useful,
51 return tfrc_tx_hist_slab == NULL ? -ENOBUFS : 0; in tfrc_tx_packet_history_init()
67 return -ENOBUFS; in tfrc_tx_hist_add()
68 entry->seqno = seqno; in tfrc_tx_hist_add()
69 entry->stamp = ktime_get_real(); in tfrc_tx_hist_add()
70 entry->next = *headp; in tfrc_tx_hist_add()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | coresight-cti.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/coresight-cti.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 to one or more CoreSight components and/or a CPU, with CTIs interconnected in
15 not part of the CoreSight graph described in the general CoreSight bindings
18 The CTI component properties define the connections between the individual
22 number is defined at design time, the maximum of each defined in the DEVID
25 CTIs are interconnected in a star topology via the CTM, using a number of
27 described in the DEVID register. The star topology is not required to be
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mtd/ |
| D | cadence-quadspi.txt | 4 - compatible : should be one of the following:
5 Generic default - "cdns,qspi-nor".
6 For TI 66AK2G SoC - "ti,k2g-qspi", "cdns,qspi-nor".
7 - reg : Contains two entries, each of which is a tuple consisting of a
11 - interrupts : Unit interrupt specifier for the controller interrupt.
12 - clocks : phandle to the Quad SPI clock.
13 - cdns,fifo-depth : Size of the data FIFO in words.
14 - cdns,fifo-width : Bus width of the data FIFO in bytes.
15 - cdns,trigger-address : 32-bit indirect AHB trigger address.
18 - cdns,is-decoded-cs : Flag to indicate whether decoder is used or not.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | field-order.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _field-order:
9 We have to distinguish between progressive and interlaced video.
13 odd and even field are transmitted, and due to a small delay between
22 fields are in fact captured at two different instances in time. An
23 object on screen may well move between one field and the next. For
29 combine to frames. We distinguish between top (aka odd) and bottom (aka
43 determined by the video standard. Hence the distinction between temporal
47 In V4L it is assumed that all video cameras transmit fields on the media
48 bus in the same order they were captured, so if the top field was
[all …]
|
| /kernel/linux/linux-5.10/drivers/dma-buf/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 userspace via Sync File fds for synchronization between drivers via
14 The first and main user for this is graphics in which a fence is
18 Documentation/driver-api/sync_file.rst.
30 WARNING: improper use of this can result in deadlocking kernel
39 A driver to let userspace turn memfd regions into dma-bufs.
43 bool "Move notify between drivers (EXPERIMENTAL)"
47 Don't pin buffers if the dynamic DMA-buf interface is available on
50 through DMA-buf.
52 execution context and memory management between drivers.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | cadence-quadspi.txt | 4 - compatible : should be one of the following:
5 Generic default - "cdns,qspi-nor".
6 For TI 66AK2G SoC - "ti,k2g-qspi", "cdns,qspi-nor".
7 For TI AM654 SoC - "ti,am654-ospi", "cdns,qspi-nor".
8 - reg : Contains two entries, each of which is a tuple consisting of a
12 - interrupts : Unit interrupt specifier for the controller interrupt.
13 - clocks : phandle to the Quad SPI clock.
14 - cdns,fifo-depth : Size of the data FIFO in words.
15 - cdns,fifo-width : Bus width of the data FIFO in bytes.
16 - cdns,trigger-address : 32-bit indirect AHB trigger address.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/ |
| D | graph.txt | 4 ---------------
7 control flow to devices, but there can be more complex connections between
10 There already is a simple directed graph between devices tree nodes using
12 can not be inferred from device tree parent-child relationships. The device
22 Documentation/devicetree/bindings/media/video-interfaces.txt.
23 Here the ports describe data interfaces, and the links between them are
28 -----------------------------------
30 Ports are described by child 'port' nodes contained in the device node.
34 If more than one port is present in a device node or there is more than one
36 hardware interface, a common scheme using '#address-cells', '#size-cells'
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ |
| D | graph.txt | 4 ---------------
7 control flow to devices, but there can be more complex connections between
10 There already is a simple directed graph between devices tree nodes using
12 can not be inferred from device tree parent-child relationships. The device
22 Documentation/devicetree/bindings/media/video-interfaces.txt.
23 Here the ports describe data interfaces, and the links between them are
28 -----------------------------------
30 Ports are described by child 'port' nodes contained in the device node.
34 If more than one port is present in a device node or there is more than one
36 hardware interface, a common scheme using '#address-cells', '#size-cells'
[all …]
|
| /kernel/linux/linux-5.10/include/linux/sched/ |
| D | sd_flags.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * sched-domains (multiprocessor balancing) flag declarations.
15 * is usually because the flag describes some shared resource (all CPUs in that
17 * behaviour that we want to disable at some point in the hierarchy for
20 * In those cases it doesn't make sense to have the flag set for a domain but
21 * not have it in (some of) its children: sched domains ALWAYS span their child
22 * domains, so operations done with parent domains will cover CPUs in the lower
40 * involves equalizing a metric between groups), or for flags describing some
41 * shared resource (which would be shared between groups).
89 * NEEDS_GROUPS: Per-CPU capacity is asymmetric between groups.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-class-backlight-driver-adp8870 | 9 Contact: device-drivers-devel@blackfin.uclinux.org
12 on this <backlight>. Values are between 0 and 127. This file
23 Contact: device-drivers-devel@blackfin.uclinux.org
26 on this <backlight>. Values are between 0 and 127, typically
34 Contact: device-drivers-devel@blackfin.uclinux.org
38 is enabled). Returns integer between 0 (dark) and
44 Contact: device-drivers-devel@blackfin.uclinux.org
47 integer between 1..5 (1 = daylight, 2 = bright, ..., 5 = dark).
48 Writing a value between 1..5 forces the backlight controller
52 is an extension to the API documented in
[all …]
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| D | altera_tse.txt | 1 Altera Triple-Speed Ethernet MAC driver
3 Copyright (C) 2008-2014 Altera Corporation
5 This is the driver for the Altera Triple-Speed Ethernet (TSE) controllers
10 cases are simple communications between an embedded system and an external peer
16 the maintainer of this driver, found in MAINTAINERS.
18 The Triple-Speed Ethernet, SGDMA, and MSGDMA components are all soft IP
25 Triple-Speed Ethernet instance is using an SGDMA or MSGDMA component. The
30 The SGDMA component is to be deprecated in the near future (over the next 1-2
31 years as of this writing in early 2014) in favor of the MSGDMA component.
32 SGDMA support is included for existing designs and reference in case a
[all …]
|
| /kernel/linux/linux-5.10/drivers/misc/cxl/ |
| D | hcalls.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
26 * The 'flags' parameter regroups the various bit-fields
59 * cxl_h_detach_process - Detach a process element from a coherent
65 * cxl_h_reset_afu - Perform a reset to the coherent platform function.
70 * cxl_h_suspend_process - Suspend a process from being executed
71 * Parameter1 = process-token as returned from H_ATTACH_CA_PROCESS when
77 * cxl_h_resume_process - Resume a process to be executed
78 * Parameter1 = process-token as returned from H_ATTACH_CA_PROCESS when
84 * cxl_h_read_error_state - Reads the error state of the coherent
91 * cxl_h_get_afu_err - collect the AFU error buffer
[all …]
|
| /kernel/linux/linux-4.19/drivers/misc/cxl/ |
| D | hcalls.h | 30 * The 'flags' parameter regroups the various bit-fields
63 * cxl_h_detach_process - Detach a process element from a coherent
69 * cxl_h_reset_afu - Perform a reset to the coherent platform function.
74 * cxl_h_suspend_process - Suspend a process from being executed
75 * Parameter1 = process-token as returned from H_ATTACH_CA_PROCESS when
81 * cxl_h_resume_process - Resume a process to be executed
82 * Parameter1 = process-token as returned from H_ATTACH_CA_PROCESS when
88 * cxl_h_read_error_state - Reads the error state of the coherent
95 * cxl_h_get_afu_err - collect the AFU error buffer
97 * are between 0 and (ibm,error-buffer-size - 1)
[all …]
|