Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
pico-sdk
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Microcontroller
pico-sdk
Commits
b3bf690d
Unverified
Commit
b3bf690d
authored
1 year ago
by
andygpz11
Committed by
GitHub
1 year ago
Browse files
Options
Downloads
Patches
Plain Diff
Clarify uart_write_blocking() API vs UART still busy sending (#1274) (#1709)
parent
9f85f256
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/rp2_common/hardware_uart/include/hardware/uart.h
+3
-0
3 additions, 0 deletions
src/rp2_common/hardware_uart/include/hardware/uart.h
with
3 additions
and
0 deletions
src/rp2_common/hardware_uart/include/hardware/uart.h
+
3
−
0
View file @
b3bf690d
...
@@ -312,6 +312,9 @@ static inline bool uart_is_readable(uart_inst_t *uart) {
...
@@ -312,6 +312,9 @@ static inline bool uart_is_readable(uart_inst_t *uart) {
* \ingroup hardware_uart
* \ingroup hardware_uart
*
*
* This function will block until all the data has been sent to the UART transmit buffer
* 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 uart UART instance. \ref uart0 or \ref uart1
* \param src The bytes to send
* \param src The bytes to send
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment