SourceVu will show references to pcnt_unit_register_event_callbacks() from the following samples and libraries:
Symbols ![]()
loading...
Files ![]()
loading (2/5)...
pcnt_unit_register_event_callbacks() function
Set event callbacks for PCNT unit
Syntax
esp_err_t pcnt_unit_register_event_callbacks(pcnt_unit_handle_t unit,
const pcnt_event_callbacks_t *cbs,
void *user_data);
Implemented in ![]()
pulse_cnt.c:506
Return value
- ESP_OK: Set event callbacks successfully - ESP_ERR_INVALID_ARG: Set event callbacks failed because of invalid argument - ESP_ERR_INVALID_STATE: Set event callbacks failed because the unit is not in init state - ESP_FAIL: Set event callbacks failed because of other error
Notes
User registered callbacks are expected to be runnable within ISR context The first call to this function needs to be before the call to `pcnt_unit_enable` User can deregister a previously registered callback by calling this function and setting the callback member in the `cbs` structure to NULL.
Related Functions
Found 16 other functions taking a ![]()
pcnt_unit_t
argument:
Function
Description
Create PCNT channel for specific unit, each PCNT has several channels associated with it
Add a watch point for PCNT unit, PCNT will generate an event when the counter value reaches the watch point value
Start the PCNT unit, the counter will start to count according to the edge and/or level input signals
Clear PCNT pulse count value to zero
Get PCNT count value
Set glitch filter for PCNT unit
Enable the PCNT unit
Remove a watch point for PCNT unit
Disable the PCNT unit
Stop PCNT from counting
Delete the PCNT unit handle
Add a step notify for PCNT unit, PCNT will generate an event when the incremental(can be positive or negative) of counter value reaches the step interval
Remove a step notify for PCNT unit
Examples
Code
Location
Call Tree
from 0/1 examplespcnt_unit_register_event_callbacks() calls 7 functions:
Data Use
from 0/1 examplespcnt_unit_register_event_callbacks() reads 20 variables and writes 2 variables: