Kconfig 26 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539
  1. menu "Driver Configurations"
  2. menu "Legacy ADC Configuration"
  3. config ADC_DISABLE_DAC
  4. depends on SOC_DAC_SUPPORTED
  5. bool "Disable DAC when ADC2 is used on GPIO 25 and 26"
  6. default y
  7. help
  8. If this is set, the ADC2 driver will disable the output of the DAC corresponding to the specified
  9. channel. This is the default value.
  10. For testing, disable this option so that we can measure the output of DAC by internal ADC.
  11. config ADC_SUPPRESS_DEPRECATE_WARN
  12. bool "Suppress legacy driver deprecated warning"
  13. default n
  14. help
  15. Wether to suppress the deprecation warnings when using legacy adc driver (driver/adc.h).
  16. If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
  17. you can enable this option.
  18. menu "Legacy ADC Calibration Configuration"
  19. config ADC_CAL_EFUSE_TP_ENABLE
  20. depends on IDF_TARGET_ESP32
  21. bool "Use Two Point Values"
  22. default "y"
  23. help
  24. Some ESP32s have Two Point calibration values burned into eFuse BLOCK3.
  25. This option will allow the ADC calibration component to characterize the
  26. ADC-Voltage curve using Two Point values if they are available.
  27. config ADC_CAL_EFUSE_VREF_ENABLE
  28. depends on IDF_TARGET_ESP32
  29. bool "Use eFuse Vref"
  30. default "y"
  31. help
  32. Some ESP32s have Vref burned into eFuse BLOCK0. This option will allow
  33. the ADC calibration component to characterize the ADC-Voltage curve using
  34. eFuse Vref if it is available.
  35. config ADC_CAL_LUT_ENABLE
  36. depends on IDF_TARGET_ESP32
  37. bool "Use Lookup Tables"
  38. default "y"
  39. help
  40. This option will allow the ADC calibration component to use Lookup Tables
  41. to correct for non-linear behavior in 11db attenuation. Other attenuations
  42. do not exhibit non-linear behavior hence will not be affected by this option.
  43. config ADC_CALI_SUPPRESS_DEPRECATE_WARN
  44. bool "Suppress legacy driver deprecated warning"
  45. default n
  46. help
  47. Wether to suppress the deprecation warnings when using legacy adc calibration
  48. driver (esp_adc_cal.h).
  49. If you want to continue using the legacy driver, and don't want to see related
  50. deprecation warnings, you can enable this option.
  51. endmenu
  52. endmenu # ADC Configuration
  53. menu "SPI Configuration"
  54. config SPI_MASTER_IN_IRAM
  55. bool "Place transmitting functions of SPI master into IRAM"
  56. default n
  57. depends on !FREERTOS_PLACE_FUNCTIONS_INTO_FLASH
  58. select SPI_MASTER_ISR_IN_IRAM
  59. help
  60. Normally only the ISR of SPI master is placed in the IRAM, so that it
  61. can work without the flash when interrupt is triggered.
  62. For other functions, there's some possibility that the flash cache
  63. miss when running inside and out of SPI functions, which may increase
  64. the interval of SPI transactions.
  65. Enable this to put ``queue_trans``, ``get_trans_result`` and
  66. ``transmit`` functions into the IRAM to avoid possible cache miss.
  67. This configuration won't be available if `CONFIG_FREERTOS_PLACE_FUNCTIONS_INTO_FLASH` is enabled.
  68. During unit test, this is enabled to measure the ideal case of api.
  69. config SPI_MASTER_ISR_IN_IRAM
  70. bool "Place SPI master ISR function into IRAM"
  71. default y
  72. depends on !HEAP_PLACE_FUNCTION_INTO_FLASH
  73. select PERIPH_CTRL_FUNC_IN_IRAM
  74. help
  75. Place the SPI master ISR in to IRAM to avoid possible cache miss.
  76. Enabling this configuration is possible only when HEAP_PLACE_FUNCTION_INTO_FLASH
  77. is disabled since the spi master uses can allocate transactions buffers into DMA
  78. memory section using the heap component API that ipso facto has to be placed in IRAM.
  79. Also you can forbid the ISR being disabled during flash writing
  80. access, by add ESP_INTR_FLAG_IRAM when initializing the driver.
  81. config SPI_SLAVE_IN_IRAM
  82. bool "Place transmitting functions of SPI slave into IRAM"
  83. default n
  84. select SPI_SLAVE_ISR_IN_IRAM
  85. help
  86. Normally only the ISR of SPI slave is placed in the IRAM, so that it
  87. can work without the flash when interrupt is triggered.
  88. For other functions, there's some possibility that the flash cache
  89. miss when running inside and out of SPI functions, which may increase
  90. the interval of SPI transactions.
  91. Enable this to put ``queue_trans``, ``get_trans_result`` and
  92. ``transmit`` functions into the IRAM to avoid possible cache miss.
  93. config SPI_SLAVE_ISR_IN_IRAM
  94. bool "Place SPI slave ISR function into IRAM"
  95. default y
  96. select PERIPH_CTRL_FUNC_IN_IRAM
  97. help
  98. Place the SPI slave ISR in to IRAM to avoid possible cache miss.
  99. Also you can forbid the ISR being disabled during flash writing
  100. access, by add ESP_INTR_FLAG_IRAM when initializing the driver.
  101. endmenu # SPI Configuration
  102. menu "TWAI Configuration"
  103. depends on SOC_TWAI_SUPPORTED
  104. config TWAI_ISR_IN_IRAM
  105. bool "Place TWAI ISR function into IRAM"
  106. default n
  107. select PERIPH_CTRL_FUNC_IN_IRAM if TWAI_ERRATA_FIX_RX_FRAME_INVALID || TWAI_ERRATA_FIX_RX_FIFO_CORRUPT
  108. help
  109. Place the TWAI ISR in to IRAM. This will allow the ISR to avoid
  110. cache misses, and also be able to run whilst the cache is disabled
  111. (such as when writing to SPI Flash).
  112. Note that if this option is enabled:
  113. - Users should also set the ESP_INTR_FLAG_IRAM in the driver
  114. configuration structure when installing the driver (see docs for
  115. specifics).
  116. - Alert logging (i.e., setting of the TWAI_ALERT_AND_LOG flag)
  117. will have no effect.
  118. config TWAI_ERRATA_FIX_BUS_OFF_REC
  119. bool "Add SW workaround for REC change during bus-off"
  120. depends on IDF_TARGET_ESP32
  121. default y
  122. help
  123. When the bus-off condition is reached, the REC should be reset to 0 and frozen (via LOM) by the
  124. driver's ISR. However on the ESP32, there is an edge case where the REC will increase before the
  125. driver's ISR can respond in time (e.g., due to the rapid occurrence of bus errors), thus causing the
  126. REC to be non-zero after bus-off. A non-zero REC can prevent bus-off recovery as the bus-off recovery
  127. condition is that both TEC and REC become 0. Enabling this option will add a workaround in the driver
  128. to forcibly reset REC to zero on reaching bus-off.
  129. config TWAI_ERRATA_FIX_TX_INTR_LOST
  130. bool "Add SW workaround for TX interrupt lost errata"
  131. depends on IDF_TARGET_ESP32
  132. default y
  133. help
  134. On the ESP32, when a transmit interrupt occurs, and interrupt register is read on the same APB clock
  135. cycle, the transmit interrupt could be lost. Enabling this option will add a workaround that checks the
  136. transmit buffer status bit to recover any lost transmit interrupt.
  137. config TWAI_ERRATA_FIX_RX_FRAME_INVALID
  138. bool "Add SW workaround for invalid RX frame errata"
  139. depends on IDF_TARGET_ESP32
  140. default y
  141. help
  142. On the ESP32, when receiving a data or remote frame, if a bus error occurs in the data or CRC field,
  143. the data of the next received frame could be invalid. Enabling this option will add a workaround that
  144. will reset the peripheral on detection of this errata condition. Note that if a frame is transmitted on
  145. the bus whilst the reset is ongoing, the message will not be receive by the peripheral sent on the bus
  146. during the reset, the message will be lost.
  147. config TWAI_ERRATA_FIX_RX_FIFO_CORRUPT
  148. bool "Add SW workaround for RX FIFO corruption errata"
  149. depends on IDF_TARGET_ESP32
  150. default y
  151. help
  152. On the ESP32, when the RX FIFO overruns and the RX message counter maxes out at 64 messages, the entire
  153. RX FIFO is no longer recoverable. Enabling this option will add a workaround that resets the peripheral
  154. on detection of this errata condition. Note that if a frame is being sent on the bus during the reset
  155. bus during the reset, the message will be lost.
  156. config TWAI_ERRATA_FIX_LISTEN_ONLY_DOM
  157. bool "Add SW workaround for listen only transmits dominant bit errata"
  158. depends on IDF_TARGET_ESP32 || IDF_TARGET_ESP32S2 || IDF_TARGET_ESP32S3 || IDF_TARGET_ESP32C3
  159. default y
  160. help
  161. When in the listen only mode, the TWAI controller must not influence the TWAI bus (i.e., must not send
  162. any dominant bits). However, while in listen only mode on the ESP32/ESP32-S2/ESP32-S3/ESP32-C3, the
  163. TWAI controller will still transmit dominant bits when it detects an error (i.e., as part of an active
  164. error frame). Enabling this option will add a workaround that forces the TWAI controller into an error
  165. passive state on initialization, thus preventing any dominant bits from being sent.
  166. endmenu # TWAI Configuration
  167. menu "Temperature sensor Configuration"
  168. depends on SOC_TEMP_SENSOR_SUPPORTED
  169. config TEMP_SENSOR_SUPPRESS_DEPRECATE_WARN
  170. bool "Suppress legacy driver deprecated warning"
  171. default n
  172. help
  173. Wether to suppress the deprecation warnings when using legacy temperature sensor driver
  174. (driver/temp_sensor.h). If you want to continue using the legacy driver,
  175. and don't want to see related deprecation warnings, you can enable this option.
  176. config TEMP_SENSOR_ENABLE_DEBUG_LOG
  177. bool "Enable debug log"
  178. default n
  179. help
  180. Wether to enable the debug log message for temperature sensor driver.
  181. Note that, this option only controls the temperature sensor driver log, won't affect other drivers.
  182. config TEMP_SENSOR_ISR_IRAM_SAFE
  183. depends on SOC_TEMPERATURE_SENSOR_INTR_SUPPORT
  184. bool "Temperature sensor ISR IRAM-Safe"
  185. default n
  186. help
  187. Ensure the Temperature Sensor interrupt is IRAM-Safe by allowing the interrupt handler to be
  188. executable when the cache is disabled (e.g. SPI Flash write).
  189. endmenu # TEMP_SENSOR Configuration
  190. menu "UART Configuration"
  191. config UART_ISR_IN_IRAM
  192. bool "Place UART ISR function into IRAM"
  193. depends on !RINGBUF_PLACE_ISR_FUNCTIONS_INTO_FLASH
  194. default n
  195. help
  196. If this option is not selected, UART interrupt will be disabled for a long time and
  197. may cause data lost when doing spi flash operation.
  198. endmenu # UART Configuration
  199. menu "GPIO Configuration"
  200. config GPIO_ESP32_SUPPORT_SWITCH_SLP_PULL
  201. bool "Support light sleep GPIO pullup/pulldown configuration for ESP32"
  202. depends on IDF_TARGET_ESP32
  203. help
  204. This option is intended to fix the bug that ESP32 is not able to switch to configured
  205. pullup/pulldown mode in sleep.
  206. If this option is selected, chip will automatically emulate the behaviour of switching,
  207. and about 450B of source codes would be placed into IRAM.
  208. config GPIO_CTRL_FUNC_IN_IRAM
  209. bool "Place GPIO control functions into IRAM"
  210. default n
  211. help
  212. Place GPIO control functions (like intr_disable/set_level) into IRAM,
  213. so that these functions can be IRAM-safe and able to be called in the other IRAM interrupt context.
  214. endmenu # GPIO Configuration
  215. menu "Sigma Delta Modulator Configuration"
  216. depends on SOC_SDM_SUPPORTED
  217. config SDM_CTRL_FUNC_IN_IRAM
  218. bool "Place SDM control functions into IRAM"
  219. default n
  220. help
  221. Place SDM control functions (like set_duty) into IRAM,
  222. so that these functions can be IRAM-safe and able to be called in the other IRAM interrupt context.
  223. Enabling this option can improve driver performance as well.
  224. config SDM_SUPPRESS_DEPRECATE_WARN
  225. bool "Suppress legacy driver deprecated warning"
  226. default n
  227. help
  228. Wether to suppress the deprecation warnings when using legacy sigma delta driver.
  229. If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
  230. you can enable this option.
  231. config SDM_ENABLE_DEBUG_LOG
  232. bool "Enable debug log"
  233. default n
  234. help
  235. Wether to enable the debug log message for SDM driver.
  236. Note that, this option only controls the SDM driver log, won't affect other drivers.
  237. endmenu # Sigma Delta Modulator Configuration
  238. menu "Analog Comparator Configuration"
  239. depends on SOC_ANA_CMPR_SUPPORTED
  240. config ANA_CMPR_ISR_IRAM_SAFE
  241. bool "Analog comparator ISR IRAM-Safe"
  242. default n
  243. help
  244. Ensure the Analog Comparator interrupt is IRAM-Safe by allowing the interrupt handler to be
  245. executable when the cache is disabled (e.g. SPI Flash write).
  246. config ANA_CMPR_CTRL_FUNC_IN_IRAM
  247. bool "Place Analog Comparator control functions into IRAM"
  248. default n
  249. help
  250. Place Analog Comparator control functions (like ana_cmpr_set_internal_reference) into IRAM,
  251. so that these functions can be IRAM-safe and able to be called in an IRAM interrupt context.
  252. Enabling this option can improve driver performance as well.
  253. config ANA_CMPR_ENABLE_DEBUG_LOG
  254. bool "Enable debug log"
  255. default n
  256. help
  257. Wether to enable the debug log message for Analog Comparator driver.
  258. Note that, this option only controls the Analog Comparator driver log, won't affect other drivers.
  259. endmenu # Analog Comparator Configuration
  260. menu "GPTimer Configuration"
  261. config GPTIMER_CTRL_FUNC_IN_IRAM
  262. bool "Place GPTimer control functions into IRAM"
  263. default n
  264. help
  265. Place GPTimer control functions (like start/stop) into IRAM,
  266. so that these functions can be IRAM-safe and able to be called in the other IRAM interrupt context.
  267. Enabling this option can improve driver performance as well.
  268. config GPTIMER_ISR_IRAM_SAFE
  269. bool "GPTimer ISR IRAM-Safe"
  270. default n
  271. help
  272. Ensure the GPTimer interrupt is IRAM-Safe by allowing the interrupt handler to be
  273. executable when the cache is disabled (e.g. SPI Flash write).
  274. config GPTIMER_SUPPRESS_DEPRECATE_WARN
  275. bool "Suppress legacy driver deprecated warning"
  276. default n
  277. help
  278. Wether to suppress the deprecation warnings when using legacy timer group driver (driver/timer.h).
  279. If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
  280. you can enable this option.
  281. config GPTIMER_ENABLE_DEBUG_LOG
  282. bool "Enable debug log"
  283. default n
  284. help
  285. Wether to enable the debug log message for GPTimer driver.
  286. Note that, this option only controls the GPTimer driver log, won't affect other drivers.
  287. endmenu # GPTimer Configuration
  288. menu "PCNT Configuration"
  289. depends on SOC_PCNT_SUPPORTED
  290. config PCNT_CTRL_FUNC_IN_IRAM
  291. bool "Place PCNT control functions into IRAM"
  292. default n
  293. help
  294. Place PCNT control functions (like start/stop) into IRAM,
  295. so that these functions can be IRAM-safe and able to be called in the other IRAM interrupt context.
  296. Enabling this option can improve driver performance as well.
  297. config PCNT_ISR_IRAM_SAFE
  298. bool "PCNT ISR IRAM-Safe"
  299. default n
  300. help
  301. Ensure the PCNT interrupt is IRAM-Safe by allowing the interrupt handler to be
  302. executable when the cache is disabled (e.g. SPI Flash write).
  303. config PCNT_SUPPRESS_DEPRECATE_WARN
  304. bool "Suppress legacy driver deprecated warning"
  305. default n
  306. help
  307. Wether to suppress the deprecation warnings when using legacy PCNT driver (driver/pcnt.h).
  308. If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
  309. you can enable this option.
  310. config PCNT_ENABLE_DEBUG_LOG
  311. bool "Enable debug log"
  312. default n
  313. help
  314. Wether to enable the debug log message for PCNT driver.
  315. Note that, this option only controls the PCNT driver log, won't affect other drivers.
  316. endmenu # PCNT Configuration
  317. menu "RMT Configuration"
  318. depends on SOC_RMT_SUPPORTED
  319. config RMT_ISR_IRAM_SAFE
  320. bool "RMT ISR IRAM-Safe"
  321. default n
  322. select GDMA_ISR_IRAM_SAFE if SOC_RMT_SUPPORT_DMA # RMT basic functionality relies on GDMA callback
  323. select GDMA_CTRL_FUNC_IN_IRAM if SOC_RMT_SUPPORT_DMA # RMT needs to restart the GDMA in the interrupt
  324. help
  325. Ensure the RMT interrupt is IRAM-Safe by allowing the interrupt handler to be
  326. executable when the cache is disabled (e.g. SPI Flash write).
  327. config RMT_SUPPRESS_DEPRECATE_WARN
  328. bool "Suppress legacy driver deprecated warning"
  329. default n
  330. help
  331. Wether to suppress the deprecation warnings when using legacy rmt driver (driver/rmt.h).
  332. If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
  333. you can enable this option.
  334. config RMT_ENABLE_DEBUG_LOG
  335. bool "Enable debug log"
  336. default n
  337. help
  338. Wether to enable the debug log message for RMT driver.
  339. Note that, this option only controls the RMT driver log, won't affect other drivers.
  340. endmenu # RMT Configuration
  341. menu "MCPWM Configuration"
  342. depends on SOC_MCPWM_SUPPORTED
  343. config MCPWM_ISR_IRAM_SAFE
  344. bool "Place MCPWM ISR function into IRAM"
  345. default n
  346. help
  347. This will ensure the MCPWM interrupt handle is IRAM-Safe, allow to avoid flash
  348. cache misses, and also be able to run whilst the cache is disabled.
  349. (e.g. SPI Flash write)
  350. config MCPWM_CTRL_FUNC_IN_IRAM
  351. bool "Place MCPWM control functions into IRAM"
  352. default n
  353. help
  354. Place MCPWM control functions (like set_compare_value) into IRAM,
  355. so that these functions can be IRAM-safe and able to be called in the other IRAM interrupt context.
  356. Enabling this option can improve driver performance as well.
  357. config MCPWM_SUPPRESS_DEPRECATE_WARN
  358. bool "Suppress leagcy driver deprecated warning"
  359. default n
  360. help
  361. Wether to suppress the deprecation warnings when using legacy MCPWM driver (driver/mcpwm.h).
  362. If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
  363. you can enable this option.
  364. config MCPWM_ENABLE_DEBUG_LOG
  365. bool "Enable debug log"
  366. default n
  367. help
  368. Wether to enable the debug log message for MCPWM driver.
  369. Note that, this option only controls the MCPWM driver log, won't affect other drivers.
  370. endmenu # MCPWM Configuration
  371. menu "I2S Configuration"
  372. depends on SOC_I2S_SUPPORTED
  373. config I2S_ISR_IRAM_SAFE
  374. bool "I2S ISR IRAM-Safe"
  375. default n
  376. help
  377. Ensure the I2S interrupt is IRAM-Safe by allowing the interrupt handler to be
  378. executable when the cache is disabled (e.g. SPI Flash write).
  379. config I2S_SUPPRESS_DEPRECATE_WARN
  380. bool "Suppress leagcy driver deprecated warning"
  381. default n
  382. help
  383. Enable this option will suppress the deprecation warnings of using APIs in legacy I2S driver.
  384. config I2S_ENABLE_DEBUG_LOG
  385. bool "Enable I2S debug log"
  386. default n
  387. help
  388. Wether to enable the debug log message for I2S driver.
  389. Note that, this option only controls the I2S driver log, will not affect other drivers.
  390. endmenu # I2S Configuration
  391. menu "DAC Configuration"
  392. depends on SOC_DAC_SUPPORTED
  393. config DAC_CTRL_FUNC_IN_IRAM
  394. bool "Place DAC control functions into IRAM"
  395. default n
  396. help
  397. Place DAC control functions (e.g. 'dac_oneshot_output_voltage') into IRAM,
  398. so that this function can be IRAM-safe and able to be called in the other IRAM interrupt context.
  399. Enabling this option can improve driver performance as well.
  400. config DAC_ISR_IRAM_SAFE
  401. bool "DAC ISR IRAM-Safe"
  402. default n
  403. help
  404. Ensure the DAC interrupt is IRAM-Safe by allowing the interrupt handler to be
  405. executable when the cache is disabled (e.g. SPI Flash write).
  406. config DAC_SUPPRESS_DEPRECATE_WARN
  407. bool "Suppress legacy driver deprecated warning"
  408. default n
  409. help
  410. Wether to suppress the deprecation warnings when using legacy DAC driver (driver/dac.h).
  411. If you want to continue using the legacy driver, and don't want to see related deprecation warnings,
  412. you can enable this option.
  413. config DAC_ENABLE_DEBUG_LOG
  414. bool "Enable debug log"
  415. default n
  416. help
  417. Wether to enable the debug log message for DAC driver.
  418. Note that, this option only controls the DAC driver log, won't affect other drivers.
  419. config DAC_DMA_AUTO_16BIT_ALIGN
  420. bool "Align the continuous data to 16 bit automatically"
  421. depends on SOC_DAC_DMA_16BIT_ALIGN
  422. default y
  423. help
  424. Whether to left shift the continuous data to align every bytes to 16 bits in the driver.
  425. On ESP32, although the DAC resolution is only 8 bits,
  426. the hardware requires 16 bits data in continuous mode.
  427. By enabling this option, the driver will left shift 8 bits for the input data automatically.
  428. Only disable this option when you decide to do this step by yourself.
  429. Note that the driver will allocate a new piece of memory to save the converted data.
  430. endmenu # DAC Configuration
  431. menu "USB Serial/JTAG Configuration"
  432. depends on SOC_USB_SERIAL_JTAG_SUPPORTED
  433. config USJ_NO_AUTO_LS_ON_CONNECTION
  434. bool "Don't enter the automatic light sleep when USB Serial/JTAG port is connected"
  435. depends on PM_ENABLE && ESP_CONSOLE_USB_SERIAL_JTAG_ENABLED && !SOC_USB_SERIAL_JTAG_SUPPORT_LIGHT_SLEEP
  436. default n
  437. help
  438. If enabled, the chip will constantly monitor the connection status of the USB Serial/JTAG port. As long
  439. as the USB Serial/JTAG is connected, a ESP_PM_NO_LIGHT_SLEEP power management lock will be acquired to
  440. prevent the system from entering light sleep.
  441. This option can be useful if serial monitoring is needed via USB Serial/JTAG while power management is
  442. enabled, as the USB Serial/JTAG cannot work under light sleep and after waking up from light sleep.
  443. Note. This option can only control the automatic Light-Sleep behavior. If esp_light_sleep_start() is
  444. called manually from the program, enabling this option will not prevent light sleep entry even if the
  445. USB Serial/JTAG is in use.
  446. endmenu # USB Serial/JTAG Configuration
  447. menu "Parallel IO Configuration"
  448. depends on SOC_PARLIO_SUPPORTED
  449. config PARLIO_ENABLE_DEBUG_LOG
  450. bool "Enable debug log"
  451. default n
  452. help
  453. Wether to enable the debug log message for parallel IO driver.
  454. Note that, this option only controls the parallel IO driver log, won't affect other drivers.
  455. config PARLIO_ISR_IRAM_SAFE
  456. bool "Parallel IO ISR IRAM-Safe"
  457. default n
  458. select GDMA_CTRL_FUNC_IN_IRAM # the driver needs to start the GDMA in the interrupt
  459. help
  460. Ensure the Parallel IO interrupt is IRAM-Safe by allowing the interrupt handler to be
  461. executable when the cache is disabled (e.g. SPI Flash write).
  462. endmenu # Parallel IO Configuration
  463. endmenu # Driver configurations