/linux/Documentation/driver-api/dmaengine/ |
H A D | provider.rst | 21 will want to start a transfer, it will assert a DMA request (DRQ) by 25 parameter: the transfer size. At each clock cycle, it would transfer a 26 byte of data from one buffer to another, until the transfer size has 31 cycle. For example, we may want to transfer as much data as the 36 parameter called the transfer width. 44 transfer into smaller sub-transfers. 59 transfer, and whenever the transfer is started, the controller will go 73 transfer width and the transfer size. 118 should contain a bitmask of the supported source transfer width 121 should contain a bitmask of the supported destination transfer width [all …]
|
H A D | pxa_dma.rst | 9 A driver submitting a transfer and issuing it should be granted the transfer 11 This implies that the queuing doesn't wait for the previous transfer end, 13 triggered by the end of the transfer. 14 A transfer which is submitted and issued on a phy doesn't wait for a phy to 17 a new transfer. 20 Any issued transfer with DMA_PREP_INTERRUPT should trigger a callback call. 27 multimedia case, such as video capture, if a transfer is submitted and then 28 a check of the DMA channel reports a "stopped channel", the transfer should 44 assigned on the fly when the transfer is issued. 46 b) Transfer anatomy for a scatter-gather transfer [all …]
|
H A D | client.rst | 95 setting the DMA_PREP_REPEAT transfer flag. 97 A non-NULL return of this transfer API represents a "descriptor" for 189 after their transfer completion callback has run for the descriptor. 190 If no completion callback has been defined for the transfer, then the 192 In other words: if the aim is to read back metadata after the transfer is 220 3. submit the transfer 227 3. submit the transfer 228 4. when the transfer is completed, the metadata should be available in the 241 5. submit the transfer 246 2. submit the transfer [all …]
|
/linux/drivers/net/ethernet/qualcomm/ |
H A D | qca_7k.c | 33 struct spi_transfer transfer[2]; in qcaspi_read_register() local 37 memset(transfer, 0, sizeof(transfer)); in qcaspi_read_register() 44 transfer[0].tx_buf = &tx_data; in qcaspi_read_register() 45 transfer[0].len = QCASPI_CMD_LEN; in qcaspi_read_register() 46 transfer[1].rx_buf = &rx_data; in qcaspi_read_register() 47 transfer[1].len = QCASPI_CMD_LEN; in qcaspi_read_register() 49 spi_message_add_tail(&transfer[0], &msg); in qcaspi_read_register() 55 spi_message_add_tail(&transfer[1], &msg); in qcaspi_read_register() 73 struct spi_transfer transfer[2]; in __qcaspi_write_register() local 77 memset(&transfer, 0, sizeof(transfer)); in __qcaspi_write_register() [all …]
|
H A D | qca_spi.c | 98 struct spi_transfer transfer[2]; in qcaspi_write_burst() local 101 memset(&transfer, 0, sizeof(transfer)); in qcaspi_write_burst() 105 transfer[0].tx_buf = &cmd; in qcaspi_write_burst() 106 transfer[0].len = QCASPI_CMD_LEN; in qcaspi_write_burst() 107 transfer[1].tx_buf = src; in qcaspi_write_burst() 108 transfer[1].len = len; in qcaspi_write_burst() 110 spi_message_add_tail(&transfer[0], &msg); in qcaspi_write_burst() 111 spi_message_add_tail(&transfer[1], &msg); in qcaspi_write_burst() 126 struct spi_transfer transfer; in qcaspi_write_legacy() local 129 memset(&transfer, 0, sizeof(transfer)); in qcaspi_write_legacy() [all …]
|
/linux/drivers/mtd/devices/ |
H A D | mchp23k256.c | 64 struct spi_transfer transfer[2] = {}; in mchp23k256_write() local 76 transfer[0].tx_buf = command; in mchp23k256_write() 77 transfer[0].len = cmd_len; in mchp23k256_write() 78 spi_message_add_tail(&transfer[0], &message); in mchp23k256_write() 80 transfer[1].tx_buf = buf; in mchp23k256_write() 81 transfer[1].len = len; in mchp23k256_write() 82 spi_message_add_tail(&transfer[1], &message); in mchp23k256_write() 103 struct spi_transfer transfer[2] = {}; in mchp23k256_read() local 112 memset(&transfer, 0, sizeof(transfer)); in mchp23k256_read() 116 transfer[0].tx_buf = command; in mchp23k256_read() [all …]
|
/linux/Documentation/mhi/ |
H A D | mhi.rst | 58 Transfer rings: Used by the host to schedule work items for a channel. The 59 transfer rings are organized as a circular queue of Transfer Descriptors (TD). 81 Two unidirectional channels with their associated transfer rings form a 85 transfer ring. 87 Transfer rings 91 Transfer Descriptors (TD). TDs are managed through transfer rings, which are 93 memory. TDs consist of one or more ring elements (or transfer blocks):: 101 Below is the basic usage of transfer rings: 103 * Host allocates memory for transfer ring. 118 data transfer completion status, command completion status, and state changes [all …]
|
/linux/drivers/net/wireless/ralink/rt2x00/ |
H A D | rt2x00crypto.c | 152 unsigned int transfer = 0; in rt2x00crypto_rx_insert_iv() local 194 memmove(skb->data + transfer, in rt2x00crypto_rx_insert_iv() 195 skb->data + transfer + (iv_len - align), in rt2x00crypto_rx_insert_iv() 197 transfer += header_length; in rt2x00crypto_rx_insert_iv() 203 memmove(skb->data + transfer, in rt2x00crypto_rx_insert_iv() 204 skb->data + transfer + iv_len + align, in rt2x00crypto_rx_insert_iv() 206 transfer += header_length; in rt2x00crypto_rx_insert_iv() 210 memcpy(skb->data + transfer, rxdesc->iv, iv_len); in rt2x00crypto_rx_insert_iv() 211 transfer += iv_len; in rt2x00crypto_rx_insert_iv() 218 memmove(skb->data + transfer, in rt2x00crypto_rx_insert_iv() [all …]
|
/linux/Documentation/userspace-api/media/v4l/ |
H A D | colorspaces-details.rst | 14 PAL and by SDTV in general. The default transfer function is 45 The transfer function defined for SMPTE 170M is the same as the one 56 Inverse Transfer function: 92 general. The default transfer function is ``V4L2_XFER_FUNC_709``. The 121 Transfer function. Normally L is in the range [0…1], but for the 132 Inverse Transfer function: 209 and computer graphics. The default transfer function is 244 Transfer function. Note that negative values for L are only used by the 255 Inverse Transfer function: 287 graphics that use the opRGB colorspace. The default transfer function is [all …]
|
H A D | colorspaces-defs.rst | 9 which defines the chromaticities, the default transfer function, the 11 is the transfer function identifier (enum 13 transfer functions. The third is the Y'CbCr encoding identifier (enum 80 .. flat-table:: V4L2 Transfer Function 87 - Use the default transfer function as defined by the colorspace. 89 - Use the Rec. 709 transfer function. 91 - Use the sRGB transfer function. 93 - Use the opRGB transfer function. 95 - Use the SMPTE 240M transfer function. 97 - Do not use a transfer function (i.e. use linear RGB values). [all …]
|
/linux/include/linux/spi/ |
H A D | spi.h | 62 * transfer bytes histogram 136 * The spi_transfer.speed_hz can override this for each transfer. 143 * each word in a transfer (by specifying SPI_LSB_FIRST). 149 * The spi_transfer.bits_per_word can override this for each transfer. 166 * words of a transfer 403 * supported. If set, the SPI core will reject any transfer with an 406 * @min_speed_hz: Lowest supported transfer speed 407 * @max_speed_hz: Highest supported transfer speed 412 * @max_transfer_size: function that returns the max transfer size for 429 * @transfer: adds a message to the controller's transfer queue. [all …]
|
/linux/sound/core/ |
H A D | isadma.c | 19 * snd_dma_program - program an ISA DMA transfer 22 * @size: the DMA transfer size 23 * @mode: the DMA transfer mode, DMA_MODE_XXX 25 * Programs an ISA DMA transfer for the given buffer. 46 * snd_dma_disable - stop the ISA DMA transfer 49 * Stops the ISA DMA transfer. 63 * snd_dma_pointer - return the current pointer to DMA transfer buffer in bytes 65 * @size: the dma transfer size 67 * Return: The current pointer in DMA transfer buffer in bytes. 92 …pr_err("ALSA: pointer (0x%x) for DMA #%ld is greater than transfer size (0x%x)\n", result, dma, si… in snd_dma_pointer()
|
/linux/Documentation/arch/arm/stm32/ |
H A D | stm32-dma-mdma-chaining.rst | 30 without the ability to generate convenient burst transfer ensuring the best 54 the STM32 DMA transfer. 58 channel is null. The channel transfer complete of the last node is the end of 59 transfer, unless first and last nodes are linked to each other, in such a 60 case, the linked-list loops on to create a circular MDMA transfer. 64 resources and bus congestion. Transfer Complete signal of STM32 DMA channel 65 can triggers STM32 MDMA transfer. STM32 MDMA can clear the request generated 73 | channels | channels | Transfer | request | 133 * the address of the STM32 DMA register to clear the Transfer Complete 135 * the mask of the Transfer Complete interrupt flag of the STM32 DMA channel. [all …]
|
/linux/drivers/scsi/ |
H A D | dc395x.h | 250 #define SCSIXFERDONE 0x0800 /* SCSI SCSI transfer done */ 251 #define SCSIXFERCNT_2_ZERO 0x0100 /* SCSI SCSI transfer count to zero */ 273 #define DO_CLRFIFO 0x0004 /* Clear SCSI transfer FIFO */ 319 /* transfer. */ 325 /* are used to transfer data */ 330 /* are used to transfer data */ 333 /* 02-00 0 PERIOD[2:0]/ Synchronous SCSI Transfer Rate. */ 335 /* the Synchronous SCSI Transfer */ 381 #define TRM_S1040_SCSI_COUNTER 0x88 /* SCSI Transfer Counter 24bits(R/W) */ 413 #define SCMD_FIFO_OUT 0xC0 /* SCSI FIFO transfer out */ [all …]
|
/linux/drivers/usb/dwc2/ |
H A D | hcd.h | 48 * @xfer_buf: Pointer to current transfer buffer position 52 * @xfer_len: Total number of bytes to transfer 54 * @start_pkt_count: Packet count at start of transfer 55 * @xfer_started: True if the transfer has been started 74 * assigned to the current transfer (not counting PINGs) 76 * @ntd: Number of transfer descriptors for the transfer 79 * @qh: QH for the transfer being processed by this channel 86 * host mode. It contains the data items needed to transfer packets to an 213 * struct dwc2_hs_transfer_time - Info about a transfer on the high speed bus. 220 * @duration_us: How long this transfer goes. [all …]
|
/linux/drivers/usb/image/ |
H A D | microtek.c | 78 * 20000515 Put transfer context and URB in mts_desc (john) 191 MTS_DEBUG("transfer = 0x%x context = 0x%x\n",(int)transfer,(int)context ); \ 192 …status = 0x%x data-length = 0x%x sent = 0x%x\n",transfer->status,(int)context->data_length, (int)t… 208 struct mts_transfer_context* context = (struct mts_transfer_context*)transfer->context; \ 361 static void mts_transfer_cleanup( struct urb *transfer ); 362 static void mts_do_sg(struct urb * transfer); 365 void mts_int_submit_urb (struct urb* transfer, in mts_int_submit_urb() argument 372 /* Holding transfer->context->lock! */ in mts_int_submit_urb() 378 usb_fill_bulk_urb(transfer, in mts_int_submit_urb() 387 res = usb_submit_urb( transfer, GFP_ATOMIC ); in mts_int_submit_urb() [all …]
|
/linux/Documentation/devicetree/bindings/dma/stm32/ |
H A D | st,stm32-mdma.yaml | 24 0x2: Source address pointer is incremented after each data transfer 25 0x3: Source address pointer is decremented after each data transfer 28 0x2: Destination address pointer is incremented after each data transfer 29 0x3: Destination address pointer is decremented after each data transfer 40 -bit 25-18: The number of bytes to be transferred in a single transfer 43 0x00: Each MDMA request triggers a buffer transfer (max 128 bytes) 44 0x1: Each MDMA request triggers a block transfer (max 64K bytes) 45 0x2: Each MDMA request triggers a repeated block transfer 46 0x3: Each MDMA request triggers a linked list transfer
|
/linux/drivers/i3c/master/mipi-i3c-hci/ |
H A D | xfer_mode_rate.h | 7 * Transfer Mode/Rate Table definitions as found in extended capability 16 * Master Transfer Mode Table Fixed Indexes. 29 * Transfer Mode Table Entry Bits Definitions 38 * Master Data Transfer Rate Selector Values. 44 * Data Transfer Rate Table. Indicated are typical rates. The actual 45 * rates may vary slightly and are also specified in the Data Transfer 67 * Master Data Transfer Rate Table Mode ID values. 73 * Master Data Transfer Rate Table Entry Bits Definitions
|
/linux/arch/sh/drivers/pci/ |
H A D | pci-sh4.h | 59 #define SH4_PCICLR_MDMA0 0x40000000 /* DMA0 Transfer Error */ 60 #define SH4_PCICLR_MDMA1 0x20000000 /* DMA1 Transfer Error */ 61 #define SH4_PCICLR_MDMA2 0x10000000 /* DMA2 Transfer Error */ 62 #define SH4_PCICLR_MDMA3 0x08000000 /* DMA3 Transfer Error */ 63 #define SH4_PCICLR_TGT 0x04000000 /* Target Transfer Error */ 80 #define SH4_PCIDMABT 0x140 /* DMA Transfer Arb. Register */ 82 #define SH4_PCIDPA0 0x180 /* DMA0 Transfer Addr. */ 84 #define SH4_PCIDTC0 0x188 /* DMA0 Transfer Cnt. */ 93 #define SH4_PCIDCR_DIR 0x00000004 /* DMA Transfer Direction */ 96 #define SH4_PCIDPA1 0x190 /* DMA1 Transfer Addr. */ [all …]
|
/linux/drivers/spi/ |
H A D | spi-fsi.c | 299 struct spi_transfer *transfer) in fsi_spi_transfer_data() argument 306 if (transfer->tx_buf) { in fsi_spi_transfer_data() 310 const u8 *tx = transfer->tx_buf; in fsi_spi_transfer_data() 312 while (transfer->len > sent) { in fsi_spi_transfer_data() 314 (int)transfer->len - sent); in fsi_spi_transfer_data() 333 } else if (transfer->rx_buf) { in fsi_spi_transfer_data() 336 u8 *rx = transfer->rx_buf; in fsi_spi_transfer_data() 338 while (transfer->len > recv) { in fsi_spi_transfer_data() 355 (int)transfer->len - recv); in fsi_spi_transfer_data() 430 struct spi_transfer *transfer; in fsi_spi_transfer_one_message() local [all …]
|
/linux/include/linux/ |
H A D | atmel_pdc.h | 24 #define ATMEL_PDC_PTCR 0x120 /* Transfer Control Register */ 25 #define ATMEL_PDC_RXTEN (1 << 0) /* Receiver Transfer Enable */ 26 #define ATMEL_PDC_RXTDIS (1 << 1) /* Receiver Transfer Disable */ 27 #define ATMEL_PDC_TXTEN (1 << 8) /* Transmitter Transfer Enable */ 28 #define ATMEL_PDC_TXTDIS (1 << 9) /* Transmitter Transfer Disable */ 30 #define ATMEL_PDC_PTSR 0x124 /* Transfer Status Register */
|
/linux/drivers/mmc/core/ |
H A D | sdio_io.c | 147 * data transfer use the optimal (least) number of commands. 187 * Calculate the maximum byte mode transfer size 220 * sdio_align_size - pads a transfer size to a more optimal value 222 * @sz: original transfer size 249 * If we can still do this with just a byte transfer, then in sdio_align_size() 257 * Check if the transfer is already block aligned in sdio_align_size() 313 /* Split an arbitrarily sized data transfer into several 325 /* Do the bulk of the transfer using block mode (if supported). */ in sdio_io_rw_ext_helper() 327 /* Blocks per command is limited by host count, host transfer in sdio_io_rw_ext_helper() 374 * @err_ret: optional status value from transfer [all …]
|
/linux/drivers/cxl/core/ |
H A D | memdev.c | 774 * cxl_mem_abort_fw_xfer - Abort an in-progress FW transfer 777 * Abort an in-progress firmware transfer for the device specified. 781 * See CXL-3.0 8.2.9.3.2 Transfer FW 786 struct cxl_mbox_transfer_fw *transfer; in cxl_mem_abort_fw_xfer() local 790 transfer = kzalloc(struct_size(transfer, data, 0), GFP_KERNEL); in cxl_mem_abort_fw_xfer() 791 if (!transfer) in cxl_mem_abort_fw_xfer() 797 .size_in = sizeof(*transfer), in cxl_mem_abort_fw_xfer() 798 .payload_in = transfer, in cxl_mem_abort_fw_xfer() 803 transfer->action = CXL_FW_TRANSFER_ACTION_ABORT; in cxl_mem_abort_fw_xfer() 806 kfree(transfer); in cxl_mem_abort_fw_xfer() [all …]
|
/linux/Documentation/driver-api/usb/ |
H A D | error-codes.rst | 13 behave the same except for transfer speed dependent behaviors and the 42 ``-EINVAL`` a) Invalid transfer type specified (or not supported) 43 b) Invalid or unsupported periodic transfer interval 44 c) ISO: attempted to change transfer interval 61 (c) requested data transfer length is invalid: negative 87 A transfer's actual_length may be positive even when an error has been 101 0 Transfer completed successfully 132 to indicate timeout expired before the transfer 140 ``-ECOMM`` During an IN transfer, the host controller 144 ``-ENOSR`` During an OUT transfer, the host controller [all …]
|
/linux/Documentation/networking/ |
H A D | plip.rst | 83 mode as compared to IRQ mode as far as the data transfer speed is involved. 87 data transfer (the maximal time the PLIP driver would allow the other side 88 before announcing a timeout, when trying to handshake a transfer of some 116 PLIP uses several different data transfer methods. The first (and the 118 printer "null" cable to transfer data four bits at a time using 121 The second data transfer method relies on both machines having 126 Parallel Transfer Mode 0 Cable 129 The cable for the first transfer mode is a standard 159 Parallel Transfer Mode 1 162 The second data transfer method relies on both machines having [all …]
|