2018-06-11 07:54:18 -04:00
|
|
|
menu "Driver configurations"
|
2018-03-07 02:04:43 -05:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
menu "ADC configuration"
|
2018-03-07 02:04:43 -05:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
config ADC_FORCE_XPD_FSM
|
|
|
|
|
bool "Use the FSM to control ADC power"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
ADC power can be controlled by the FSM instead of software. This allows the ADC to
|
|
|
|
|
be shut off when it is not working leading to lower power consumption. However
|
|
|
|
|
using the FSM control ADC power will increase the noise of ADC.
|
2018-03-07 02:04:43 -05:00
|
|
|
|
2019-04-29 08:22:57 -04:00
|
|
|
config ADC_DISABLE_DAC
|
2019-01-25 11:10:53 -05:00
|
|
|
bool "Disable DAC when ADC2 is used on GPIO 25 and 26"
|
|
|
|
|
default y
|
|
|
|
|
help
|
2019-04-29 08:22:57 -04:00
|
|
|
If this is set, the ADC2 driver will disable the output of the DAC corresponding to the specified
|
2019-01-25 11:10:53 -05:00
|
|
|
channel. This is the default value.
|
2018-01-24 05:46:34 -05:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
For testing, disable this option so that we can measure the output of DAC by internal ADC.
|
2018-01-24 05:46:34 -05:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
endmenu # ADC Configuration
|
2018-03-07 02:04:43 -05:00
|
|
|
|
2021-08-25 05:45:46 -04:00
|
|
|
menu "MCPWM configuration"
|
2022-01-17 01:42:09 -05:00
|
|
|
depends on SOC_MCPWM_SUPPORTED
|
2021-08-25 05:45:46 -04:00
|
|
|
config MCPWM_ISR_IN_IRAM
|
|
|
|
|
bool "Place MCPWM ISR function into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If this option is not selected, the MCPWM interrupt will be deferred when the Cache
|
|
|
|
|
is in a disabled state (e.g. Flash write/erase operation).
|
|
|
|
|
|
|
|
|
|
Note that if this option is selected, all user registered ISR callbacks should never
|
|
|
|
|
try to use cache as well. (with IRAM_ATTR)
|
|
|
|
|
endmenu # MCPWM Configuration
|
|
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
menu "SPI configuration"
|
2018-03-07 02:04:43 -05:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
config SPI_MASTER_IN_IRAM
|
|
|
|
|
bool "Place transmitting functions of SPI master into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
select SPI_MASTER_ISR_IN_IRAM
|
|
|
|
|
help
|
|
|
|
|
Normally only the ISR of SPI master is placed in the IRAM, so that it
|
|
|
|
|
can work without the flash when interrupt is triggered.
|
|
|
|
|
For other functions, there's some possibility that the flash cache
|
|
|
|
|
miss when running inside and out of SPI functions, which may increase
|
|
|
|
|
the interval of SPI transactions.
|
|
|
|
|
Enable this to put ``queue_trans``, ``get_trans_result`` and
|
|
|
|
|
``transmit`` functions into the IRAM to avoid possible cache miss.
|
2018-06-11 07:54:18 -04:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
During unit test, this is enabled to measure the ideal case of api.
|
2018-06-11 07:54:18 -04:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
config SPI_MASTER_ISR_IN_IRAM
|
|
|
|
|
bool "Place SPI master ISR function into IRAM"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Place the SPI master ISR in to IRAM to avoid possible cache miss.
|
2018-10-23 04:57:32 -04:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
Also you can forbid the ISR being disabled during flash writing
|
|
|
|
|
access, by add ESP_INTR_FLAG_IRAM when initializing the driver.
|
2018-06-11 07:54:18 -04:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
config SPI_SLAVE_IN_IRAM
|
|
|
|
|
bool "Place transmitting functions of SPI slave into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
select SPI_SLAVE_ISR_IN_IRAM
|
|
|
|
|
help
|
|
|
|
|
Normally only the ISR of SPI slave is placed in the IRAM, so that it
|
|
|
|
|
can work without the flash when interrupt is triggered.
|
|
|
|
|
For other functions, there's some possibility that the flash cache
|
|
|
|
|
miss when running inside and out of SPI functions, which may increase
|
|
|
|
|
the interval of SPI transactions.
|
|
|
|
|
Enable this to put ``queue_trans``, ``get_trans_result`` and
|
|
|
|
|
``transmit`` functions into the IRAM to avoid possible cache miss.
|
2018-08-20 06:30:40 -04:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
config SPI_SLAVE_ISR_IN_IRAM
|
|
|
|
|
bool "Place SPI slave ISR function into IRAM"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Place the SPI slave ISR in to IRAM to avoid possible cache miss.
|
2018-10-23 04:57:32 -04:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
Also you can forbid the ISR being disabled during flash writing
|
|
|
|
|
access, by add ESP_INTR_FLAG_IRAM when initializing the driver.
|
2018-08-20 06:30:40 -04:00
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
endmenu # SPI Configuration
|
2018-06-11 07:54:18 -04:00
|
|
|
|
2020-08-04 00:52:10 -04:00
|
|
|
menu "TWAI configuration"
|
2022-01-20 16:23:45 -05:00
|
|
|
depends on SOC_TWAI_SUPPORTED
|
2020-08-04 00:52:10 -04:00
|
|
|
|
|
|
|
|
config TWAI_ISR_IN_IRAM
|
|
|
|
|
bool "Place TWAI ISR function into IRAM"
|
|
|
|
|
default n
|
2022-03-24 09:33:36 -04:00
|
|
|
select PERIPH_CTRL_FUNC_IN_IRAM if TWAI_ERRATA_FIX_RX_FRAME_INVALID || TWAI_ERRATA_FIX_RX_FIFO_CORRUPT
|
2020-08-04 00:52:10 -04:00
|
|
|
help
|
|
|
|
|
Place the TWAI ISR in to IRAM. This will allow the ISR to avoid
|
|
|
|
|
cache misses, and also be able to run whilst the cache is disabled
|
|
|
|
|
(such as when writing to SPI Flash).
|
|
|
|
|
Note that if this option is enabled:
|
|
|
|
|
- Users should also set the ESP_INTR_FLAG_IRAM in the driver
|
|
|
|
|
configuration structure when installing the driver (see docs for
|
|
|
|
|
specifics).
|
|
|
|
|
- Alert logging (i.e., setting of the TWAI_ALERT_AND_LOG flag)
|
|
|
|
|
will have no effect.
|
|
|
|
|
|
2021-03-24 22:24:37 -04:00
|
|
|
config TWAI_ERRATA_FIX_BUS_OFF_REC
|
|
|
|
|
bool "Add SW workaround for REC change during bus-off"
|
|
|
|
|
depends on IDF_TARGET_ESP32
|
2022-02-18 12:27:59 -05:00
|
|
|
default y
|
2021-03-24 22:24:37 -04:00
|
|
|
help
|
|
|
|
|
When the bus-off condition is reached, the REC should be reset to 0 and frozen (via LOM) by the
|
|
|
|
|
driver's ISR. However on the ESP32, there is an edge case where the REC will increase before the
|
|
|
|
|
driver's ISR can respond in time (e.g., due to the rapid occurrence of bus errors), thus causing the
|
|
|
|
|
REC to be non-zero after bus-off. A non-zero REC can prevent bus-off recovery as the bus-off recovery
|
|
|
|
|
condition is that both TEC and REC become 0. Enabling this option will add a workaround in the driver
|
|
|
|
|
to forcibly reset REC to zero on reaching bus-off.
|
|
|
|
|
|
|
|
|
|
config TWAI_ERRATA_FIX_TX_INTR_LOST
|
|
|
|
|
bool "Add SW workaround for TX interrupt lost errata"
|
|
|
|
|
depends on IDF_TARGET_ESP32
|
2022-02-18 12:27:59 -05:00
|
|
|
default y
|
2021-03-24 22:24:37 -04:00
|
|
|
help
|
|
|
|
|
On the ESP32, when a transmit interrupt occurs, and interrupt register is read on the same APB clock
|
|
|
|
|
cycle, the transmit interrupt could be lost. Enabling this option will add a workaround that checks the
|
|
|
|
|
transmit buffer status bit to recover any lost transmit interrupt.
|
|
|
|
|
|
|
|
|
|
config TWAI_ERRATA_FIX_RX_FRAME_INVALID
|
|
|
|
|
bool "Add SW workaround for invalid RX frame errata"
|
|
|
|
|
depends on IDF_TARGET_ESP32
|
2022-02-18 12:27:59 -05:00
|
|
|
default y
|
2021-03-24 22:24:37 -04:00
|
|
|
help
|
|
|
|
|
On the ESP32, when receiving a data or remote frame, if a bus error occurs in the data or CRC field,
|
|
|
|
|
the data of the next received frame could be invalid. Enabling this option will add a workaround that
|
|
|
|
|
will reset the peripheral on detection of this errata condition. Note that if a frame is transmitted on
|
|
|
|
|
the bus whilst the reset is ongoing, the message will not be receive by the peripheral sent on the bus
|
|
|
|
|
during the reset, the message will be lost.
|
|
|
|
|
|
|
|
|
|
config TWAI_ERRATA_FIX_RX_FIFO_CORRUPT
|
|
|
|
|
bool "Add SW workaround for RX FIFO corruption errata"
|
|
|
|
|
depends on IDF_TARGET_ESP32
|
2022-02-18 12:27:59 -05:00
|
|
|
default y
|
2021-03-24 22:24:37 -04:00
|
|
|
help
|
|
|
|
|
On the ESP32, when the RX FIFO overruns and the RX message counter maxes out at 64 messages, the entire
|
|
|
|
|
RX FIFO is no longer recoverable. Enabling this option will add a workaround that resets the peripheral
|
|
|
|
|
on detection of this errata condition. Note that if a frame is being sent on the bus during the reset
|
|
|
|
|
bus during the reset, the message will be lost.
|
|
|
|
|
|
2020-08-04 00:52:10 -04:00
|
|
|
endmenu # TWAI Configuration
|
|
|
|
|
|
2022-03-04 04:59:07 -05:00
|
|
|
menu "Temperature sensor Configuration"
|
2022-03-07 22:53:22 -05:00
|
|
|
depends on SOC_TEMP_SENSOR_SUPPORTED
|
2022-03-04 04:59:07 -05:00
|
|
|
|
|
|
|
|
config TEMP_SENSOR_SUPPRESS_DEPRECATE_WARN
|
|
|
|
|
bool "Suppress legacy driver deprecated warning"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to suppress the deprecation warnings when using legacy temperature sensor driver
|
|
|
|
|
(driver/temp_sensor.h). If you want to continue using the legacy driver,
|
|
|
|
|
and don't want to see related deprecation warnings, you can enable this option.
|
|
|
|
|
|
|
|
|
|
config TEMP_SENSOR_ENABLE_DEBUG_LOG
|
|
|
|
|
bool "Enable debug log"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to enable the debug log message for temperature sensor driver.
|
|
|
|
|
Note that, this option only controls the temperature sensor driver log, won't affect other drivers.
|
|
|
|
|
|
|
|
|
|
endmenu # TEMP_SENSOR Configuration
|
|
|
|
|
|
2019-08-26 05:14:15 -04:00
|
|
|
menu "UART configuration"
|
|
|
|
|
|
|
|
|
|
config UART_ISR_IN_IRAM
|
|
|
|
|
bool "Place UART ISR function into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If this option is not selected, UART interrupt will be disabled for a long time and
|
|
|
|
|
may cause data lost when doing spi flash operation.
|
|
|
|
|
|
|
|
|
|
endmenu # UART Configuration
|
|
|
|
|
|
2020-11-12 07:39:55 -05:00
|
|
|
menu "GPIO Configuration"
|
|
|
|
|
config GPIO_ESP32_SUPPORT_SWITCH_SLP_PULL
|
|
|
|
|
bool "Support light sleep GPIO pullup/pulldown configuration for ESP32"
|
|
|
|
|
depends on IDF_TARGET_ESP32
|
|
|
|
|
help
|
|
|
|
|
This option is intended to fix the bug that ESP32 is not able to switch to configured
|
|
|
|
|
pullup/pulldown mode in sleep.
|
|
|
|
|
If this option is selected, chip will automatically emulate the behaviour of switching,
|
|
|
|
|
and about 450B of source codes would be placed into IRAM.
|
2022-03-09 01:37:41 -05:00
|
|
|
|
|
|
|
|
config GPIO_CTRL_FUNC_IN_IRAM
|
|
|
|
|
bool "Place GPIO control functions into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Place GPIO control functions (like intr_disable/set_level) into IRAM,
|
|
|
|
|
so that these functions can be IRAM-safe and able to be called in the other IRAM interrupt context.
|
2020-11-12 07:39:55 -05:00
|
|
|
endmenu # GPIO Configuration
|
|
|
|
|
|
2021-11-07 21:26:52 -05:00
|
|
|
menu "GDMA Configuration"
|
2022-01-17 01:42:09 -05:00
|
|
|
depends on SOC_GDMA_SUPPORTED
|
2021-11-07 21:26:52 -05:00
|
|
|
config GDMA_CTRL_FUNC_IN_IRAM
|
|
|
|
|
bool "Place GDMA control functions into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Place GDMA control functions (like start/stop/append/reset) into IRAM,
|
|
|
|
|
so that these functions can be IRAM-safe and able to be called in the other IRAM interrupt context.
|
|
|
|
|
Enabling this option can improve driver performance as well.
|
|
|
|
|
|
|
|
|
|
config GDMA_ISR_IRAM_SAFE
|
|
|
|
|
bool "GDMA ISR IRAM-Safe"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This will ensure the GDMA interrupt handler is IRAM-Safe, allow to avoid flash
|
|
|
|
|
cache misses, and also be able to run whilst the cache is disabled.
|
|
|
|
|
(e.g. SPI Flash write).
|
|
|
|
|
endmenu # GDMA Configuration
|
|
|
|
|
|
2022-01-02 03:14:17 -05:00
|
|
|
menu "GPTimer Configuration"
|
|
|
|
|
config GPTIMER_CTRL_FUNC_IN_IRAM
|
|
|
|
|
bool "Place GPTimer control functions into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Place GPTimer control functions (like start/stop) into IRAM,
|
|
|
|
|
so that these functions can be IRAM-safe and able to be called in the other IRAM interrupt context.
|
|
|
|
|
Enabling this option can improve driver performance as well.
|
|
|
|
|
|
|
|
|
|
config GPTIMER_ISR_IRAM_SAFE
|
|
|
|
|
bool "GPTimer ISR IRAM-Safe"
|
|
|
|
|
default n
|
|
|
|
|
help
|
2022-01-17 01:42:09 -05:00
|
|
|
Ensure the GPTimer interrupt is IRAM-Safe by allowing the interrupt handler to be
|
|
|
|
|
executable when the cache is disabled (e.g. SPI Flash write).
|
2022-01-02 03:14:17 -05:00
|
|
|
|
|
|
|
|
config GPTIMER_SUPPRESS_DEPRECATE_WARN
|
2022-01-17 01:42:09 -05:00
|
|
|
bool "Suppress legacy driver deprecated warning"
|
2022-01-02 03:14:17 -05:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to suppress the deprecation warnings when using legacy timer group driver (driver/timer.h).
|
|
|
|
|
If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
|
|
|
|
|
you can enable this option.
|
2022-01-17 01:42:09 -05:00
|
|
|
|
|
|
|
|
config GPTIMER_ENABLE_DEBUG_LOG
|
|
|
|
|
bool "Enable debug log"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to enable the debug log message for GPTimer driver.
|
|
|
|
|
Note that, this option only controls the GPTimer driver log, won't affect other drivers.
|
2022-01-02 03:14:17 -05:00
|
|
|
endmenu # GPTimer Configuration
|
|
|
|
|
|
2022-01-17 01:42:09 -05:00
|
|
|
menu "PCNT Configuration"
|
|
|
|
|
depends on SOC_PCNT_SUPPORTED
|
|
|
|
|
config PCNT_CTRL_FUNC_IN_IRAM
|
|
|
|
|
bool "Place PCNT control functions into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Place PCNT control functions (like start/stop) into IRAM,
|
|
|
|
|
so that these functions can be IRAM-safe and able to be called in the other IRAM interrupt context.
|
|
|
|
|
Enabling this option can improve driver performance as well.
|
|
|
|
|
|
|
|
|
|
config PCNT_ISR_IRAM_SAFE
|
|
|
|
|
bool "PCNT ISR IRAM-Safe"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Ensure the PCNT interrupt is IRAM-Safe by allowing the interrupt handler to be
|
|
|
|
|
executable when the cache is disabled (e.g. SPI Flash write).
|
|
|
|
|
|
|
|
|
|
config PCNT_SUPPRESS_DEPRECATE_WARN
|
|
|
|
|
bool "Suppress legacy driver deprecated warning"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to suppress the deprecation warnings when using legacy PCNT driver (driver/pcnt.h).
|
|
|
|
|
If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
|
|
|
|
|
you can enable this option.
|
|
|
|
|
|
|
|
|
|
config PCNT_ENABLE_DEBUG_LOG
|
|
|
|
|
bool "Enable debug log"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to enable the debug log message for PCNT driver.
|
|
|
|
|
Note that, this option only controls the PCNT driver log, won't affect other drivers.
|
|
|
|
|
endmenu # PCNT Configuration
|
|
|
|
|
|
2018-06-11 07:54:18 -04:00
|
|
|
endmenu # Driver configurations
|
