/openbmc/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 …]
|
/openbmc/u-boot/drivers/axi/ |
H A D | ihs_axi.c | 18 * error during transfer, transfer complete, etc.) 23 * device to transfer data from/to 25 * device to transfer data from/to 74 * @STATUS_READ_COMPLETE_EVENT: A read transfer was completed 75 * @STATUS_WRITE_COMPLETE_EVENT: A write transfer was completed 76 * @STATUS_TIMEOUT_EVENT: A timeout has occurred during the transfer 77 * @STATUS_ERROR_EVENT: A error has occurred during the transfer 108 * for the next transfer 109 * @CONTROL_CMD_WRITE: Configure bus to do a write transfer 111 * transfer [all …]
|
/openbmc/linux/drivers/net/ethernet/qualcomm/ |
H A D | qca_7k.c | 48 struct spi_transfer transfer[2]; in qcaspi_read_register() local 52 memset(transfer, 0, sizeof(transfer)); in qcaspi_read_register() 59 transfer[0].tx_buf = &tx_data; in qcaspi_read_register() 60 transfer[0].len = QCASPI_CMD_LEN; in qcaspi_read_register() 61 transfer[1].rx_buf = &rx_data; in qcaspi_read_register() 62 transfer[1].len = QCASPI_CMD_LEN; in qcaspi_read_register() 64 spi_message_add_tail(&transfer[0], &msg); in qcaspi_read_register() 70 spi_message_add_tail(&transfer[1], &msg); in qcaspi_read_register() 88 struct spi_transfer transfer[2]; in __qcaspi_write_register() local 92 memset(&transfer, 0, sizeof(transfer)); in __qcaspi_write_register() [all …]
|
H A D | qca_spi.c | 110 struct spi_transfer transfer[2]; in qcaspi_write_burst() local 113 memset(&transfer, 0, sizeof(transfer)); in qcaspi_write_burst() 117 transfer[0].tx_buf = &cmd; in qcaspi_write_burst() 118 transfer[0].len = QCASPI_CMD_LEN; in qcaspi_write_burst() 119 transfer[1].tx_buf = src; in qcaspi_write_burst() 120 transfer[1].len = len; in qcaspi_write_burst() 122 spi_message_add_tail(&transfer[0], &msg); in qcaspi_write_burst() 123 spi_message_add_tail(&transfer[1], &msg); in qcaspi_write_burst() 138 struct spi_transfer transfer; in qcaspi_write_legacy() local 141 memset(&transfer, 0, sizeof(transfer)); in qcaspi_write_legacy() [all …]
|
/openbmc/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 …]
|
/openbmc/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 …]
|
/openbmc/qemu/hw/display/ |
H A D | virtio-gpu-rutabaga.c | 36 struct rutabaga_transfer transfer = { 0 }; in virtio_gpu_rutabaga_update_cursor() local 51 transfer.x = 0; in virtio_gpu_rutabaga_update_cursor() 52 transfer.y = 0; in virtio_gpu_rutabaga_update_cursor() 53 transfer.z = 0; in virtio_gpu_rutabaga_update_cursor() 54 transfer.w = res->width; in virtio_gpu_rutabaga_update_cursor() 55 transfer.h = res->height; in virtio_gpu_rutabaga_update_cursor() 56 transfer.d = 1; in virtio_gpu_rutabaga_update_cursor() 62 resource_id, &transfer, in virtio_gpu_rutabaga_update_cursor() 241 struct rutabaga_transfer transfer = { 0 }; in rutabaga_cmd_resource_flush() local 271 transfer.x = 0; in rutabaga_cmd_resource_flush() [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/mailbox/ |
H A D | arm,mhuv2.yaml | 33 - Data-transfer: Each transfer is made of one or more words, using one or more 36 - Doorbell: Each transfer is made up of single bit flag, using any one of the 96 The first field of a tuple signifies the transfer protocol, 0 is reserved 97 for doorbell protocol, and 1 is reserved for data-transfer protocol. 103 windows that implement the doorbell protocol. For data-transfer protocol, 105 the data-transfer protocol. 120 7 windows (separately) used in data-transfer protocol. 135 doorbell, or data-transfer protocol, and the second argument (only 144 mboxes = <&mhu 2 0>; // Channel Window Group 2, data transfer protocol with 1 window. 145 mboxes = <&mhu 3 0>; // Channel Window Group 3, data transfer protocol with 5 windows. [all …]
|
/openbmc/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() 206 memmove(skb->data + transfer, in rt2x00crypto_rx_insert_iv() 207 skb->data + transfer + iv_len + align, in rt2x00crypto_rx_insert_iv() 209 transfer += header_length; in rt2x00crypto_rx_insert_iv() 213 memcpy(skb->data + transfer, rxdesc->iv, iv_len); in rt2x00crypto_rx_insert_iv() 214 transfer += iv_len; in rt2x00crypto_rx_insert_iv() 221 memmove(skb->data + transfer, in rt2x00crypto_rx_insert_iv() [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | PowerDistribution.v1_4_0.json | 354 "description": "The configuration settings for an automatic transfer switch.", 355 …erty shall contain the configuration information regarding an automatic transfer switch function f… 366 … "description": "The criteria used to initiate a transfer for an automatic transfer switch.", 367 …This property shall contain the criteria for initiating a transfer within an automatic transfer sw… 420 "AutomaticTransferSwitch": "An automatic power transfer switch.", 424 "ManualTransferSwitch": "A manual power transfer switch.", 438 "description": "The configuration settings for an automatic transfer switch.", 439 …type shall contain the configuration information regarding an automatic transfer switch function f… 501 …"description": "The time in seconds to delay the automatic transfer from the alternate mains circu… 502 …"This property shall contain the time in seconds to delay the automatic transfer from the alternat… [all …]
|
/openbmc/linux/drivers/spi/ |
H A D | spi-mpc52xx.c | 83 /* Details of current transfer (length, and buffer pointers) */ 85 struct spi_transfer *transfer; /* current transfer */ member 112 * Start a new transfer. This is called both by the idle state 113 * for the first transfer in a message, and by the wait state when the 114 * previous transfer in a message is complete. 118 ms->rx_buf = ms->transfer->rx_buf; in mpc52xx_spi_start_transfer() 119 ms->tx_buf = ms->transfer->tx_buf; in mpc52xx_spi_start_transfer() 120 ms->len = ms->transfer->len; in mpc52xx_spi_start_transfer() 125 ms->cs_change = ms->transfer->cs_change; in mpc52xx_spi_start_transfer() 144 * No transfers are in progress; if another transfer is pending then retrieve [all …]
|
H A D | spi-cadence.c | 109 * @tx_bytes: Number of bytes left to transfer 242 * @transfer: Pointer to the spi_transfer structure which provides 243 * information about next transfer setup parameters 248 * is lower than the requested frequency (maximum lower) for the transfer. If 254 struct spi_transfer *transfer) in cdns_spi_config_clock_freq() argument 265 if (xspi->speed_hz != transfer->speed_hz) { in cdns_spi_config_clock_freq() 269 (frequency / (2 << baud_rate_val)) > transfer->speed_hz) in cdns_spi_config_clock_freq() 281 * cdns_spi_setup_transfer - Configure SPI controller for specified transfer 283 * @transfer: Pointer to the spi_transfer structure which provides 284 * information about next transfer setup parameters [all …]
|
H A D | spi-stm32.c | 231 * @transfer_one_dma_start: routine to start transfer a single spi_transfer 284 * @cur_xferlen: current transfer length in bytes 285 * @cur_usedma: boolean to know if dma is used in current transfer 290 * @dma_tx: dma channel for TX transfer 291 * @dma_rx: dma channel for RX transfer 343 /* SPI data transfer is enabled but spi_ker_ck is idle. 738 * stm32_spi_can_dma - Determine if the transfer is eligible for DMA use 741 * @transfer: pointer to spi transfer 743 * If driver has fifo and the current transfer size is greater than fifo size, 744 * use DMA. Otherwise use DMA for transfer longer than defined DMA min bytes. [all …]
|
/openbmc/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()
|
/openbmc/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 …]
|
/openbmc/libpldm/include/libpldm/ |
H A D | fru.h | 246 * Table data transfer 248 * the start of the transfer 261 * next portion of the transfer 262 * @param[in] transfer_flag - The transfer flag that indicates what part of the 263 * transfer this response represents 282 * Table data transfer 289 * the start of the transfer 303 * next portion of the transfer 304 * @param[in] transfer_flag - The transfer flag that indicates what part of the 305 * transfer this response represents [all …]
|
H A D | bios.h | 248 * @param[in] transfer_handle - Handle to identify a BIOS table transfer 249 * @param[in] transfer_flag - Flag to indicate what part of the transfer 276 * next portion of the transfer 288 * @param[in] transfer_handle - Handle to identify a BIOS table transfer 289 * @param[in] transfer_flag - Flag to indicate what part of the transfer 319 * next portion of the transfer 358 * transfer 359 * @param[in] transfer_flag - To indicate what part of the transfer this 374 * @param[in] transfer_handle - Handle to identify a BIOS table transfer 376 * transfer [all …]
|
/openbmc/linux/include/linux/spi/ |
H A D | spi.h | 59 * transfer bytes histogram 134 * The spi_transfer.speed_hz can override this for each transfer. 140 * each word in a transfer (by specifying SPI_LSB_FIRST). 146 * The spi_transfer.bits_per_word can override this for each transfer. 163 * words of a transfer 384 * supported. If set, the SPI core will reject any transfer with an 387 * @min_speed_hz: Lowest supported transfer speed 388 * @max_speed_hz: Highest supported transfer speed 393 * @max_transfer_size: function that returns the max transfer size for 410 * @transfer: adds a message to the controller's transfer queue. [all …]
|
/openbmc/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 …]
|
/openbmc/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
|
/openbmc/linux/Documentation/devicetree/bindings/dma/ |
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
|
/openbmc/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 …]
|
/openbmc/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 …]
|