aboutsummaryrefslogtreecommitdiff
path: root/embassy-nrf/src/buffered_uarte/mod.rs
diff options
context:
space:
mode:
authorUlf Lilleengen <[email protected]>2025-10-28 13:52:53 +0000
committerGitHub <[email protected]>2025-10-28 13:52:53 +0000
commitafe9defe31c79444d3bf8eca5e2f0d4161fd96f9 (patch)
treeac3273028c11098689a5d0f637d905974b35aa09 /embassy-nrf/src/buffered_uarte/mod.rs
parent41ff72bbce343c1e3c5efa2939e08a73b9122552 (diff)
parent83deef3672c651ac86e7ad497eccc52119b3a27f (diff)
Merge pull request #4793 from embassy-rs/nrf54-new-pac
feat: improve nrf54 support using new nrf-pac
Diffstat (limited to 'embassy-nrf/src/buffered_uarte/mod.rs')
-rw-r--r--embassy-nrf/src/buffered_uarte/mod.rs14
1 files changed, 14 insertions, 0 deletions
diff --git a/embassy-nrf/src/buffered_uarte/mod.rs b/embassy-nrf/src/buffered_uarte/mod.rs
new file mode 100644
index 000000000..75d84baac
--- /dev/null
+++ b/embassy-nrf/src/buffered_uarte/mod.rs
@@ -0,0 +1,14 @@
1//! Async buffered UART driver.
2//!
3//! Note that discarding a future from a read or write operation may lead to losing
4//! data. For example, when using `futures_util::future::select` and completion occurs
5//! on the "other" future, you should capture the incomplete future and continue to use
6//! it for the next read or write. This pattern is a consideration for all IO, and not
7//! just serial communications.
8//!
9//! Please also see [crate::uarte] to understand when [BufferedUarte] should be used.
10#[cfg_attr(not(feature = "_nrf54l"), path = "v1.rs")]
11#[cfg_attr(feature = "_nrf54l", path = "v2.rs")]
12mod _version;
13
14pub use _version::*;