Uwe Kleine-König 9d3aaceb73 serial: 8250_fsl: Don't report FE, PE and OE twice
Some Freescale 8250 implementations have the problem that a single long
break results in one irq per character frame time. The code in
fsl8250_handle_irq() that is supposed to handle that uses the BI bit in
lsr_saved_flags to detect such a situation and then skip the second
received character. However it also stores other error bits and so after
a single frame error the character received in the next irq handling is
passed to the upper layer with a frame error, too.

So after a spike on the data line (which is correctly recognized as a
frame error) the following valid character is thrown away, because the
driver reports a frame error for that one, too.

To weaken this problem restrict saving LSR to only the BI bit.

Note however that the handling is still broken:

 - lsr_saved_flags is updated using orig_lsr which is the LSR content
   for the first received char, but there might be more in the FIFO, so
   a character is thrown away that is received later and not necessarily
   the one following the break.
 - The doubled break might be the 2nd and 3rd char in the FIFO, so the
   workaround doesn't catch these, because serial8250_rx_chars() doesn't
   handle the workaround.
 - lsr_saved_flags might have set UART_LSR_BI at the entry of
   fsl8250_handle_irq() which doesn't originate from
   fsl8250_handle_irq()'s "up->lsr_saved_flags |= orig_lsr &
   UART_LSR_BI;" but from e.g. from serial8250_tx_empty().
 - For a long or a short break this isn't about two characters, but more
   or only a single one.

Fixes: 9deaa53ac7fa ("serial: add irq handler for Freescale 16550 errata.")
Acked-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Link: https://lore.kernel.org/r/20220704085119.55900-1-u.kleine-koenig@pengutronix.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2022-07-08 15:13:22 +02:00
..
2022-06-03 11:48:47 -07:00
2022-06-04 13:42:53 -07:00
2022-05-15 18:31:28 -06:00
2022-06-17 07:58:39 -07:00
2022-06-03 11:48:47 -07:00
2022-05-29 11:38:27 -07:00
2022-05-25 16:18:27 -07:00
2022-06-17 11:32:35 +10:00
2022-06-04 14:04:27 -07:00
2022-05-26 21:08:40 -07:00
2022-06-07 15:00:29 -07:00
2022-05-31 09:56:54 -07:00
2022-06-02 15:23:54 -07:00
2022-06-17 11:22:58 -07:00
2022-06-02 15:23:54 -07:00
2022-06-07 14:24:30 -07:00
2022-05-27 21:24:19 -07:00
2022-05-25 15:02:26 +02:00
2022-06-03 11:48:47 -07:00
2022-06-02 15:23:54 -07:00
2022-05-23 21:06:11 -07:00
2022-05-19 16:56:17 +02:00
2022-06-12 11:33:42 -07:00
2022-06-03 11:48:47 -07:00
2022-06-02 15:23:54 -07:00
2022-06-03 11:48:47 -07:00
2022-06-03 11:48:47 -07:00
2022-06-03 11:48:47 -07:00
2022-06-05 09:25:12 -07:00
2022-06-01 13:49:15 -07:00
2022-06-11 16:32:47 -07:00
2022-06-05 09:25:12 -07:00
2022-06-05 09:25:12 -07:00