| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/tools/usb/ |
| D | hcd-tests.sh | 11 # - loop: needs firmware that will buffer N transfers
38 # set up to use interrupt transfers by 'usbtest' module options
126 echo "test 1: $COUNT transfers, same size"
128 echo "test 3: $COUNT transfers, variable/short size"
132 echo "test 17: $COUNT transfers, unaligned DMA map by core"
135 echo "test 19: $COUNT transfers, unaligned DMA map by usb_alloc_coherent"
166 echo "test 15: $COUNT transfers, same size"
175 echo "test 22: $COUNT transfers, non aligned"
187 echo "test 2: $COUNT transfers, same size"
189 echo "test 4: $COUNT transfers, variable size"
[all …]
|
| /kernel/linux/linux-5.10/tools/usb/ |
| D | hcd-tests.sh | 11 # - loop: needs firmware that will buffer N transfers
38 # set up to use interrupt transfers by 'usbtest' module options
126 echo "test 1: $COUNT transfers, same size"
128 echo "test 3: $COUNT transfers, variable/short size"
132 echo "test 17: $COUNT transfers, unaligned DMA map by core"
135 echo "test 19: $COUNT transfers, unaligned DMA map by usb_alloc_coherent"
166 echo "test 15: $COUNT transfers, same size"
175 echo "test 22: $COUNT transfers, non aligned"
187 echo "test 2: $COUNT transfers, same size"
189 echo "test 4: $COUNT transfers, variable size"
[all …]
|
| /kernel/linux/linux-6.6/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 | 8 a) Transfers hot queuing
19 b) All transfers having asked for confirmation should be signaled
61 Transfers a single u32 to a well known dma coherent memory to leave
70 c) Transfers hot-chaining
109 d) Transfers completion updater
115 This will speed up residue calculation, for large transfers such as video
120 e) Transfers completion, irq and tasklet
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)
|
| /kernel/linux/linux-5.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 | 8 a) Transfers hot queuing
19 b) All transfers having asked for confirmation should be signaled
61 Transfers a single u32 to a well known dma coherent memory to leave
70 c) Transfers hot-chaining
109 d) Transfers completion updater
115 This will speed up residue calculation, for large transfers such as video
120 e) Transfers completion, irq and tasklet
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)
|
| /kernel/linux/linux-5.10/drivers/spi/ |
| D | spi-loopback-test.c | 25 /* flag to only simulate transfers */
83 .transfers = {
97 .transfers = {
110 .transfers = {
122 .transfers = {
129 .description = "two tx-transfers - alter both",
135 .transfers = {
146 .description = "two tx-transfers - alter first",
152 .transfers = {
163 .description = "two tx-transfers - alter second",
[all …]
|
| /kernel/linux/linux-6.6/drivers/spi/ |
| D | spi-loopback-test.c | 25 /* flag to only simulate transfers */
94 .transfers = {
108 .transfers = {
121 .transfers = {
133 .transfers = {
140 .description = "two tx-transfers - alter both",
146 .transfers = {
157 .description = "two tx-transfers - alter first",
163 .transfers = {
174 .description = "two tx-transfers - alter second",
[all …]
|
| /kernel/linux/linux-6.6/Documentation/usb/ |
| 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 …]
|
| D | ohci.rst | 22 - interrupt transfers can be larger, and can be queued
27 The "ohci-hcd" driver handles all USB 1.1 transfer types. Transfers of all
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
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| 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 …]
|
| D | ohci.rst | 22 - interrupt transfers can be larger, and can be queued
27 The "ohci-hcd" driver handles all USB 1.1 transfer types. Transfers of all
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
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-6.6/drivers/usb/gadget/udc/ |
| D | Kconfig | 142 zero (for control transfers).
163 supports both full and high speed USB 2.0 data transfers.
175 that supports both full and high speed USB 2.0 data transfers.
200 that supports super, high, and full speed USB 3.0 data transfers.
225 control transfers).
284 supports both full and high speed USB 2.0 data transfers.
334 both full and high speed USB 2.0 data transfers.
357 supports both full and high speed USB 2.0 data transfers.
360 (for control transfers) and several endpoints with dedicated
367 data transfers.
[all …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/Documentation/spi/ |
| D | pxa2xx.rst | 10 - SSP PIO and SSP DMA data transfers.
18 launching the dma/interrupt driven transfers.
106 fifo overruns (especially in PIO mode transfers). Good default values are::
116 to determine the correct value. An SSP configured for byte-wide transfers would
171 .dma_burst_size = 8, /* Byte wide transfers used so 8 byte bursts */
179 .dma_burst_size = 8, /* Byte wide transfers used so 8 byte bursts */
214 transfers. The driver defaults to PIO mode and DMA transfers must be enabled
222 always use PIO transfers
226 use PIO transfers
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-6.6/Documentation/i2c/ |
| D | i2c-topology.rst | 25 I2C transfers, and all adapters with a parent are part of an "i2c-mux"
49 select and/or deselect operations must use I2C transfers to complete
51 full transaction, unrelated I2C transfers may interleave the different
74 4. M1 (presumably) does some I2C transfers as part of its select.
75 These transfers are normal I2C transfers that locks the parent
114 number (one, in most cases) of I2C transfers. Unrelated I2C transfers
130 has to ensure that any and all I2C transfers through that parent
131 adapter during the transaction are unlocked I2C transfers (using e.g.
154 5. If M1 does any I2C transfers (on this root adapter) as part of
155 its select, those transfers must be unlocked I2C transfers so
[all …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-6.6/include/linux/platform_data/ |
| D | edma.h | 11 * Channel Triggers transfers, usually from a hardware event but
21 * Each PaRAM set describes a sequence of transfers, either for one large
23 * is driven only from a channel, which performs the transfers specified
24 * in its PaRAM slot until there are no more transfers. When that last
66 * This way, long transfers on the default queue started
|
| /kernel/linux/linux-5.10/include/linux/platform_data/ |
| D | edma.h | 11 * Channel Triggers transfers, usually from a hardware event but
21 * Each PaRAM set describes a sequence of transfers, either for one large
23 * is driven only from a channel, which performs the transfers specified
24 * in its PaRAM slot until there are no more transfers. When that last
66 * This way, long transfers on the default queue started
|
| /kernel/linux/linux-6.6/Documentation/driver-api/usb/ |
| D | URB.rst | 33 - Transfers for one URB can be canceled with :c:func:`usb_unlink_urb`
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
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | URB.rst | 33 - Transfers for one URB can be canceled with :c:func:`usb_unlink_urb`
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
|