SourceVu will show references to pcnt_unit_set_glitch_filter() from the following samples and libraries:
Symbols ![]()
loading...
Files ![]()
loading (2/5)...
pcnt_unit_set_glitch_filter() function
Set glitch filter for PCNT unit
Syntax
esp_err_t pcnt_unit_set_glitch_filter(pcnt_unit_handle_t unit,
const pcnt_glitch_filter_config_t *config);
Implemented in ![]()
pulse_cnt.c:383
Return value
- ESP_OK: Set glitch filter successfully - ESP_ERR_INVALID_ARG: Set glitch filter failed because of invalid argument (e.g. glitch width is too big) - ESP_ERR_INVALID_STATE: Set glitch filter failed because the unit is not in the init state - ESP_FAIL: Set glitch filter failed because of other error
Notes
This function should be called when the PCNT unit is in the init state (i.e. before calling `pcnt_unit_enable()`)
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
Enable the PCNT unit
Set event callbacks for 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/2 examplespcnt_unit_set_glitch_filter() calls 7 functions:
Data Use
from 0/2 examplespcnt_unit_set_glitch_filter() reads 13 variables: