mirror of
https://github.com/espressif/esp-idf
synced 2025-03-10 09:39:10 -04:00
Merge branch 'bugfix/delete_duplicate_s3_pm_configs' into 'master'
esp32s3: delete duplicate s3 pm configs See merge request espressif/esp-idf!10715
This commit is contained in:
commit
902d630102
@ -526,53 +526,3 @@ menu "ESP32S3-Specific"
|
|||||||
wise RTC fast memory operates on APB clock and hence does not have much performance impact.
|
wise RTC fast memory operates on APB clock and hence does not have much performance impact.
|
||||||
|
|
||||||
endmenu # ESP32S3-Specific
|
endmenu # ESP32S3-Specific
|
||||||
|
|
||||||
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 CONFIG_ESP32S3_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.
|
|
||||||
|
|
||||||
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"
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user