From 26d61c867077e0b529f7ab301188101e7352022d Mon Sep 17 00:00:00 2001 From: Kinsey Moore Date: Wed, 23 Jun 2021 11:57:18 -0500 Subject: 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. --- bsps/aarch64/xilinx-zynqmp/console/console.c | 5 ----- 1 file changed, 5 deletions(-) (limited to 'bsps/aarch64/xilinx-zynqmp') 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); } -- cgit v1.2.3