2022-05-28 05:27:02 -04:00
|
|
|
menu "Driver Configurations"
|
2018-03-07 02:04:43 -05:00
|
|
|
|
2022-07-15 00:52:44 -04:00
|
|
|
menu "Legacy ADC Configuration"
|
2018-03-07 02:04:43 -05:00
|
|
|
|
2019-04-29 08:22:57 -04:00
|
|
|
config ADC_DISABLE_DAC
|
2022-07-15 00:52:44 -04:00
|
|
|
depends on SOC_DAC_SUPPORTED
|
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
|
|
|
|
2022-07-15 00:52:44 -04:00
|
|
|
config ADC_SUPPRESS_DEPRECATE_WARN
|
|
|
|
|
bool "Suppress legacy driver deprecated warning"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to suppress the deprecation warnings when using legacy adc driver (driver/adc.h).
|
|
|
|
|
If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
|
|
|
|
|
you can enable this option.
|
|
|
|
|
|
|
|
|
|
menu "Legacy ADC Calibration Configuration"
|
|
|
|
|
|
|
|
|
|
config ADC_CAL_EFUSE_TP_ENABLE
|
|
|
|
|
depends on IDF_TARGET_ESP32
|
|
|
|
|
bool "Use Two Point Values"
|
|
|
|
|
default "y"
|
|
|
|
|
help
|
|
|
|
|
Some ESP32s have Two Point calibration values burned into eFuse BLOCK3.
|
|
|
|
|
This option will allow the ADC calibration component to characterize the
|
|
|
|
|
ADC-Voltage curve using Two Point values if they are available.
|
|
|
|
|
|
|
|
|
|
config ADC_CAL_EFUSE_VREF_ENABLE
|
|
|
|
|
depends on IDF_TARGET_ESP32
|
|
|
|
|
bool "Use eFuse Vref"
|
|
|
|
|
default "y"
|
|
|
|
|
help
|
|
|
|
|
Some ESP32s have Vref burned into eFuse BLOCK0. This option will allow
|
|
|
|
|
the ADC calibration component to characterize the ADC-Voltage curve using
|
|
|
|
|
eFuse Vref if it is available.
|
|
|
|
|
|
|
|
|
|
config ADC_CAL_LUT_ENABLE
|
|
|
|
|
depends on IDF_TARGET_ESP32
|
|
|
|
|
bool "Use Lookup Tables"
|
|
|
|
|
default "y"
|
|
|
|
|
help
|
|
|
|
|
This option will allow the ADC calibration component to use Lookup Tables
|
|
|
|
|
to correct for non-linear behavior in 11db attenuation. Other attenuations
|
|
|
|
|
do not exhibit non-linear behavior hence will not be affected by this option.
|
|
|
|
|
|
|
|
|
|
config ADC_CALI_SUPPRESS_DEPRECATE_WARN
|
|
|
|
|
bool "Suppress legacy driver deprecated warning"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to suppress the deprecation warnings when using legacy adc calibration
|
|
|
|
|
driver (esp_adc_cal.h).
|
|
|
|
|
If you want to continue using the legacy driver, and don't want to see related
|
|
|
|
|
deprecation warnings, you can enable this option.
|
|
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
2019-01-25 11:10:53 -05:00
|
|
|
endmenu # ADC Configuration
|
2018-03-07 02:04:43 -05:00
|
|
|
|
2022-05-28 05:27:02 -04: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
|
|
|
|
2022-05-28 05:27:02 -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.
|
|
|
|
|
|
twai: Add errata workaround for listen only mode
This commit adds a workaround for the TWAI listen only mode errata which is
present on the ESP32, ESP32-S2, ESP32-S3, and ESP32-C3. twai_get_status_info()
has also been updated to account for the fact that TEC/REC are frozen in
listen only mode.
Errata Description:
When the TWAI controller is put into listen only mode, it should not influence
the TWAI bus in any way (i.e., should never send a dominant bit). However,
on the targets listed above, the TWAI controller will send dominant bits in an
error frame (i.e., active error frame), even if the controller is set to listen
only mode.
Workaround:
We can force the TWAI controller into the error passive state on startup (by
setting the REC to >= 128). Since the TEC/REC are frozen in listen only mode,
the TWAI controller will remain error passive and only send recessive bits
(i.e., passive error frames), thus will not influence the TWAI bus.
Closes https://github.com/espressif/esp-idf/issues/9157
2023-02-24 06:26:22 -05:00
|
|
|
config TWAI_ERRATA_FIX_LISTEN_ONLY_DOM
|
|
|
|
|
bool "Add SW workaround for listen only transmits dominant bit errata"
|
|
|
|
|
depends on IDF_TARGET_ESP32 || IDF_TARGET_ESP32S2 || IDF_TARGET_ESP32S3 || IDF_TARGET_ESP32C3
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
When in the listen only mode, the TWAI controller must not influence the TWAI bus (i.e., must not send
|
|
|
|
|
any dominant bits). However, while in listen only mode on the ESP32/ESP32-S2/ESP32-S3/ESP32-C3, the
|
|
|
|
|
TWAI controller will still transmit dominant bits when it detects an error (i.e., as part of an active
|
|
|
|
|
error frame). Enabling this option will add a workaround that forces the TWAI controller into an error
|
|
|
|
|
passive state on initialization, thus preventing any dominant bits from being sent.
|
|
|
|
|
|
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
|
|
|
|
|
|
2022-05-28 05:27:02 -04:00
|
|
|
menu "UART Configuration"
|
2019-08-26 05:14:15 -04:00
|
|
|
|
|
|
|
|
config UART_ISR_IN_IRAM
|
|
|
|
|
bool "Place UART ISR function into IRAM"
|
2022-06-30 03:43:45 -04:00
|
|
|
depends on !RINGBUF_PLACE_ISR_FUNCTIONS_INTO_FLASH
|
2019-08-26 05:14:15 -04:00
|
|
|
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
|
|
|
|
|
|
2022-06-22 04:34:13 -04:00
|
|
|
menu "Sigma Delta Modulator Configuration"
|
|
|
|
|
depends on SOC_SDM_SUPPORTED
|
|
|
|
|
config SDM_CTRL_FUNC_IN_IRAM
|
|
|
|
|
bool "Place SDM control functions into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Place SDM control functions (like set_duty) 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 SDM_SUPPRESS_DEPRECATE_WARN
|
|
|
|
|
bool "Suppress legacy driver deprecated warning"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to suppress the deprecation warnings when using legacy sigma delta driver.
|
|
|
|
|
If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
|
|
|
|
|
you can enable this option.
|
|
|
|
|
|
|
|
|
|
config SDM_ENABLE_DEBUG_LOG
|
|
|
|
|
bool "Enable debug log"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to enable the debug log message for SDM driver.
|
|
|
|
|
Note that, this option only controls the SDM driver log, won't affect other drivers.
|
|
|
|
|
endmenu # Sigma Delta Modulator 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
|
|
|
|
|
|
2022-04-06 23:50:41 -04:00
|
|
|
menu "RMT Configuration"
|
|
|
|
|
depends on SOC_RMT_SUPPORTED
|
2022-04-06 23:59:46 -04:00
|
|
|
config RMT_ISR_IRAM_SAFE
|
|
|
|
|
bool "RMT ISR IRAM-Safe"
|
|
|
|
|
default n
|
|
|
|
|
select GDMA_ISR_IRAM_SAFE if SOC_RMT_SUPPORT_DMA # RMT basic functionality relies on GDMA callback
|
|
|
|
|
select GDMA_CTRL_FUNC_IN_IRAM if SOC_RMT_SUPPORT_DMA # RMT needs to restart the GDMA in the interrupt
|
|
|
|
|
help
|
|
|
|
|
Ensure the RMT interrupt is IRAM-Safe by allowing the interrupt handler to be
|
|
|
|
|
executable when the cache is disabled (e.g. SPI Flash write).
|
|
|
|
|
|
2022-04-06 23:50:41 -04:00
|
|
|
config RMT_SUPPRESS_DEPRECATE_WARN
|
|
|
|
|
bool "Suppress legacy driver deprecated warning"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to suppress the deprecation warnings when using legacy rmt driver (driver/rmt.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-04-06 23:59:46 -04:00
|
|
|
|
|
|
|
|
config RMT_ENABLE_DEBUG_LOG
|
|
|
|
|
bool "Enable debug log"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to enable the debug log message for RMT driver.
|
|
|
|
|
Note that, this option only controls the RMT driver log, won't affect other drivers.
|
2022-04-06 23:50:41 -04:00
|
|
|
endmenu # RMT Configuration
|
|
|
|
|
|
2022-05-28 05:27:02 -04:00
|
|
|
menu "MCPWM Configuration"
|
|
|
|
|
depends on SOC_MCPWM_SUPPORTED
|
|
|
|
|
config MCPWM_ISR_IRAM_SAFE
|
|
|
|
|
bool "Place MCPWM ISR function into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This will ensure the MCPWM interrupt handle 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)
|
|
|
|
|
|
2022-09-20 03:34:45 -04:00
|
|
|
config MCPWM_CTRL_FUNC_IN_IRAM
|
|
|
|
|
bool "Place MCPWM control functions into IRAM"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Place MCPWM control functions (like set_compare_value) 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.
|
|
|
|
|
|
2022-05-28 05:02:07 -04:00
|
|
|
config MCPWM_SUPPRESS_DEPRECATE_WARN
|
|
|
|
|
bool "Suppress leagcy driver deprecated warning"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to suppress the deprecation warnings when using legacy MCPWM driver (driver/mcpwm.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 MCPWM_ENABLE_DEBUG_LOG
|
|
|
|
|
bool "Enable debug log"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to enable the debug log message for MCPWM driver.
|
|
|
|
|
Note that, this option only controls the MCPWM driver log, won't affect other drivers.
|
2022-05-28 05:27:02 -04:00
|
|
|
endmenu # MCPWM Configuration
|
|
|
|
|
|
2021-08-18 07:45:51 -04:00
|
|
|
menu "I2S Configuration"
|
|
|
|
|
depends on SOC_I2S_SUPPORTED
|
|
|
|
|
config I2S_ISR_IRAM_SAFE
|
|
|
|
|
bool "I2S ISR IRAM-Safe"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Ensure the I2S interrupt is IRAM-Safe by allowing the interrupt handler to be
|
|
|
|
|
executable when the cache is disabled (e.g. SPI Flash write).
|
|
|
|
|
|
|
|
|
|
config I2S_SUPPRESS_DEPRECATE_WARN
|
|
|
|
|
bool "Suppress leagcy driver deprecated warning"
|
|
|
|
|
default n
|
|
|
|
|
help
|
2022-04-07 03:32:46 -04:00
|
|
|
Enable this option will suppress the deprecation warnings of using APIs in legacy I2S driver.
|
|
|
|
|
|
|
|
|
|
config I2S_ENABLE_DEBUG_LOG
|
|
|
|
|
bool "Enable I2S debug log"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Wether to enable the debug log message for I2S driver.
|
|
|
|
|
Note that, this option only controls the I2S driver log, will not affect other drivers.
|
2021-08-18 07:45:51 -04:00
|
|
|
endmenu # I2S Configuration
|
|
|
|
|
|
|
|
|
|
endmenu # Driver configurations
|
