summaryrefslogtreecommitdiff
path: root/drivers/tty
diff options
context:
space:
mode:
authorSascha Hauer <s.hauer@pengutronix.de>2019-05-17 13:01:38 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-05-21 13:18:17 +0300
commit8178eeb3e8007d29b1e9dfd3c4d0f90de0f6ce55 (patch)
tree4f37e770a61267a75431032d7b84b69800f8a43b /drivers/tty
parent61c0e37950b88bad590056286c1d766b1f167f4e (diff)
downloadlinux-8178eeb3e8007d29b1e9dfd3c4d0f90de0f6ce55.tar.xz
serial: imx: remove log spamming error message
Each time the DMA engine signals a transaction error the driver prints a message at error level. Getting transaction errors is pretty much expected on baudrate mismatches and the correspoding error counters are increased in this case properly. Remove the error message which is possibly repeated at a very high rate which can lock up the whole system. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Reviewed-by: Fabio Estevam <festevam@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/tty')
-rw-r--r--drivers/tty/serial/imx.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/tty/serial/imx.c b/drivers/tty/serial/imx.c
index dff75dc94731..8b752e895053 100644
--- a/drivers/tty/serial/imx.c
+++ b/drivers/tty/serial/imx.c
@@ -1165,7 +1165,6 @@ static void imx_uart_clear_rx_errors(struct imx_port *sport)
sport->port.icount.buf_overrun++;
tty_flip_buffer_push(port);
} else {
- dev_err(sport->port.dev, "DMA transaction error.\n");
if (usr1 & USR1_FRAMERR) {
sport->port.icount.frame++;
imx_uart_writel(sport, USR1_FRAMERR, USR1);