SourceVu will show references to i2c_slave_register_event_callbacks() from the following samples and libraries:
Symbols ![]()
loading...
Files ![]()
loading...
i2c_slave_register_event_callbacks() function
Set I2C slave event callbacks for I2C slave channel.
Syntax
esp_err_t i2c_slave_register_event_callbacks(i2c_slave_dev_handle_t i2c_slave,
const i2c_slave_event_callbacks_t *cbs,
void *user_data);
Implemented in ![]()
i2c_slave.c:417
Return value
- ESP_OK: Set I2C transaction callbacks successfully - ESP_ERR_INVALID_ARG: Set I2C transaction callbacks failed because of invalid argument - ESP_FAIL: Set I2C transaction callbacks failed because of other error
Notes
User can deregister a previously registered callback by calling this function and setting the callback member in the `cbs` structure to NULL. When CONFIG_I2C_ISR_IRAM_SAFE is enabled, the callback itself and functions called by it should be placed in IRAM. The variables used in the function should be in the SRAM as well. The `user_data` should also reside in SRAM.
Related Functions
Found 13 other functions taking a ![]()
i2c_slave_dev_t
argument:
Function
Description
Initialize an I2C slave device
Deinitialize the I2C slave device
Write buffer to hardware fifo. If write length is larger than hardware fifo, then restore in software buffer.
Read bytes from I2C internal buffer. Start a job to receive I2C data.
Write bytes to internal ringbuffer of the I2C slave data. When the TX fifo empty, the ISR will fill the hardware FIFO with the internal ringbuffer's data.
Examples
Code
Location
Call Tree
from 0/1 examplesi2c_slave_register_event_callbacks() calls 2 functions:
Data Use
from 0/1 examplesi2c_slave_register_event_callbacks() reads 9 variables and writes 3 variables: