SourceVu will show references to spi_device_interface_config_t from the following samples and libraries:
Symbols ![]()
loading...
Files ![]()
loading...
spi_device_interface_config_t struct
This is a configuration for a SPI slave device that is connected to one of the SPI buses.
Syntax
typedef struct
{
uint8_t command_bits;
uint8_t address_bits;
uint8_t dummy_bits;
uint8_t mode;
spi_clock_source_t clock_source;
uint16_t duty_cycle_pos;
uint16_t cs_ena_pretrans;
uint8_t cs_ena_posttrans;
int clock_speed_hz;
int input_delay_ns;
spi_sampling_point_t sample_point;
int spics_io_num;
uint32_t flags;
int queue_size;
transaction_cb_t pre_cb;
transaction_cb_t post_cb;
} spi_device_interface_config_t;
Fields
Field
Declared as
Description
uint8_t
SPI mode, representing a pair of (CPOL, CPHA) configuration: - 0: (0, 0) - 1: (0, 1) - 2: (1, 0) - 3: (1, 1).
int
Maximum data valid time of slave. The time required between SCLK and MISO valid, including the possible clock delay from slave to master. The driver uses this value to give an extra delay before the MISO is ready on the line. Leave at 0 unless you know you need a delay. For better timing performance at high frequency (over 8MHz), it's suggest to have the right value.
Callback to be called before a transmission is started. This callback is called within interrupt context should be in IRAM for best performance, see "Transferring Speed" section in the SPI Master documentation for full details. If not, the callback may crash during flash operation when the driver is initialized with ESP_INTR_FLAG_IRAM.
Callback to be called after a transmission has completed. This callback is called within interrupt context should be in IRAM for best performance, see "Transferring Speed" section in the SPI Master documentation for full details. If not, the callback may crash during flash operation when the driver is initialized with ESP_INTR_FLAG_IRAM.