mirror of
https://github.com/espressif/esp-idf.git
synced 2024-10-05 20:47:46 -04:00
7c8208d903
This commit adds the feature where the CAN ISR will continue to run even if the cache is disabled. Whilst cache is disabled, any received messages will go into the RX queue, and any pending TX messages in the TX queue will be transmitted. This feature should be enabled using the CONFIG_CAN_ISR_IN_IRAM option.
98 lines
4.3 KiB
Plaintext
98 lines
4.3 KiB
Plaintext
menu "Driver configurations"
|
|
|
|
menu "ADC configuration"
|
|
|
|
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.
|
|
|
|
config ADC_DISABLE_DAC
|
|
bool "Disable DAC when ADC2 is used on GPIO 25 and 26"
|
|
default y
|
|
help
|
|
If this is set, the ADC2 driver will disable the output of the DAC corresponding to the specified
|
|
channel. This is the default value.
|
|
|
|
For testing, disable this option so that we can measure the output of DAC by internal ADC.
|
|
|
|
endmenu # ADC Configuration
|
|
|
|
menu "SPI configuration"
|
|
|
|
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.
|
|
|
|
During unit test, this is enabled to measure the ideal case of api.
|
|
|
|
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.
|
|
|
|
Also you can forbid the ISR being disabled during flash writing
|
|
access, by add ESP_INTR_FLAG_IRAM when initializing the driver.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
Also you can forbid the ISR being disabled during flash writing
|
|
access, by add ESP_INTR_FLAG_IRAM when initializing the driver.
|
|
|
|
endmenu # SPI Configuration
|
|
|
|
menu "CAN Configuration"
|
|
|
|
config CAN_ISR_IN_IRAM
|
|
bool "Place CAN ISR function into IRAM"
|
|
default n
|
|
select SUPPORT_STATIC_ALLOCATION
|
|
# We need to enable FREERTOS_SUPPORT_STATIC_ALLOCATION because the
|
|
# CAN driver requires the use of FreeRTOS Queues and Semaphores from
|
|
# the driver ISR. These Queues and Semaphores need to be placed in
|
|
# DRAM thus FreeRTOS static allocation API is required.
|
|
help
|
|
Place the CAN 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 CAN_ALERT_AND_LOG flag)
|
|
will have no effect.
|
|
|
|
endmenu # CAN Configuration
|
|
|
|
endmenu # Driver configurations
|