2020-07-21 05:15:19 -04:00
|
|
|
menu "Power Management"
|
|
|
|
|
config PM_ENABLE
|
|
|
|
|
bool "Support for power management"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If enabled, application is compiled with support for power management.
|
|
|
|
|
This option has run-time overhead (increased interrupt latency,
|
|
|
|
|
longer time to enter idle state), and it also reduces accuracy of
|
|
|
|
|
RTOS ticks and timers used for timekeeping.
|
|
|
|
|
Enable this option if application uses power management APIs.
|
|
|
|
|
|
|
|
|
|
config PM_DFS_INIT_AUTO
|
|
|
|
|
bool "Enable dynamic frequency scaling (DFS) at startup"
|
|
|
|
|
depends on PM_ENABLE
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If enabled, startup code configures dynamic frequency scaling.
|
|
|
|
|
Max CPU frequency is set to DEFAULT_CPU_FREQ_MHZ setting,
|
|
|
|
|
min frequency is set to XTAL frequency.
|
|
|
|
|
If disabled, DFS will not be active until the application
|
|
|
|
|
configures it using esp_pm_configure function.
|
|
|
|
|
|
2020-07-22 03:23:39 -04:00
|
|
|
|
2020-07-21 05:15:19 -04:00
|
|
|
config PM_USE_RTC_TIMER_REF
|
|
|
|
|
bool "Use RTC timer to prevent time drift (EXPERIMENTAL)"
|
2020-10-20 02:09:32 -04:00
|
|
|
depends on (PM_ENABLE && ESP_TIMER_IMPL_FRC2 && ESP_TIME_FUNCS_USE_RTC_TIMER)
|
2020-07-21 05:15:19 -04:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
When APB clock frequency changes, high-resolution timer (esp_timer)
|
|
|
|
|
scale and base value need to be adjusted. Each adjustment may cause
|
|
|
|
|
small error, and over time such small errors may cause time drift.
|
|
|
|
|
If this option is enabled, RTC timer will be used as a reference to
|
|
|
|
|
compensate for the drift.
|
|
|
|
|
It is recommended that this option is only used if 32k XTAL is selected
|
|
|
|
|
as RTC clock source.
|
|
|
|
|
|
|
|
|
|
config PM_PROFILING
|
|
|
|
|
bool "Enable profiling counters for PM locks"
|
|
|
|
|
depends on PM_ENABLE
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If enabled, esp_pm_* functions will keep track of the amount of time
|
|
|
|
|
each of the power management locks has been held, and esp_pm_dump_locks
|
|
|
|
|
function will print this information.
|
|
|
|
|
This feature can be used to analyze which locks are preventing the chip
|
|
|
|
|
from going into a lower power state, and see what time the chip spends
|
|
|
|
|
in each power saving mode. This feature does incur some run-time
|
|
|
|
|
overhead, so should typically be disabled in production builds.
|
|
|
|
|
|
|
|
|
|
config PM_TRACE
|
|
|
|
|
bool "Enable debug tracing of PM using GPIOs"
|
|
|
|
|
depends on PM_ENABLE
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If enabled, some GPIOs will be used to signal events such as RTOS ticks,
|
|
|
|
|
frequency switching, entry/exit from idle state. Refer to pm_trace.c
|
|
|
|
|
file for the list of GPIOs.
|
|
|
|
|
This feature is intended to be used when analyzing/debugging behavior
|
|
|
|
|
of power management implementation, and should be kept disabled in
|
|
|
|
|
applications.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
endmenu # "Power Management"
|
