Home
last modified time | relevance | path

Searched refs:DMA (Results 1 – 25 of 325) sorted by relevance

12345678910>>...13

/f-stack/freebsd/contrib/device-tree/Bindings/dma/
H A Dfsl-imx-dma.txt1 * Freescale Direct Memory Access (DMA) Controller for i.MX
3 This document will only describe differences to the generic DMA Controller and
4 DMA request bindings as described in dma/dma.txt .
6 * DMA controller
10 - reg : Should contain DMA registers location and length
12 should contain DMA Error interrupt
16 - #dma-channels : Number of DMA channels supported. Should be 16.
17 - #dma-requests : Number of DMA requests supported.
30 * DMA client
32 Clients have to specify the DMA requests with phandles in a list.
[all …]
H A Dti-dma-crossbar.txt1 Texas Instruments DMA Crossbar (DMA request router)
4 - compatible: "ti,dra7-dma-crossbar" for DRA7xx DMA crossbar
9 - dma-requests: Number of DMA requests the crossbar can receive
10 - dma-masters: phandle pointing to the DMA controller
12 The DMA controller node need to have the following poroperties:
13 - dma-requests: Number of DMA requests the controller can handle
18 when mapping xbar input to DMA request, they are either
24 the DMA event number as crossbar ID (input to the DMA crossbar).
33 /* DMA controller */
46 /* DMA crossbar */
[all …]
H A Dmpc512x-dma.txt1 * Freescale MPC512x and MPC8308 DMA Controller
3 The DMA controller in Freescale MPC512x and MPC8308 SoCs can move
7 Refer to "Generic DMA Controller and DMA request bindings" in
12 - reg: should contain the DMA controller registers location and length;
13 - interrupt for the DMA controller: syntax of interrupt client node
15 - #dma-cells: the length of the DMA specifier, must be <1>.
16 Each channel of this DMA controller has a peripheral request line,
29 DMA clients must use the format described in dma/dma.txt file.
H A Drenesas,shdma.txt3 Sh-/r-mobile and R-Car systems often have multiple identical DMA controller
4 instances, capable of serving any of a common set of DMA slave devices, using
6 SHDMA DT nodes to be placed under a DMA multiplexer node. All such compatible
7 DMAC instances have the same number of channels and use the same DMA
12 * DMA multiplexer
19 - dma-channels: number of DMA channels
20 - dma-requests: number of DMA request signals
22 * DMA controller
73 * DMA client
76 - dmas: a list of <[DMA multiplexer phandle] [MID/RID value]> pairs,
[all …]
H A Dst,stm32-dma.yaml7 title: STMicroelectronics STM32 DMA Controller bindings
10 The STM32 DMA is a general-purpose direct memory access controller capable of
11 supporting 8 independent DMA channels. Each channel can have up to 8 requests.
12 DMA clients connected to the STM32 DMA controller must use the format
14 channel: a phandle to the DMA controller plus the following four integer cells:
17 3. A 32bit mask specifying the DMA channel configuration which are device
34 -bit 0-1: DMA FIFO threshold selection
39 -bit 2: DMA direct mode
41 0x1: Direct mode: each DMA request immediately initiates a transfer
66 description: Should contain all of the per-channel DMA
[all …]
H A Dmmp-dma.txt1 * MARVELL MMP DMA controller
3 Marvell Peripheral DMA Controller
8 - reg: Should contain DMA registers location and length.
9 - interrupts: Either contain all of the per-channel DMA interrupts
13 - #dma-channels: Number of DMA channels supported by the controller (defaults
15 - #dma-requests: Number of DMA requestor lines supported by the controller
26 * while DMA controller may not able to distinguish the irq channel
41 * Dmaengine driver (DMA controller) distinguish irq channel via
52 Marvell Two Channel DMA Controller used specifically for audio
57 - reg: Should contain DMA registers location and length.
[all …]
H A Dsprd-dma.txt1 * Spreadtrum DMA controller
3 This binding follows the generic DMA bindings defined in dma.txt.
7 - reg: Should contain DMA registers location and length.
11 - #dma-channels : Number of DMA channels supported. Should be 32.
12 - clock-names: Should contain the clock of the DMA controller.
30 DMA clients connected to the Spreadtrum DMA controller must use the format
33 1. A phandle pointing to the DMA controller.
H A Ddma-common.yaml7 title: DMA Engine Generic Binding
13 Generic binding to provide a way for a driver using DMA Engine to
14 retrieve the DMA request or channel information that goes from a
15 hardware device to a DMA controller.
25 Used to provide DMA controller specific information.
29 Bitmask of available DMA channels in ascending order that are
43 Number of DMA channels supported by the controller.
48 Number of DMA request signals supported by the controller.
H A Dowl-dma.txt1 * Actions Semi Owl SoCs DMA controller
3 This binding follows the generic DMA bindings defined in dma.txt.
7 - reg: Should contain DMA registers location and length.
12 - dma-requests: Number of DMA request signals supported by the controller.
14 - clocks: Phandle and Specifier of the clock feeding the DMA controller.
34 DMA clients connected to the Actions Semi Owl SoCs DMA controller must
39 1. A phandle pointing to the DMA controller.
H A Ddma-router.yaml7 title: DMA Router Generic Binding
16 DMA routers are transparent IP blocks used to route DMA request
17 lines from devices to the DMA controller. Some SoCs (like TI DRA7x)
18 have more peripherals integrated with DMA requests than what the DMA
28 Array of phandles to the DMA controllers the router can direct
H A Dapm-xgene-dma.txt1 Applied Micro X-Gene SoC DMA nodes
3 DMA nodes are defined to describe on-chip DMA interfaces in
6 Required properties for DMA interfaces:
11 1st - DMA control and status register address space.
15 - interrupts: DMA has 5 interrupts sources. 1st interrupt is
16 DMA error reporting interrupt. 2nd, 3rd, 4th and 5th interrupts
17 are completion interrupts for each DMA channels.
H A Datmel-dma.txt1 * Atmel Direct Memory Access Controller (DMA)
5 - reg: Should contain DMA registers location and length.
6 - interrupts: Should contain DMA interrupt.
19 DMA clients connected to the Atmel DMA controller must use the format
24 1. A phandle pointing to the DMA controller.
27 3. Parameters for the at91 DMA configuration register which are device
H A Dmilbeaut-m10v-xdmac.txt1 * Milbeaut AXI DMA Controller
3 Milbeaut AXI DMA controller has only memory to memory transfer capability.
5 * DMA controller
9 - reg: Should contain DMA registers location and length.
10 - interrupts: Should contain all of the per-channel DMA interrupts.
H A Dsnps,dma-spear1340.yaml7 title: Synopsys Designware DMA Controller
23 First cell is a phandle pointing to the DMA controller. Second one is
24 the DMA request line number. Third cell is the memory master identifier
43 Number of DMA channels supported by the controller. In case if
56 Number of DMA masters supported by the controller. In case if
65 DMA channels allocation order specifier. Zero means ascending order
73 DMA channels priority order. Zero means ascending channels priority
81 description: Maximum block size supported by the DMA controller.
86 description: Data bus width per each DMA master in bytes.
116 each DMA channel.
[all …]
H A Dadi,axi-dmac.txt1 Analog Devices AXI-DMAC DMA controller
11 - adi,channels: This sub-node must contain a sub-node for each DMA channel. For
31 - adi,length-width: Width of the DMA transfer length register.
32 - adi,cyclic: Must be set if the channel supports hardware cyclic DMA
34 - adi,2d: Must be set if the channel supports hardware 2D DMA transfers.
36 DMA clients connected to the AXI-DMAC DMA controller must use the format
38 specifier refers to the DMA channel index.
H A Dnvidia,tegra20-apbdma.txt1 * NVIDIA Tegra APB DMA controller
5 - reg: Should contain DMA registers location and length. This shuld include
7 - interrupts: Should contain all of the per-channel DMA interrupts.
14 - #dma-cells : Must be <1>. This dictates the length of DMA specifiers in
15 client nodes' dmas properties. The specifier represents the DMA request
17 documentation of the APB DMA channel control register REQ_SEL field.
H A Dbrcm,bcm2835-dma.txt1 * BCM2835 DMA controller
3 The BCM2835 DMA controller has 16 channels in total.
12 - reg: Should contain DMA registers location and length.
13 - interrupts: Should contain the DMA interrupts associated
14 to the DMA channels in ascending order.
70 DMA clients connected to the BCM2835 DMA controller must use the format
H A Dfsl-mxs-dma.txt1 * Freescale MXS DMA
6 - interrupts : Should contain the interrupt numbers of DMA channels.
9 - dma-channels : Number of channels supported by the DMA controller
12 - interrupt-names : Name of DMA channel interrupts
49 DMA clients connected to the MXS DMA controller must use the format
H A Dlpc1850-dmamux.txt1 NXP LPC18xx/43xx DMA MUX (DMA request router)
11 - dma-requests: Number of DMA requests for the mux
12 - dma-masters: phandle pointing to the DMA controller
14 The DMA controller node need to have the following poroperties:
15 - dma-requests: Number of DMA requests the controller can handle
/f-stack/freebsd/contrib/device-tree/Bindings/powerpc/fsl/
H A Ddma.txt1 * Freescale DMA Controllers
3 ** Freescale Elo DMA Controller
13 DMA channels and the address space of the DMA controller
17 - DMA channel nodes:
68 ** Freescale EloPlus DMA Controller
81 DMA channels and the address space of the DMA controller
83 - DMA channel nodes:
128 ** Freescale Elo3 DMA Controller
140 DMA channels and the address space of the DMA controller
142 - DMA channel nodes:
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/soc/ti/
H A Dkeystone-navigator-dma.txt1 Keystone Navigator DMA Controller
9 an internal packet DMA module which is used as an infrastructure DMA
12 Navigator DMA cloud layout:
17 |-> DMA instance #0
19 |-> DMA instance #1
23 |-> DMA instance #n
25 Navigator DMA properties:
34 into DMA and the DMA uses it as the physical addresses to reach queue
40 DMA instance properties:
94 Navigator DMA client:
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/powerpc/4xx/
H A Dppc440spe-adma.txt1 PPC440SPe DMA/XOR (DMA Controller and XOR Accelerator)
4 are specified hereby. These are I2O/DMA, DMA and XOR nodes
5 for DMA engines and Memory Queue Module node. The latter is used
9 DMA devices.
28 ii) The DMA node
33 - cell-index : 1 cell, hardware index of the DMA engine
39 and DMA Error IRQ (on UIC1). The latter is common
40 for both DMA engines>.
/f-stack/dpdk/doc/guides/rawdevs/
H A Docteontx2_dma.rst4 OCTEON TX2 DMA Driver
7 OCTEON TX2 has an internal DMA unit which can be used by applications to initiate
8 DMA transaction internally, from/to host when OCTEON TX2 operates in PCIe End
9 Point mode. The DMA PF function supports 8 VFs corresponding to 8 DMA queues.
10 Each DMA queue was exposed as a VF function when SRIOV enabled.
15 This DMA PMD supports below 3 modes of memory transfers
44 The number of DMA VFs (queues) enabled can be controlled by setting sysfs
57 The OCTEON TX2 DPI DMA HW devices will need to be bound to a
68 Configuring DMA rawdev device is done using the ``rte_rawdev_configure()``
88 To perform data transfer using OCTEON TX2 DMA rawdev devices use standard
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/net/
H A Dxilinx_axienet.txt11 sent and received through means of an AXI DMA controller. This driver
12 includes the DMA driver code, so this driver is incompatible with AXI DMA
21 and length of the AXI DMA controller IO space, unless
24 - interrupts : Should be a list of 2 or 3 interrupts: TX DMA, RX DMA,
26 specified, the TX/RX DMA interrupts should be on that node
47 for the AXI DMA controller used by this device.
48 If this is specified, the DMA-related resources from that
49 device (DMA registers and DMA TX/RX interrupts) rather
/f-stack/freebsd/contrib/device-tree/Bindings/spi/
H A Domap-spi.txt15 - dmas: List of DMA specifiers with the controller specific format
16 as described in the generic DMA client binding. A tx and rx
18 - dma-names: List of DMA request names. These strings correspond
19 1:1 with the DMA specifiers listed in dmas. The string naming
25 [hwmod populated DMA resources]
35 [generic DMA request binding]

12345678910>>...13