Add DORMANT_CLOCK_SOURCE_RTC option on RP2040 #3048
No reviewers
Labels
No labels
bazel
bluetooth
board settings
boot_stage2
bug
build
c++
can't reproduce
clang
clib-interface
cmsis
code cleanliness
code size
compiler version issues
cyw43_driver
debug
discussion
documentation
duplicate
dynamic_clock
elf2uf2
enhancement
errata
filesystem
flash layout
floating point
FreeRTOS
hardware_adc
hardware_claim
hardware_clocks
hardware_dma
hardware_exception
hardware_flash
hardware_gpio
hardware_i2c
hardware_irq
hardware_pio
hardware_pwm
hardware_rcp
hardware_rtc
hardware_spi
hardware_sync
hardware_uart
hardware_vreg
hardware_watchdog
hardware_xosc
help wanted
host
IAR
installation
invalid
linker scripts
lto
lwip
mbedtls
missing API
needs reporter detail
networking
newlib
newlib-multicore
non-c
non-cmake
non-gcc
openocd
orphan PR
OS integration
pico_async_context
pico_base
pico_binary_info
pico_flash
picolibc
pico_lwip
pico_malloc
pico_multicore
pico_printf
pico_runtime
pico_stdio
pico_stdio_usb
pico_sync
pico_time
pico_util
pioasm
port
question
review
review2
rtos interop
runtime init
static library
svd
test
tinyusb
vscode
wifi integration
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-raspberrypi/pico-sdk!3048
Loading…
Reference in a new issue
No description provided.
Delete branch "low-power-dormant-rtc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This runs RTC from XOSC, which allows going dormant without an external timer, at the expense of higher power consumption (about double
DORMANT_CLOCK_SOURCE_XOSC, but still 5x less than sleep)I think this is the lowest power the RP2040 can run at without an external clock source for the RTC, so is a useful option to add
Does the "except clk_rtc which will be run from the XOSC" here mean that the "but XOSC and ROSC will be stopped" wording a few lines above needs to be changed? 🤷 (I'm afraid I never got to grips with all this clock-source stuff)
I think I won't change it up there, but can add more to this note:
@ -243,6 +250,13 @@ int low_power_dormant_until_aon_timer(absolute_time_t until, dormant_clock_sourc*I guess the "In this case the XOSC will not be stopped." ought to be mentioned here too?
@ -243,6 +250,13 @@ int low_power_dormant_until_aon_timer(absolute_time_t until, dormant_clock_sourc*Thanks, added