| /linux-5.19.10/drivers/media/platform/amphion/ |
| D | vpu_color.c | 79 u32 vpu_color_cvrt_transfers_v2i(u32 transfers) in vpu_color_cvrt_transfers_v2i() argument
81 return vpu_helper_find_in_array_u8(colortransfers, ARRAY_SIZE(colortransfers), transfers); in vpu_color_cvrt_transfers_v2i()
84 u32 vpu_color_cvrt_transfers_i2v(u32 transfers) in vpu_color_cvrt_transfers_i2v() argument
86 return transfers < ARRAY_SIZE(colortransfers) ? colortransfers[transfers] : 0; in vpu_color_cvrt_transfers_i2v()
117 int vpu_color_check_transfers(u32 transfers) in vpu_color_check_transfers() argument
119 return vpu_color_cvrt_transfers_v2i(transfers) ? 0 : -EINVAL; in vpu_color_check_transfers()
145 u32 transfers; in vpu_color_get_default() local
151 transfers = V4L2_XFER_FUNC_709; in vpu_color_get_default()
157 transfers = V4L2_XFER_FUNC_709; in vpu_color_get_default()
161 transfers = V4L2_XFER_FUNC_SMPTE240M; in vpu_color_get_default()
[all …]
|
| D | vpu_helpers.h | 56 int vpu_color_check_transfers(u32 transfers);
61 u32 vpu_color_cvrt_transfers_v2i(u32 transfers);
62 u32 vpu_color_cvrt_transfers_i2v(u32 transfers);
|
| /linux-5.19.10/drivers/spi/ |
| D | spi-loopback-test.c | 83 .transfers = {
97 .transfers = {
110 .transfers = {
122 .transfers = {
135 .transfers = {
152 .transfers = {
169 .transfers = {
186 .transfers = {
202 .transfers = {
219 .transfers = {
[all …]
|
| D | spi-fsl-espi.c | 160 first = list_first_entry(&m->transfers, struct spi_transfer, in fsl_espi_check_message()
163 list_for_each_entry(t, &m->transfers, transfer_list) { in fsl_espi_check_message()
198 list_for_each_entry(t, &m->transfers, transfer_list) { in fsl_espi_check_rxskip_mode()
406 espi->m_transfers = &m->transfers; in fsl_espi_trans()
407 espi->tx_t = list_first_entry(&m->transfers, struct spi_transfer, in fsl_espi_trans()
411 espi->rx_t = list_first_entry(&m->transfers, struct spi_transfer, in fsl_espi_trans()
446 list_for_each_entry(t, &m->transfers, transfer_list) { in fsl_espi_do_one_msg()
455 t = list_first_entry(&m->transfers, struct spi_transfer, in fsl_espi_do_one_msg()
|
| D | spi-cavium.c | 135 list_for_each_entry(xfer, &msg->transfers, transfer_list) { in octeon_spi_transfer_one_message()
137 &msg->transfers); in octeon_spi_transfer_one_message()
|
| /linux-5.19.10/Documentation/i2c/ |
| D | i2c-topology.rst | 23 I2C transfers, and all adapters with a parent are part of an "i2c-mux"
86 select and/or deselect operations must use I2C transfers to complete
88 full transaction, unrelated I2C transfers may interleave the different
112 number (one, in most cases) of I2C transfers. Unrelated I2C transfers
143 4. M1 (presumably) does some I2C transfers as part of its select.
144 These transfers are normal I2C transfers that locks the parent
162 has to ensure that any and all I2C transfers through that parent
163 adapter during the transaction are unlocked I2C transfers (using e.g.
172 and the parent mux issues I2C transfers as part of its select).
177 pinctrl, regmap or iio, it is essential that any I2C transfers
[all …]
|
| /linux-5.19.10/Documentation/usb/ |
| D | ohci.rst | 22 - interrupt transfers can be larger, and can be queued
29 transfers. Previously, using periods of one frame would risk data loss due
30 to overhead in IRQ processing. When interrupt transfers are queued, those
31 risks can be minimized by making sure the hardware always has transfers to
|
| D | ehci.rst | 59 and interrupt transfers, including requests to USB 1.1 devices through
67 transfers can't share much code with the code for high speed ISO transfers,
74 Transfers of all types can be queued. This means that control transfers
76 ones from another driver, and that interrupt transfers can use periods
88 transactions (interrupt and isochronous transfers). These place some
125 and bulk transfers. Shows each active qh and the qtds
130 and isochronous transfers. Doesn't show qtds.
140 can't, such as "high bandwidth" periodic (interrupt or ISO) transfers.
142 periodic transfers) use different encodings when operating at high speed.
160 Bulk transfers are most often used where throughput is an issue. It's
[all …]
|
| /linux-5.19.10/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-5.19.10/Documentation/spi/ |
| D | pxa2xx.rst | 10 - SSP PIO and SSP DMA data transfers.
18 the DMA or interrupt driven transfers.
109 FIFO overruns (especially in PIO mode transfers). Good default values are::
119 to determine the correct value. An SSP configured for byte-wide transfers would
146 .dma_burst_size = 8, /* Byte wide transfers used so 8 byte bursts */
153 .dma_burst_size = 8, /* Byte wide transfers used so 8 byte bursts */
187 transfers. The driver defaults to PIO mode and DMA transfers must be enabled
197 always use PIO transfers
201 use PIO transfers
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-bus-mdio | 10 What: /sys/bus/mdio_bus/devices/.../statistics/transfers
11 What: /sys/class/mdio_bus/.../transfers
16 Total number of transfers for this MDIO bus.
48 Total number of transfers for this MDIO bus address.
|
| D | sysfs-bus-fsi-devices-sbefifo | 8 ocurred and no transfers have completed since the timeout. A
10 has, more recent transfers have completed successful.
|
| D | sysfs-module | 18 Description: Maximum time allowed for periodic transfers per microframe (μs)
21 USB 2.0 sets maximum allowed time for periodic transfers per
|
| /linux-5.19.10/Documentation/devicetree/bindings/dma/ |
| D | st,stm32-dma.yaml | 20 0x0: no address increment between transfers
21 0x1: increment address between transfers
23 0x0: no address increment between transfers
24 0x1: increment address between transfers
49 managing transfers for STM32 USART/UART.
|
| 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-5.19.10/Documentation/core-api/ |
| D | dma-isa-lpc.rst | 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-5.19.10/drivers/usb/gadget/udc/ |
| D | Kconfig | 154 zero (for control transfers).
175 supports both full and high speed USB 2.0 data transfers.
187 that supports both full and high speed USB 2.0 data transfers.
201 that supports super, high, and full speed USB 3.0 data transfers.
215 control transfers).
227 endpoints, as well as endpoint zero (for control transfers).
299 supports both full and high speed USB 2.0 data transfers.
349 both full and high speed USB 2.0 data transfers.
372 supports both full and high speed USB 2.0 data transfers.
375 (for control transfers) and several endpoints with dedicated
[all …]
|
| /linux-5.19.10/drivers/usb/musb/ |
| D | Kconfig | 145 Enable DMA transfers on UX500 platforms.
151 Enable DMA transfers using Mentor's engine.
157 Enable DMA transfers when TI CPPI DMA is available.
169 Enable DMA transfers on TUSB 6010 when OMAP DMA is available.
|
| /linux-5.19.10/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 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-5.19.10/Documentation/devicetree/bindings/dma/xilinx/ |
| D | xlnx,zynqmp-dma-1.0.yaml | 10 The Xilinx ZynqMP DMA engine supports memory to memory transfers,
11 memory to device and device to memory transfers. It also has flow
|
| /linux-5.19.10/Documentation/driver-api/rapidio/ |
| D | mport_cdev.rst | 49 - Allocate/Free contiguous DMA coherent memory buffer for DMA data transfers
51 - Initiate DMA data transfers to/from remote RapidIO devices (RIO_TRANSFER).
75 specific DMA engine support and therefore DMA data transfers mport_cdev driver
109 - Add memory mapped DMA data transfers as an option when RapidIO-specific DMA
|
| /linux-5.19.10/drivers/rapidio/ |
| D | Kconfig | 35 than Maintenance transfers.
44 transfers to/from target RIO devices. RapidIO uses NREAD and
47 capable to perform data transfers to/from RapidIO.
|
| /linux-5.19.10/include/linux/spi/ |
| D | spi.h | 65 unsigned long transfers; member
994 struct list_head transfers; member
1031 INIT_LIST_HEAD(&m->transfers); in spi_message_init_no_memset()
1044 list_add_tail(&t->transfer_list, &m->transfers); in spi_message_add_tail()
1485 return list_is_last(&xfer->transfer_list, &ctlr->cur_msg->transfers); in spi_transfer_is_last()
|