Kconfig 2.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263
  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_USE_RTC_TIMER_REF
  22. bool "Use RTC timer to prevent time drift (EXPERIMENTAL)"
  23. depends on (PM_ENABLE && ESP_TIMER_IMPL_FRC2 && ESP_TIME_FUNCS_USE_RTC_TIMER)
  24. default n
  25. help
  26. When APB clock frequency changes, high-resolution timer (esp_timer)
  27. scale and base value need to be adjusted. Each adjustment may cause
  28. small error, and over time such small errors may cause time drift.
  29. If this option is enabled, RTC timer will be used as a reference to
  30. compensate for the drift.
  31. It is recommended that this option is only used if 32k XTAL is selected
  32. as RTC clock source.
  33. config PM_PROFILING
  34. bool "Enable profiling counters for PM locks"
  35. depends on PM_ENABLE
  36. default n
  37. help
  38. If enabled, esp_pm_* functions will keep track of the amount of time
  39. each of the power management locks has been held, and esp_pm_dump_locks
  40. function will print this information.
  41. This feature can be used to analyze which locks are preventing the chip
  42. from going into a lower power state, and see what time the chip spends
  43. in each power saving mode. This feature does incur some run-time
  44. overhead, so should typically be disabled in production builds.
  45. config PM_TRACE
  46. bool "Enable debug tracing of PM using GPIOs"
  47. depends on PM_ENABLE
  48. default n
  49. help
  50. If enabled, some GPIOs will be used to signal events such as RTOS ticks,
  51. frequency switching, entry/exit from idle state. Refer to pm_trace.c
  52. file for the list of GPIOs.
  53. This feature is intended to be used when analyzing/debugging behavior
  54. of power management implementation, and should be kept disabled in
  55. applications.
  56. endmenu # "Power Management"