Home
last modified time | relevance | path

Searched refs:transfers (Results 1 – 25 of 151) sorted by relevance

1234567

/linux/Documentation/i2c/
H A Di2c-topology.rst25 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 …]
/linux/Documentation/usb/
H A Dohci.rst22 - 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
H A 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 …]
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-mdio10 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.
H A Dsysfs-bus-fsi-devices-sbefifo8 occurred and no transfers have completed since the timeout. A
10 has, more recent transfers have completed successfully.
/linux/Documentation/core-api/
H A 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/drivers/usb/gadget/udc/
H A DKconfig136 zero (for control transfers).
157 supports both full and high speed USB 2.0 data transfers.
169 that supports both full and high speed USB 2.0 data transfers.
194 that supports super, high, and full speed USB 3.0 data transfers.
219 control transfers).
263 supports both full and high speed USB 2.0 data transfers.
313 supports both full and high speed USB 2.0 data transfers.
316 (for control transfers) and several endpoints with dedicated
323 data transfers.
326 (for control transfers) and several endpoints with dedicated
[all …]
/linux/Documentation/driver-api/soundwire/
H A Dbra.rst15 command/control transfers by reclaiming parts of the audio
32 efficiency of the protocol by requiring multiple BRA transfers
41 bandwidth. If there are no on-going audio transfers, the entire
53 BRA transfers. This is convenient to e.g. deal with alerts, jack
60 bus behind the SoundWire IP. In this case, the transfers may
181 with two FIFOs consuming/generating data transfers in parallel
226 However BRA transfers could be quite long, and the use of a single
228 operation of the control/command and BRA transfers is a fundamental
242 to wait for the BRA transfers to complete. This would allow for a
244 the BRA API must support async transfers and expose a separate wait
[all …]
/linux/Documentation/devicetree/bindings/dma/
H A Dst_fdma.txt59 0x0: no address increment between transfers
60 0x1: increment address between transfers
64 4. transfers type
/linux/Documentation/driver-api/usb/
H A DURB.rst67 // (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/drivers/rapidio/
H A 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/Documentation/driver-api/rapidio/
H A 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
/linux/Documentation/fb/
H A Dudlfb.rst15 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.
127 do not transmit. Spends host memory to save USB transfers.
/linux/drivers/usb/musb/
H A DKconfig145 Enable DMA transfers on UX500 platforms.
151 Enable DMA transfers using Mentor's engine.
163 Enable DMA transfers on TUSB 6010 when OMAP DMA is available.
/linux/Documentation/networking/
H A Dj1939.rst92 - These are automatically handled as J1939 Transport Protocol (TP) transfers.
96 - TP transfers can be unicast or broadcast.
106 - These are handled as ISO 11783 Extended Transport Protocol (ETP) transfers.
108 - ETP transfers are used for larger payloads and are split into multiple CAN
111 - **ETP transfers (unicast):** Require a receiver on the other side to
114 - ETP transfers cannot be broadcast like TP transfers, and always require a
123 monitor this value and handle partial transfers.
136 - **Simple transfers (<= 8 bytes):** Do not require a receiver on the other
145 TP transfers. ETP cannot be broadcast and always needs a receiving client.
646 message transfers and errors.
[all …]
H A Dplip.rst123 ports. This allows byte-wide transfers and avoids reconstructing
124 nibbles into bytes, leading to much faster transfers.
130 printer "null" cable which transfers data four bits at a time using
164 ports. This allows byte-wide transfers, and avoids reconstructing
/linux/drivers/spi/
H A Dspi-cavium.c135 list_for_each_entry(xfer, &msg->transfers, transfer_list) { in octeon_spi_transfer_one_message()
137 &msg->transfers); in octeon_spi_transfer_one_message()
H A Dspi.c175 SPI_STATISTICS_SHOW(transfers);
320 u64_stats_inc(&stats->transfers); in spi_statistics_add_transfer_stats()
1257 list_for_each_entry(xfer, &msg->transfers, transfer_list) { in __spi_map_msg()
1306 list_for_each_entry(xfer, &msg->transfers, transfer_list) { in __spi_unmap_msg()
1376 list_for_each_entry(xfer, &msg->transfers, transfer_list) { in spi_unmap_msg()
1401 list_for_each_entry(xfer, &msg->transfers, transfer_list) { in spi_map_msg()
1427 list_for_each_entry(xfer, &msg->transfers, in spi_map_msg()
1613 xfer = list_first_entry(&msg->transfers, struct spi_transfer, transfer_list); in spi_transfer_one_message()
1619 list_for_each_entry(xfer, &msg->transfers, transfer_list) { in spi_transfer_one_message()
1684 &msg->transfers)) { in spi_transfer_one_message()
[all …]
H A Dspi-test.h75 struct spi_transfer transfers[SPI_TEST_MAX_TRANSFERS]; member
/linux/drivers/staging/greybus/
H A Dspilib.c131 if (last_xfer == list_last_entry(&msg->transfers, in setup_next_xfer()
154 if (xfer == list_last_entry(&msg->transfers, struct spi_transfer, in get_next_xfer()
242 gb_xfer = &request->transfers[0]; in gb_spi_operation_create()
336 spi->first_xfer = list_first_entry_or_null(&msg->transfers, in gb_spi_transfer_one_message()
/linux/include/linux/spi/
H A Dspi.h77 u64_stats_t transfers; member
1192 struct list_head transfers; member
1248 INIT_LIST_HEAD(&m->transfers); in spi_message_init_no_memset()
1261 list_add_tail(&t->transfer_list, &m->transfers); in spi_message_add_tail()
1762 return list_is_last(&xfer->transfer_list, &ctlr->cur_msg->transfers); in spi_transfer_is_last()
/linux/drivers/usb/gadget/udc/cdns2/
H A DKconfig7 data transfers.
/linux/Documentation/devicetree/bindings/mips/cavium/
H A Ddma-engine.txt3 The Octeon DMA Engine transfers between the Boot Bus and main memory.
/linux/drivers/usb/renesas_usbhs/
H A DKconfig13 that supports both full and high speed USB 2.0 data transfers.
/linux/Documentation/arch/riscv/
H A Dzicfilp.rst7 Tracking indirect control transfers on RISC-V Linux
28 restriction on such indirect control transfers:
30 - Indirect control transfers must land on a landing pad instruction ``lpad``.

1234567