some comment cleanup #3150
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!3150
Loading…
Reference in a new issue
No description provided.
Delete branch "comment-cleanup"
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?
@ -21,0 +28,4 @@//// On RP2040 we preserve the original default lock numbers existing since SDK v1.0, since they are a// compatibility detail that out-of-tree code might rely on.The above paragraph explains why/when spinliock numbers are different on RP2350. I'm not sure we need this "On RP2040 we preserve the original default lock numbers" sentence?
This "0 on RP2040 unless..." wording gives no hint as to what the default value might be on RP2350, so perhaps it's better to explicitly state exactly when it is 0 (with the implication then being that it's 1 in any other situation)? I.e.
P.S. Looks like we might also need a
PICO_CONFIG:entry forPICO_IE_26_29_UNCHANGED_ON_RESET?@ -21,0 +28,4 @@//// On RP2040 we preserve the original default lock numbers existing since SDK v1.0, since they are a// compatibility detail that out-of-tree code might rely on.otherwise we would have just changed the default for all platforms
unset is unclear since it is unset or 0... feel free to make a PR/issue for adding
PICO_IE_26_20_UNCHANGED_ON_RESETLOL. I was originally going to write "...is 0" since that's more technically accurate, but I thought you'd prefer the "is unset" wording 😆
I created an issue ( #3153 ) rather than a PR, because I've no idea what the
descriptionforPICO_IE_26_20_UNCHANGED_ON_RESETshould be (nor where would be a sensible place to add it).