Home
last modified time | relevance | path

Searched full:transfers (Results 1 – 25 of 998) sorted by relevance

12345678910>>...40

/linux-5.10/tools/usb/
Dhcd-tests.sh11 # - 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 …]
/linux-5.10/Documentation/driver-api/dmaengine/
Dprovider.rst11 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 …]
Dpxa_dma.rst8 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)
/linux-5.10/drivers/spi/
Dspi-loopback-test.c25 /* 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 …]
Dspi-test.h41 * @transfers: array of @spi_transfers that are part of the
43 * @transfer_count: number of transfers
63 * @iterate_transfer_mask: the bitmask of transfers to which the iterations
75 struct spi_transfer transfers[SPI_TEST_MAX_TRANSFERS]; member
/linux-5.10/Documentation/usb/
Dehci.rst59 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 …]
Dohci.rst22 - 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
/linux-5.10/drivers/usb/gadget/udc/
DKconfig154 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.
348 both full and high speed USB 2.0 data transfers.
371 supports both full and high speed USB 2.0 data transfers.
374 (for control transfers) and several endpoints with dedicated
[all …]
/linux-5.10/Documentation/spi/
Dpxa2xx.rst10 - 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
/linux-5.10/Documentation/i2c/
Di2c-topology.rst23 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.10/Documentation/core-api/
Ddma-isa-lpc.rst7 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.10/include/linux/platform_data/
Dedma.h11 * 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
Ddma-dw.h27 * @m_master: memory master for transfers on allocated channel
28 * @p_master: peripheral master for transfers on allocated channel
51 * @multi_block: Multi block transfers supported by hardware per channel.
/linux-5.10/Documentation/driver-api/usb/
DURB.rst33 - 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
/linux-5.10/drivers/usb/c67x00/
Dc67x00-hcd.h22 * These can be tuned for specific use cases, e.g. if isochronous transfers
25 * If bulk transfers are important, the MAX_FRAME_BW can be increased,
33 * isochronous transfers are scheduled), in order to optimize the throughput
47 * Periodic transfers may only use 90% of the full frame, but as
49 * use the full usable time for periodic transfers.
/linux-5.10/Documentation/devicetree/bindings/dma/
Dst,stm32-dma.yaml20 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
/linux-5.10/drivers/usb/musb/
DKconfig145 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.10/include/linux/spi/
Dspi.h31 * struct spi_statistics - statistics for spi transfers
35 * @transfers: number of spi_transfers handled
53 * number of transfers that have been split because of
60 unsigned long transfers; member
123 * @bits_per_word: Data transfers involve one or more words; word sizes
353 * It's always safe to call this unless transfers are pending on
385 * message while queuing transfers that arrive in the meantime. When the
495 /* bitmask of supported bits_per_word for transfers */
536 * IMPORTANT: this may be called when transfers to another
538 * which could break those transfers.
[all …]
/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-mdio9 What: /sys/bus/mdio_bus/devices/.../statistics/transfers
14 Total number of transfers for this MDIO bus.
42 Total number of transfers for this MDIO bus address.
/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/
Dcore.json23 … This includes those for which prediction is not attempted (far control transfers, exceptions and …
40 "BriefDescription": "Retired Far Control Transfers.",
41 …far control transfers retired including far call/jump/return, IRET, SYSCALL and SYSRET, plus excep…
/linux-5.10/drivers/rapidio/
DKconfig35 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.10/tools/perf/pmu-events/arch/x86/amdzen2/
Dcore.json23 … This includes those for which prediction is not attempted (far control transfers, exceptions and …
40 "BriefDescription": "Retired Far Control Transfers.",
41 …far control transfers retired including far call/jump/return, IRET, SYSCALL and SYSRET, plus excep…
/linux-5.10/include/uapi/linux/usb/
Dgadgetfs.h16 * then performing data transfers by reading or writing.
72 /* IN transfers may be reported to the gadget driver as complete
74 * OUT transfers may be reported to the host's "client" driver as
/linux-5.10/drivers/usb/dwc2/
DKconfig88 bool "Enable Debugging Messages For Periodic Transfers"
93 logged for periodic transfers. This allows better debugging of
94 non-periodic transfers, but of course the debug logs will be
/linux-5.10/Documentation/driver-api/rapidio/
Dmport_cdev.rst49 - 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

12345678910>>...40