summaryrefslogtreecommitdiffstats
path: root/bsps/aarch64
diff options
context:
space:
mode:
authorKinsey Moore <kinsey.moore@oarcorp.com>2021-06-23 11:57:18 -0500
committerJoel Sherrill <joel@rtems.org>2021-06-29 11:42:06 -0500
commit26d61c867077e0b529f7ab301188101e7352022d (patch)
tree0551cb76c8b5f4713d4fb9624e791252405a1c6e /bsps/aarch64
parentspec/aarch64: fix abi flags for xilinx_versal_ilp32_vck190 (diff)
downloadrtems-26d61c867077e0b529f7ab301188101e7352022d.tar.bz2
bsps/zynq-uart: Make post baud change kick global
The existing fix for the ZynqMP UART hardware bug only caught the vast majority of instances where it could occur. To fully fix the data corruption, this fix must be applied after every baud rate change. This makes the logic reset and kick apply in any locations where the baud rate could be changed.
Diffstat (limited to 'bsps/aarch64')
-rw-r--r--bsps/aarch64/xilinx-zynqmp/console/console.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/bsps/aarch64/xilinx-zynqmp/console/console.c b/bsps/aarch64/xilinx-zynqmp/console/console.c
index 9886a117dc..d1948f1a0c 100644
--- a/bsps/aarch64/xilinx-zynqmp/console/console.c
+++ b/bsps/aarch64/xilinx-zynqmp/console/console.c
@@ -113,11 +113,6 @@ static void zynqmp_debug_console_early_init(char c)
zynq_uart_initialize(base);
BSP_output_char = zynqmp_debug_console_out;
- /*
- * Some ZynqMP UARTs have a hardware bug that causes TX/RX logic restarts to
- * require a kick after baud rate registers are initialized.
- */
- zynqmp_debug_console_out(0);
zynqmp_debug_console_out(c);
}