diff options
| author | Jiri Slaby <jslaby@suse.cz> | 2021-09-22 09:59:37 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-10-05 14:08:09 +0200 |
| commit | 215fa41c2dfb4cf36d5b39dea9417bfadc9e770e (patch) | |
| tree | ad92ef1a9c76d4c32c82d412d5f48a0c43a5acce /kernel/trace/trace_event_perf.c | |
| parent | ee7e5e66f2d4fa3cc05382d6f739c644a666010c (diff) | |
| download | linux-215fa41c2dfb4cf36d5b39dea9417bfadc9e770e.tar.gz linux-215fa41c2dfb4cf36d5b39dea9417bfadc9e770e.tar.bz2 linux-215fa41c2dfb4cf36d5b39dea9417bfadc9e770e.zip | |
mxser: don't read from UART_FCR
The UART_FCR register is write-only. When reading it, one gets contents
of (read-only) UART_IIR instead as they are shared. This mistake was
performed in mxser_flush_buffer() to clear FIFOs.
Actually FCR handling throughout the driver is completely broken. On
many places, it respects neither mu860 settings, nor FIFO (16450 vs
16550) setting. This patch doesn't help to fix this, it actually does
the same. We will introduce a mxser_port::FCR in the next patch to fix
this issue.
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Link: https://lore.kernel.org/r/20210922075938.31390-6-jslaby@suse.cz
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/trace/trace_event_perf.c')
0 files changed, 0 insertions, 0 deletions