/openbmc/linux/Documentation/devicetree/bindings/iio/pressure/ |
H A D | honeywell,mprls0025pa.yaml | 20 differ in the pressure range, unit and transfer function. 23 the transfer function. Pressure range needs to be converted from its unit to 26 The transfer function defines the ranges of numerical values delivered by the 63 honeywell,transfer-function: 80 - honeywell,transfer-function 101 honeywell,transfer-function = <1>;
|
/openbmc/linux/drivers/mmc/host/ |
H A D | litex_mmc.c | 124 u8 cmd, u32 arg, u8 response_len, u8 transfer) in litex_mmc_send_cmd() argument 133 cmd << 8 | transfer << 5 | response_len); in litex_mmc_send_cmd() 141 (transfer != SD_CTL_DATA_XFER_NONE || in litex_mmc_send_cmd() 169 if (transfer == SD_CTL_DATA_XFER_NONE) in litex_mmc_send_cmd() 179 reg = (transfer == SD_CTL_DATA_XFER_READ) ? in litex_mmc_send_cmd() 292 unsigned int *len, bool *direct, u8 *transfer) in litex_mmc_do_dma() argument 319 *transfer = SD_CTL_DATA_XFER_READ; in litex_mmc_do_dma() 328 *transfer = SD_CTL_DATA_XFER_WRITE; in litex_mmc_do_dma() 350 u8 transfer = SD_CTL_DATA_XFER_NONE; in litex_mmc_request() local 390 response_len, transfer); in litex_mmc_request() [all …]
|
/openbmc/linux/Documentation/driver-api/mmc/ |
H A D | mmc-async-req.rst | 13 transfer, the DMA preparation overhead would not affect the MMC performance. 35 in parallel with the transfer performance won't be affected. 67 with the previous transfer, since there is no previous request. 73 and finally prepare the second chunk and start the transfer. 78 /* start MMC transfer for the complete transfer size */ 86 * the transfer is delayed, guesstimate max 4k as first chunk size. 96 * before this call, the transfer is delayed.
|
/openbmc/linux/Documentation/mhi/ |
H A D | mhi.rst | 81 Two unidirectional channels with their associated transfer rings form a 85 transfer ring. 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. 120 memory. EDs consist of one or more ring elements (or transfer blocks):: 143 A Ring Element is a data structure used to transfer a single block 204 MHI data transfer is initiated by the host to transfer data to the device. 205 Following are the sequence of operations performed by the host to transfer 209 * Host increments the WP of the corresponding channel transfer ring. [all …]
|
/openbmc/linux/drivers/spi/ |
H A D | spi-imx.c | 234 struct spi_transfer *transfer) in spi_imx_can_dma() argument 1394 struct spi_transfer *transfer) in spi_imx_dma_transfer() argument 1400 struct sg_table *tx = &transfer->tx_sg, *rx = &transfer->rx_sg; in spi_imx_dma_transfer() 1490 struct spi_transfer *transfer) in spi_imx_pio_transfer() argument 1498 spi_imx->count = transfer->len; in spi_imx_pio_transfer() 1522 struct spi_transfer *transfer) in spi_imx_poll_transfer() argument 1529 spi_imx->count = transfer->len; in spi_imx_poll_transfer() 1584 spi_imx->count = transfer->len; in spi_imx_pio_transfer_target() 1615 struct spi_transfer *transfer) in spi_imx_transfer_one() argument 1620 spi_imx_setupxfer(spi, transfer); in spi_imx_transfer_one() [all …]
|
H A D | spi-cadence.c | 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() 292 struct spi_transfer *transfer) in cdns_spi_setup_transfer() argument 296 cdns_spi_config_clock_freq(spi, transfer); in cdns_spi_setup_transfer() 429 struct spi_transfer *transfer) in cdns_transfer_one() argument 433 xspi->txbuf = transfer->tx_buf; in cdns_transfer_one() 434 xspi->rxbuf = transfer->rx_buf; in cdns_transfer_one() 435 xspi->tx_bytes = transfer->len; in cdns_transfer_one() 436 xspi->rx_bytes = transfer->len; in cdns_transfer_one() 439 cdns_spi_setup_transfer(spi, transfer); in cdns_transfer_one() [all …]
|
H A D | spi-dw-core.c | 386 struct spi_transfer *transfer) in dw_spi_poll_transfer() argument 399 spi_delay_exec(&delay, transfer); in dw_spi_poll_transfer() 413 struct spi_transfer *transfer) in dw_spi_transfer_one() argument 418 .dfs = transfer->bits_per_word, in dw_spi_transfer_one() 419 .freq = transfer->speed_hz, in dw_spi_transfer_one() 428 dws->tx = (void *)transfer->tx_buf; in dw_spi_transfer_one() 429 dws->tx_len = transfer->len / dws->n_bytes; in dw_spi_transfer_one() 430 dws->rx = transfer->rx_buf; in dw_spi_transfer_one() 440 transfer->effective_speed_hz = dws->current_freq; in dw_spi_transfer_one() 450 ret = dws->dma_ops->dma_setup(dws, transfer); in dw_spi_transfer_one() [all …]
|
H A D | spi-stm32.c | 761 return (transfer->len > dma_size); in stm32_spi_can_dma() 1409 struct spi_transfer *transfer) in stm32_spi_communication_type() argument 1420 if (!transfer->tx_buf) in stm32_spi_communication_type() 1425 if (!transfer->tx_buf) in stm32_spi_communication_type() 1427 else if (!transfer->rx_buf) in stm32_spi_communication_type() 1553 struct spi_transfer *transfer) in stm32_spi_transfer_one_setup() argument 1562 spi->cur_xferlen = transfer->len; in stm32_spi_transfer_one_setup() 1592 nb_words = transfer->len; in stm32_spi_transfer_one_setup() 1633 struct spi_transfer *transfer) in stm32_spi_transfer_one() argument 1638 spi->tx_buf = transfer->tx_buf; in stm32_spi_transfer_one() [all …]
|
H A D | spi-bitbang.c | 286 struct spi_transfer *transfer) in spi_bitbang_transfer_one() argument 292 status = bitbang->setup_transfer(spi, transfer); in spi_bitbang_transfer_one() 297 if (transfer->len) in spi_bitbang_transfer_one() 298 status = bitbang->txrx_bufs(spi, transfer); in spi_bitbang_transfer_one() 300 if (status == transfer->len) in spi_bitbang_transfer_one() 366 if (master->transfer || master->transfer_one_message) in spi_bitbang_init()
|
/openbmc/linux/Documentation/devicetree/bindings/dma/ |
H A D | milbeaut-m10v-hdmac.txt | 3 Milbeaut AHB DMA controller has transfer capability below. 4 - device to memory transfer 5 - memory to device transfer
|
/openbmc/linux/Documentation/devicetree/bindings/misc/ |
H A D | atmel-ssc.txt | 5 - atmel,at91rm9200-ssc: support pdc transfer 6 - atmel,at91sam9g45-ssc: support dma transfer 31 - PDC transfer: 40 - DMA transfer:
|
/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. 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. 65 can triggers STM32 MDMA transfer. STM32 MDMA can clear the request generated 197 destination address increment, block transfer with 128 bytes per single 198 transfer 362 the overal transfer: 375 transfer or the period completion. 380 in case of cyclic transfer. You can terminate it whatever the kind of transfer. [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/spi/ |
H A D | spi-xilinx.yaml | 33 xlnx,num-transfer-bits: 34 description: Number of bits per transfer. This will be 8 if not specified. 53 xlnx,num-transfer-bits = <32>;
|
/openbmc/linux/drivers/net/ethernet/asix/ |
H A D | Kconfig | 23 bool "SPI transfer compression" 27 Say Y here to enable SPI transfer compression. It saves up 28 to 24 dummy cycles during each transfer which may noticeably
|
/openbmc/linux/Documentation/networking/ |
H A D | plip.rst | 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 129 The cable for the first transfer mode is a standard 162 The second data transfer method relies on both machines having 170 The cable for this transfer mode should be constructed as follows:: 193 PLIP Mode 0 transfer protocol 196 The PLIP driver is compatible with the "Crynwr" parallel port transfer [all …]
|
/openbmc/linux/Documentation/driver-api/soundwire/ |
H A D | locking.rst | 29 SoundWire message transfer lock. This mutex is part of 38 Message transfer. 40 1. For every message transfer 74 2. For every message transfer in Prepare operation
|
/openbmc/u-boot/doc/ |
H A D | README.dfutftp | 30 the relatively low transfer speed for large files. 32 of only EP0 for transfer. By using Ethernet we can circumvent 42 The "dfu" command has been extended to support transfer via TFTP - one 75 "ethact=usb_ether". In this way one can have very fast DFU transfer via USB. 77 For 33MiB test image the transfer rate was 1MiB/s for ETH over USB and 200KiB/s 78 for pure DFU USB transfer.
|
H A D | README.update | 8 server in NOR Flash. In more detail: a TFTP transfer of a file given in 13 TFTP transfer is successful, the hash of each update is verified, and if the 31 Normally, TFTP transfer of the update file is done to the address specified 33 transfer is made to the address given in CONFIG_UPDATE_LOAD_ADDR (0x100000 40 server. Since a transfer is attempted during each boot, it is undesirable to 55 If an optional, non-zero address is provided as argument, the TFTP transfer
|
/openbmc/linux/Documentation/driver-api/dmaengine/ |
H A D | client.rst | 91 setting the DMA_PREP_REPEAT transfer flag. 93 A non-NULL return of this transfer API represents a "descriptor" for 180 after their transfer completion callback has run for the descriptor. 181 If no completion callback has been defined for the transfer, then the 183 In other words: if the aim is to read back metadata after the transfer is 211 3. submit the transfer 218 3. submit the transfer 232 5. submit the transfer 237 2. submit the transfer 270 After calling ``dmaengine_submit()`` the submitted transfer descriptor [all …]
|
/openbmc/libpldm/docs/oem/meta/ |
H A D | file-io.md | 38 | 0 | uint8 | TransferFlag | The transfer flag that indiates what part of the transfer this r… 52 | 0 | uint8 | TransferFlag | The transfer flag that indiates what part of the transfer this…
|
/openbmc/linux/Documentation/core-api/ |
H A D | dma-isa-lpc.rst | 38 Also the transfer block may not cross page boundaries (which are 64 87 Now for the good stuff, the actual DMA transfer. :) 101 transfer using set_dma_mode(). Currently you have the options 104 Set the address from where the transfer should start (this needs to 106 transfer. Note that it's _bytes_. The DMA routines will do all the 112 Once the DMA transfer is finished (or timed out) you should disable 140 printk(KERN_ERR "driver: Incomplete DMA transfer!" 149 suspended while a DMA transfer is in progress. Also, all DMA settings
|
/openbmc/linux/drivers/s390/char/ |
H A D | hmcdrv_ftp.c | 34 ssize_t (*transfer)(const struct hmcdrv_ftp_cmdspec *ftp, member 170 len = hmcdrv_cache_cmd(ftp, hmcdrv_ftp_funcs->transfer); in hmcdrv_ftp_do() 297 .transfer = diag_ftp_cmd in hmcdrv_ftp_startup() 303 .transfer = sclp_ftp_cmd in hmcdrv_ftp_startup()
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/ |
H A D | Entry.interface.yaml | 14 The transfer will be initiated to the target provide. The caller of 15 this function should set up a method to transfer and pass the URI to 17 transfer is successfully initiated. Once the transfer is completed.
|
/openbmc/u-boot/drivers/i2c/ |
H A D | ihs_i2c.c | 210 int transfer = min(len, 2); in ihs_i2c_send_buffer() local 211 bool is_last = len <= transfer; in ihs_i2c_send_buffer() 214 if (ihs_i2c_transfer(dev, chip, data, transfer, read, in ihs_i2c_send_buffer() 218 if (ihs_i2c_transfer(chip, data, transfer, read, in ihs_i2c_send_buffer() 223 data += transfer; in ihs_i2c_send_buffer() 224 len -= transfer; in ihs_i2c_send_buffer()
|
/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 92 general. The default transfer function is ``V4L2_XFER_FUNC_709``. The 209 and computer graphics. The default transfer function is 356 definition television (UHDTV). The default transfer function is 611 709 transfer function is recommended in the literature: 651 The default transfer function is 682 The Rec. 709 transfer function is recommended in the literature: 721 reference are identical to sRGB. The transfer function use is 744 The :ref:`smpte2084` standard defines the transfer function used by [all …]
|