SourceVu will show references to adc_continuous_register_event_callbacks() from the following samples and libraries:
Symbols ![]()
loading...
Files ![]()
loading (2/5)...
adc_continuous_register_event_callbacks() function
Register callbacks
Syntax
esp_err_t adc_continuous_register_event_callbacks(adc_continuous_handle_t handle,
const adc_continuous_evt_cbs_t *cbs,
void *user_data);
Implemented in ![]()
adc_continuous.c:532
Return value
- ESP_OK: On success - ESP_ERR_INVALID_ARG: Invalid arguments - ESP_ERR_INVALID_STATE: Driver state is invalid, you shouldn't call this API at this moment
Notes
User can deregister a previously registered callback by calling this function and setting the to-be-deregistered callback member in the `cbs` structure to NULL. When CONFIG_ADC_CONTINUOUS_ISR_IRAM_SAFE is enabled, the callback itself and functions called by it should be placed in IRAM. Involved variables (including `user_data`) should be in internal RAM as well. You should only call this API when the ADC continuous mode driver isn't started. Check return value to know this.
Related Functions
Found 10 other functions taking a ![]()
adc_continuous_ctx_t
argument:
Function
Description
Deinitialize the ADC continuous driver.
Start the ADC under continuous mode. After this, the hardware starts working.
Stop the ADC. After this, the hardware stops working.
Read bytes from ADC under continuous mode.
Set ADC continuous mode required configurations
Initialize DMA interrupt event
Flush the driver internal pool
Allocate an ADC continuous mode monitor (and configure it into an initial state)
New an ADC continuous mode IIR filter
Examples
Code
Location
Call Tree
from 0/1 examplesadc_continuous_register_event_callbacks() calls 2 functions:
Data Use
from 0/1 examplesadc_continuous_register_event_callbacks() reads 11 variables and writes 3 variables: