aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorqwerty19106 <[email protected]>2024-04-27 12:22:35 +0400
committerGitHub <[email protected]>2024-04-27 12:22:35 +0400
commitc929ad226b93d41df68b7787a582072f79ee08b6 (patch)
tree7856f04d6157f5555190658d4472276655eb3022
parent34074e6eb0741e084653b3ef71163393741f558b (diff)
Improve Uart::new_half_duplex docs
-rw-r--r--embassy-stm32/src/usart/mod.rs10
1 files changed, 6 insertions, 4 deletions
diff --git a/embassy-stm32/src/usart/mod.rs b/embassy-stm32/src/usart/mod.rs
index c00317983..68899bfff 100644
--- a/embassy-stm32/src/usart/mod.rs
+++ b/embassy-stm32/src/usart/mod.rs
@@ -926,8 +926,9 @@ impl<'d, T: BasicInstance> Uart<'d, T, Async> {
926 926
927 /// Create a single-wire half-duplex Uart transceiver on a single Tx pin. 927 /// Create a single-wire half-duplex Uart transceiver on a single Tx pin.
928 /// 928 ///
929 /// See [`new_half_duplex_on_rx`][`Self::new_half_duplex_on_rx`] if you would prefer to use an Rx pin. 929 /// See [`new_half_duplex_on_rx`][`Self::new_half_duplex_on_rx`] if you would prefer to use an Rx pin
930 /// There is no functional difference between these methods, as both allow bidirectional communication. 930 /// (when it is available for your chip). There is no functional difference between these methods, as both
931 /// allow bidirectional communication.
931 /// 932 ///
932 /// The pin is always released when no data is transmitted. Thus, it acts as a standard 933 /// The pin is always released when no data is transmitted. Thus, it acts as a standard
933 /// I/O in idle or in reception. 934 /// I/O in idle or in reception.
@@ -1079,8 +1080,9 @@ impl<'d, T: BasicInstance> Uart<'d, T, Blocking> {
1079 1080
1080 /// Create a single-wire half-duplex Uart transceiver on a single Tx pin. 1081 /// Create a single-wire half-duplex Uart transceiver on a single Tx pin.
1081 /// 1082 ///
1082 /// See [`new_half_duplex_on_rx`][`Self::new_half_duplex_on_rx`] if you would prefer to use an Rx pin. 1083 /// See [`new_half_duplex_on_rx`][`Self::new_half_duplex_on_rx`] if you would prefer to use an Rx pin
1083 /// There is no functional difference between these methods, as both allow bidirectional communication. 1084 /// (when it is available for your chip). There is no functional difference between these methods, as both
1085 /// allow bidirectional communication.
1084 /// 1086 ///
1085 /// The pin is always released when no data is transmitted. Thus, it acts as a standard 1087 /// The pin is always released when no data is transmitted. Thus, it acts as a standard
1086 /// I/O in idle or in reception. 1088 /// I/O in idle or in reception.