SourceVu will show references to spi_device_queue_trans() from the following samples and libraries:
Symbols ![]()
loading...
Files ![]()
loading...
spi_device_queue_trans() function
Queue a SPI transaction for interrupt transaction execution. Get the result by ``spi_device_get_trans_result``.
Syntax
esp_err_t spi_device_queue_trans(spi_device_handle_t handle,
spi_transaction_t *trans_desc,
TickType_t ticks_to_wait);
Implemented in ![]()
spi_master.c:1194
Return value
- ESP_ERR_INVALID_ARG if parameter is invalid. This can happen if SPI_TRANS_CS_KEEP_ACTIVE flag is specified while the bus was not acquired (`spi_device_acquire_bus()` should be called first) or set flag SPI_TRANS_DMA_BUFFER_ALIGN_MANUAL but tx or rx buffer not DMA-capable, or addr&len not align to cache line size - ESP_ERR_TIMEOUT if there was no room in the queue before ticks_to_wait expired - ESP_ERR_NO_MEM if allocating DMA-capable temporary buffer failed - ESP_ERR_INVALID_STATE if previous transactions are not finished - ESP_OK on success
Notes
Normally a device cannot start (queue) polling and interrupt transactions simultaneously.
Related Functions
Found 16 other functions taking a ![]()
spi_device_t
argument:
Function
Description
Send a polling transaction, wait for it to complete, and return the result This function is the equivalent of calling spi_device_polling_start() followed by spi_device_polling_end(). Do not use this when there is still a transaction that hasn't been finalized.
Send a SPI transaction, wait for it to complete, and return the result This function is the equivalent of calling spi_device_queue_trans() followed by spi_device_get_trans_result(). Do not use this when there is still a transaction separately queued (started) from spi_device_queue_trans() or polling_start/transmit that hasn't been finalized.
Remove a device from the SPI bus
Allocate a device on a SPI bus This initializes the internal structures for a device, plus allocates a CS pin on the indicated SPI master peripheral and routes it to the indicated GPIO. All SPI master devices have three CS pins and can thus control up to three devices. There's no notable delay on chips other than ESP32.
Calculate working frequency for specific device
Release the SPI bus occupied by the device. All other devices can start sending transactions.
Occupy the SPI bus for a device to do continuous transactions. Transactions to all other devices will be put off until ``spi_device_release_bus`` is called.
Get the result of a SPI transaction queued earlier by ``spi_device_queue_trans``. This routine will wait until a transaction to the given device successfully completed. It will then return the description of the completed transaction so software can inspect the result and e.g. free the memory or reuse the buffers.
Immediately start a polling transaction.
Poll until the polling transaction ends. This routine will not return until the transaction to the given device has successfully completed. The task is not blocked, but actively busy-spins for the transaction to be completed.