Kconfig 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. menu "Power Management"
  2. config PM_ENABLE
  3. bool "Support for power management"
  4. default n
  5. help
  6. If enabled, application is compiled with support for power management.
  7. This option has run-time overhead (increased interrupt latency,
  8. longer time to enter idle state), and it also reduces accuracy of
  9. RTOS ticks and timers used for timekeeping.
  10. Enable this option if application uses power management APIs.
  11. config PM_DFS_INIT_AUTO
  12. bool "Enable dynamic frequency scaling (DFS) at startup"
  13. depends on PM_ENABLE
  14. default n
  15. help
  16. If enabled, startup code configures dynamic frequency scaling.
  17. Max CPU frequency is set to DEFAULT_CPU_FREQ_MHZ setting,
  18. min frequency is set to XTAL frequency.
  19. If disabled, DFS will not be active until the application
  20. configures it using esp_pm_configure function.
  21. config PM_PROFILING
  22. bool "Enable profiling counters for PM locks"
  23. depends on PM_ENABLE
  24. default n
  25. help
  26. If enabled, esp_pm_* functions will keep track of the amount of time
  27. each of the power management locks has been held, and esp_pm_dump_locks
  28. function will print this information.
  29. This feature can be used to analyze which locks are preventing the chip
  30. from going into a lower power state, and see what time the chip spends
  31. in each power saving mode. This feature does incur some run-time
  32. overhead, so should typically be disabled in production builds.
  33. config PM_TRACE
  34. bool "Enable debug tracing of PM using GPIOs"
  35. depends on PM_ENABLE
  36. default n
  37. help
  38. If enabled, some GPIOs will be used to signal events such as RTOS ticks,
  39. frequency switching, entry/exit from idle state. Refer to pm_trace.c
  40. file for the list of GPIOs.
  41. This feature is intended to be used when analyzing/debugging behavior
  42. of power management implementation, and should be kept disabled in
  43. applications.
  44. config PM_SLP_IRAM_OPT
  45. bool "Put lightsleep related codes in internal RAM"
  46. depends on FREERTOS_USE_TICKLESS_IDLE
  47. help
  48. If enabled, about 1.8KB of lightsleep related source code would be in IRAM and chip would sleep
  49. longer for 760us at most each time.
  50. This feature is intended to be used when lower power consumption is needed
  51. while there is enough place in IRAM to place source code.
  52. config PM_RTOS_IDLE_OPT
  53. bool "Put RTOS IDLE related codes in internal RAM"
  54. depends on FREERTOS_USE_TICKLESS_IDLE
  55. help
  56. If enabled, about 260B of RTOS_IDLE related source code would be in IRAM and chip would sleep
  57. longer for 40us at most each time.
  58. This feature is intended to be used when lower power consumption is needed
  59. while there is enough place in IRAM to place source code.
  60. config PM_SLP_DISABLE_GPIO
  61. bool "Disable all GPIO when chip at sleep"
  62. depends on FREERTOS_USE_TICKLESS_IDLE
  63. help
  64. This feature is intended to disable all GPIO pins at automantic sleep to get a lower power mode.
  65. If enabled, chips will disable all GPIO pins at automantic sleep to reduce about 200~300 uA current.
  66. If you want to specifically use some pins normally as chip wakes when chip sleeps,
  67. you can call 'gpio_sleep_sel_dis' to disable this feature on those pins.
  68. You can also keep this feature on and call 'gpio_sleep_set_direction' and 'gpio_sleep_set_pull_mode'
  69. to have a different GPIO configuration at sleep.
  70. Waring: If you want to enable this option on ESP32, you should enable `GPIO_ESP32_SUPPORT_SWITCH_SLP_PULL`
  71. at first, otherwise you will not be able to switch pullup/pulldown mode.
  72. config PM_SLP_DEFAULT_PARAMS_OPT
  73. bool
  74. default n
  75. config PM_POWER_DOWN_CPU_IN_LIGHT_SLEEP
  76. bool "Power down CPU in light sleep"
  77. depends on IDF_TARGET_ESP32C3 || IDF_TARGET_ESP32S3
  78. select PM_POWER_DOWN_TAGMEM_IN_LIGHT_SLEEP if ESP32S3_DATA_CACHE_16KB
  79. default y
  80. help
  81. If enabled, the CPU will be powered down in light sleep. On esp32c3 soc, enabling this
  82. option will consume 1.68 KB of internal RAM and will reduce sleep current consumption
  83. by about 100 uA. On esp32s3 soc, enabling this option will consume 8.58 KB of internal
  84. RAM and will reduce sleep current consumption by about 650 uA.
  85. config PM_POWER_DOWN_TAGMEM_IN_LIGHT_SLEEP
  86. bool "Power down I/D-cache tag memory in light sleep"
  87. depends on IDF_TARGET_ESP32S3 && PM_POWER_DOWN_CPU_IN_LIGHT_SLEEP
  88. default y
  89. help
  90. If enabled, the I/D-cache tag memory will be retained in light sleep. Depending on the the
  91. cache configuration, if this option is enabled, it will consume up to 9 KB of internal RAM.
  92. config PM_UPDATE_CCOMPARE_HLI_WORKAROUND
  93. bool
  94. default y if PM_ENABLE && BTDM_CTRL_HLI
  95. endmenu # "Power Management"