-
Vignesh Raghavendra authored
On K3 family of SoCs (which includes AM654 SoC), it is observed that RX TIMEOUT is signalled after RX FIFO has been drained, in which case a dummy read of RX FIFO is required to clear RX TIMEOUT condition. Otherwise, this would lead to an interrupt storm. Fix this by introducing UART_RX_TIMEOUT_QUIRK flag and doing a dummy read in IRQ handler when RX TIMEOUT is reported with no data in RX FIFO. Fixes: be708744 ("serial: 8250_omap: Add support for AM654 UART controller") Reported-by:
Jan Kiszka <jan.kiszka@siemens.com> Tested-by:
Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by:
Vignesh Raghavendra <vigneshr@ti.com> Link: https://lore.kernel.org/r/20210622145704.11168-1-vigneshr@ti.com Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
b67e830dVignesh Raghavendra authoredOn K3 family of SoCs (which includes AM654 SoC), it is observed that RX TIMEOUT is signalled after RX FIFO has been drained, in which case a dummy read of RX FIFO is required to clear RX TIMEOUT condition. Otherwise, this would lead to an interrupt storm. Fix this by introducing UART_RX_TIMEOUT_QUIRK flag and doing a dummy read in IRQ handler when RX TIMEOUT is reported with no data in RX FIFO. Fixes: be708744 ("serial: 8250_omap: Add support for AM654 UART controller") Reported-by:
Jan Kiszka <jan.kiszka@siemens.com> Tested-by:
Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by:
Vignesh Raghavendra <vigneshr@ti.com> Link: https://lore.kernel.org/r/20210622145704.11168-1-vigneshr@ti.com Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Loading