spi_slave_queue_trans_isr() function

Queue a SPI transaction in ISR If you use both ``spi_slave_queue_trans`` and ``spi_slave_queue_trans_isr`` simultaneously to transfer valid data, you should deal with concurrency issues on your self risk

Syntax

Show:

Summary

Declaration

Definition

from spi_slave_internal.h:74

esp_err_t spi_slave_queue_trans_isr(spi_host_device_t host, const spi_slave_transaction_t *trans_desc);

Implemented in spi_slave.c:433

Arguments

Argument

Description

host

SPI peripheral that is acting as a slave

trans_desc

Description of transaction to execute. Not const because we may want to write status back into the transaction description.

Return value

- ESP_ERR_INVALID_ARG if parameter is invalid - ESP_ERR_NO_MEM if trans_queue is full - ESP_OK on success

Notes

Similar as ``spi_slave_queue_trans``, but can and can only called within an ISR, then get the transaction results through the transaction descriptor passed in ``spi_slave_interface_config_t::post_trans_cb``. if use this API, you should trigger a transaction by normal ``spi_slave_queue_trans`` once and only once to start isr

Examples

References

from examples

spi_slave_queue_trans_isr() function

Syntax

Arguments

Return value

Notes

Examples

References

Call Tree

Data Use

Class Tree

Override Tree

Implementations

Instances

Lifecycle