| /Linux-v4.19/drivers/spi/ |
| D | spi-loopback-test.c | 92 .transfers = {
106 .transfers = {
119 .transfers = {
131 .transfers = {
144 .transfers = {
161 .transfers = {
178 .transfers = {
195 .transfers = {
211 .transfers = {
228 .transfers = {
[all …]
|
| D | spi-fsl-espi.c | 164 first = list_first_entry(&m->transfers, struct spi_transfer, in fsl_espi_check_message()
167 list_for_each_entry(t, &m->transfers, transfer_list) { in fsl_espi_check_message()
202 list_for_each_entry(t, &m->transfers, transfer_list) { in fsl_espi_check_rxskip_mode()
410 espi->m_transfers = &m->transfers; in fsl_espi_trans()
411 espi->tx_t = list_first_entry(&m->transfers, struct spi_transfer, in fsl_espi_trans()
415 espi->rx_t = list_first_entry(&m->transfers, struct spi_transfer, in fsl_espi_trans()
451 list_for_each_entry(t, &m->transfers, transfer_list) { in fsl_espi_do_one_msg()
458 t = list_first_entry(&m->transfers, struct spi_transfer, in fsl_espi_do_one_msg()
|
| D | spi-cavium.c | 136 list_for_each_entry(xfer, &msg->transfers, transfer_list) { in octeon_spi_transfer_one_message()
138 &msg->transfers); in octeon_spi_transfer_one_message()
|
| /Linux-v4.19/Documentation/i2c/ |
| D | i2c-topology | 21 i2c transfers, and all adapters with a parent are part of an "i2c-mux"
75 select and/or deselect operations must use i2c transfers to complete
77 full transaction, unrelated i2c transfers may interleave the different
100 number (one, in most cases) of i2c transfers. Unrelated i2c transfers
127 4. M1 (presumably) does some i2c-transfers as part of its select.
128 These transfers are normal i2c-transfers that locks the parent
146 has to ensure that any and all i2c transfers through that parent
147 adapter during the transaction are unlocked i2c transfers (using e.g.
155 and the parent mux issus i2c-transfers as part of its select).
160 pinctrl, regmap or iio, it is essential that any i2c transfers
[all …]
|
| /Linux-v4.19/Documentation/usb/ |
| D | ohci.txt | 18 - interrupt transfers can be larger, and can be queued
25 transfers. Previously, using periods of one frame would risk data loss due
26 to overhead in IRQ processing. When interrupt transfers are queued, those
27 risks can be minimized by making sure the hardware always has transfers to
|
| D | ehci.txt | 53 and interrupt transfers, including requests to USB 1.1 devices through
61 transfers can't share much code with the code for high speed ISO transfers,
67 Transfers of all types can be queued. This means that control transfers
69 ones from another driver, and that interrupt transfers can use periods
81 transactions (interrupt and isochronous transfers). These place some
116 and bulk transfers. Shows each active qh and the qtds
120 and isochronous transfers. Doesn't show qtds.
129 can't, such as "high bandwidth" periodic (interrupt or ISO) transfers.
131 periodic transfers) use different encodings when operating at high speed.
148 Bulk transfers are most often used where throughput is an issue. It's
[all …]
|
| /Linux-v4.19/Documentation/driver-api/dmaengine/ |
| D | provider.rst | 11 They have a given number of channels to use for the DMA transfers, and
41 really efficient, you'll get several bigger transfers. This is done
44 transfer into smaller sub-transfers.
46 Our theoretical DMA controller would then only be able to do transfers
48 transfers we usually have are not, and want to copy data from
52 DMAEngine, at least for mem2dev transfers, require support for
80 memory-to-device (mem2dev) kind of transfers. Most devices often
81 support other kind of transfers or memory operations that dmaengine
91 Over time, the need for memory to device transfers arose, and
125 (i.e. excluding mem2mem transfers)
[all …]
|
| D | pxa_dma.rst | 19 b) All transfers having asked for confirmation should be signaled
115 This will speed up residue calculation, for large transfers such as video
129 - calling all the transfer callbacks of finished transfers, based on
138 transfers will be scanned for all of their descriptors against the
144 - there are not "acked" transfers (tx0)
|
| /Linux-v4.19/Documentation/spi/ |
| D | pxa2xx | 8 - SSP PIO and SSP DMA data transfers.
16 launching the dma/interrupt driven transfers.
102 fifo overruns (especially in PIO mode transfers). Good default values are
112 to determine the correct value. An SSP configured for byte-wide transfers would
165 .dma_burst_size = 8, /* Byte wide transfers used so 8 byte bursts */
173 .dma_burst_size = 8, /* Byte wide transfers used so 8 byte bursts */
208 transfers. The driver defaults to PIO mode and DMA transfers must be enabled
216 always use PIO transfers
220 use PIO transfers
|
| /Linux-v4.19/Documentation/devicetree/bindings/dma/ |
| D | stm32-dma.txt | 52 0x0: no address increment between transfers
53 0x1: increment address between transfers
55 0x0: no address increment between transfers
56 0x1: increment address between transfers
|
| D | snps-dma.txt | 28 - multi-block: Multi block transfers supported by hardware. Array property with
55 3. Memory master for transfers on allocated channel
56 4. Peripheral master for transfers on allocated channel
|
| D | st_fdma.txt | 59 0x0: no address increment between transfers
60 0x1: increment address between transfers
64 4. transfers type
|
| D | adi,axi-dmac.txt | 33 transfers.
34 - adi,2d: Must be set if the channel supports hardware 2D DMA transfers.
|
| /Linux-v4.19/Documentation/ |
| D | DMA-ISA-LPC.txt | 7 This document describes how to do DMA transfers using the old ISA DMA
22 The second contains the routines specific to ISA DMA transfers. Since
34 (You usually need a special buffer for DMA transfers instead of
69 8-bit transfers and the upper four are for 16-bit transfers.
80 The ability to use 16-bit or 8-bit transfers is _not_ up to you as a
105 be 16-bit aligned for 16-bit transfers) and how many bytes to
|
| /Linux-v4.19/drivers/usb/gadget/udc/ |
| D | Kconfig | 152 zero (for control transfers).
173 supports both full and high speed USB 2.0 data transfers.
185 that supports both full and high speed USB 2.0 data transfers.
199 that supports super, high, and full speed USB 3.0 data transfers.
213 control transfers).
225 endpoints, as well as endpoint zero (for control transfers).
297 supports both full and high speed USB 2.0 data transfers.
346 both full and high speed USB 2.0 data transfers.
369 supports both full and high speed USB 2.0 data transfers.
372 (for control transfers) and several endpoints with dedicated
[all …]
|
| /Linux-v4.19/Documentation/devicetree/bindings/dma/xilinx/ |
| D | zynqmp_dma.txt | 1 Xilinx ZynqMP DMA engine, it does support memory to memory transfers,
2 memory to device and device to memory transfers. It also has flow
|
| D | xilinx_dma.txt | 1 Xilinx AXI VDMA engine, it does transfers between memory and video devices.
6 Xilinx AXI DMA engine, it does transfers between memory and AXI4 stream
11 Xilinx AXI CDMA engine, it does transfers between memory-mapped source
|
| /Linux-v4.19/drivers/usb/musb/ |
| D | Kconfig | 140 Enable DMA transfers on UX500 platforms.
146 Enable DMA transfers using Mentor's engine.
152 Enable DMA transfers when TI CPPI DMA is available.
164 Enable DMA transfers on TUSB 6010 when OMAP DMA is available.
|
| /Linux-v4.19/Documentation/driver-api/usb/ |
| D | URB.rst | 67 // (IN) buffer used for data transfers
78 // Only for PERIODIC transfers (ISO, INTERRUPT)
150 - Too many queued ISO transfers (``-EAGAIN``)
224 transferred. That's because USB transfers are packetized; it might take
239 How to do isochronous (ISO) transfers?
243 also have to set ``urb->interval`` to say how often to make transfers; it's
249 For ISO transfers you also have to fill a :c:type:`usb_iso_packet_descriptor`
275 How to start interrupt (INT) transfers?
278 Interrupt transfers, like isochronous transfers, are periodic, and happen
|
| /Linux-v4.19/Documentation/rapidio/ |
| D | mport_cdev.txt | 53 - Allocate/Free contiguous DMA coherent memory buffer for DMA data transfers
55 - Initiate DMA data transfers to/from remote RapidIO devices (RIO_TRANSFER).
78 specific DMA engine support and therefore DMA data transfers mport_cdev driver
106 - Add memory mapped DMA data transfers as an option when RapidIO-specific DMA
|
| /Linux-v4.19/drivers/rapidio/ |
| D | Kconfig | 23 than Maintenance transfers.
32 transfers to/from target RIO devices. RapidIO uses NREAD and
35 capable to perform data transfers to/from RapidIO.
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-module | 18 Description: Maximum time allowed for periodic transfers per microframe (μs)
20 [ USB 2.0 sets maximum allowed time for periodic transfers per
|
| /Linux-v4.19/include/linux/spi/ |
| D | spi.h | 67 unsigned long transfers; member
831 struct list_head transfers; member
868 INIT_LIST_HEAD(&m->transfers); in spi_message_init_no_memset()
881 list_add_tail(&t->transfer_list, &m->transfers); in spi_message_add_tail()
1309 return list_is_last(&xfer->transfer_list, &ctlr->cur_msg->transfers); in spi_transfer_is_last()
|
| /Linux-v4.19/drivers/staging/mt7621-spi/ |
| D | spi-mt7621.c | 275 list_for_each_entry(t, &m->transfers, transfer_list) in mt7621_spi_transfer_half_duplex()
286 list_for_each_entry(t, &m->transfers, transfer_list) { in mt7621_spi_transfer_half_duplex()
318 list_for_each_entry(t, &m->transfers, transfer_list) { in mt7621_spi_transfer_full_duplex()
371 list_for_each_entry(t, &m->transfers, transfer_list) { in mt7621_spi_transfer_full_duplex()
|
| /Linux-v4.19/Documentation/fb/ |
| D | udlfb.txt | 15 pixels line-by-line via USB bulk transfers.
17 Because of the efficiency of bulk transfers and a protocol on top that
22 Mode setting, EDID read, etc are other bulk or control transfers. Mode
46 Writes need to be detected and encoded into USB bulk transfers by the CPU.
119 do not transmit. Spends host memory to save USB transfers.
|
