zephyr/tests/drivers/uart/uart_mix_fifo_poll
Krzysztof Chruściński 62517f90dd tests: drivers: uart: uart_mix_fifo_poll: Clean up testcase.yaml
Clean up after automatic merge. Some test configurations got removed
and multiple lines enabling test for nrf54l09pdk/nrf54l09/cpuapp
target remained at the bottom of the file.

Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
2025-01-22 10:39:08 +01:00
..
boards tests: drivers: uart: uart_mix_fifo_poll: Enable device PM 2025-01-22 10:39:08 +01:00
src tests: drivers: uart: uart_mix_fifo_poll: Enable device PM 2025-01-22 10:39:08 +01:00
CMakeLists.txt
Kconfig tests/drivers uart_mix_fifo_poll: Allow configuring test length 2024-01-16 14:55:07 -05:00
prj.conf
README.txt
testcase.yaml tests: drivers: uart: uart_mix_fifo_poll: Clean up testcase.yaml 2025-01-22 10:39:08 +01:00

The purpose of this test is to validate that uart_poll_out call is resilient to
being interrupted by another uart API call. That includes uart_poll_out called
from higher priority context, uart_fifo_fill called from UART interrupt context
and uart_tx called from higher priority context. Preemptions shall not lead to
any bytes being dropped.

This test is establishing 3 context from which uart_poll_out is called:
- main thread
- higher priority thread
- k_timer timeout context

From each context stream of data is being sent. Bytes in streams are encoded as
following: 4 MSB bits contains stream ID, 4 LSB bits are incremented.

Test requires that two pairs of pins are shortened: TX with RX and CTS with RTS.
UART receives loopback data and validates if for each stream (identified by ID)
data is consistent.