Skip to content

Clarify uart_write_blocking() API vs UART still busy sending (#1274) #1709

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jul 25, 2024
Merged

Clarify uart_write_blocking() API vs UART still busy sending (#1274) #1709

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4a59e48
Clarify uart_write_blocking() API vs UART still busy sending (#1274)
andygpz11 May 21, 2024
478fc3f
minor improvement to a comment: Clarify uart_write_blocking() API vs…
andygpz11 May 21, 2024
d26fbf4
Update uart.h
kilograham Jul 25, 2024
8064b7e
Update uart.h
kilograham Jul 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/rp2_common/hardware_uart/include/hardware/uart.h
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -312,6 +312,9 @@ static inline bool uart_is_readable(uart_inst_t *uart) {
* \ingroup hardware_uart
*
* This function will block until all the data has been sent to the UART transmit buffer
* hardware. Note: Serial data transmission will continue until the Tx FIFO and
* the transmit shift register (not programmer-accessible) are empty.
* To ensure the UART FIFO has been emptied, you can use \ref uart_tx_wait_blocking()
*
* \param uart UART instance. \ref uart0 or \ref uart1
* \param src The bytes to send
Expand Down