Add documentation to dma_channel_abort regarding errata RP2040-E13 #816
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!816
Loading…
Reference in a new issue
No description provided.
Delete branch "dma_abort_docs"
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?
See https://github.com/raspberrypi/pico-feedback/issues/224
Note this is a documentation only fix, as
dma_channel_abortdoes not have enough information to efficiently workaround the issue on the callers behalf.@ -473,6 +473,32 @@ static inline void dma_channel_start(uint channel) {*"an channel completion" -> "a channel completion"
I fixed the typo pointed out by @lurch. I also made another change, which might be more contentious, so feel free to back out: poll BUSY rather than ABORT to check for ABORT completion, to guarantee the channel is returned to a quiescent state before the function exits. ABORT clears prematurely due to the erratum (in fact this is the erratum).
The difference in timing is the time taken for the in-flight transfers to drain from the bus FIFOs, which should be a few cycles.
Does the ABORT->BUSY change have an effect on what happens if the channel is disabled?
No. BUSY clears once the in-flight and not-yet-issued transfer counts both reach 0. The not-yet-issued count is cleared by the ABORT, and EN=0 does not prevent in-flight transfers from completing.
@ -473,6 +473,32 @@ static inline void dma_channel_start(uint channel) {*Another typo: "to" is twice.
Note I force merged this as the only change after approval was a type in a comment