diff options
| author | Yicong Yang <yang.yicong@picoheart.com> | 2026-09-08 22:15:24 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2026-09-23 14:49:34 +0200 |
| commit | 7c08f3c4da9205fc64a9c99180f9cffc3e435f7f (patch) | |
| tree | 4c57e172587bf717052f4ed36fef423f7a950cad /tools/perf/scripts/python/stackcollapse.py | |
| parent | d147a15be6840be7e842f7dcd658345a787e7867 (diff) | |
| download | linux-next-7c08f3c4da9205fc64a9c99180f9cffc3e435f7f.tar.gz linux-next-7c08f3c4da9205fc64a9c99180f9cffc3e435f7f.zip | |
serial: 8250_dw: Prefer SRBR in bogus RX timeout workaround if available
The DW uart could get into the cases where a bogus RX timeout
interrupt is asserted but no available data. This could be
workaround by doing a bogus read.
Currently the driver's using the standard RBR (receive buffer
register) for this bogus read. However the reading of RBR
in this case is allowed to raise a hardware error if vendor
choose to implement in this way (our platform). It's also
allowed to do the bogus read using SRBR (shadow RBR) for
workaround which won't raise the hardware error. So change
to use the SRBR to workaround the issue if it's available.
Signed-off-by: Yicong Yang <yang.yicong@picoheart.com>
Link: https://lore.kernel.org/linux-serial/20260907074035.77796-1-yang.yicong@picoheart.com/
Link: https://lore.kernel.org/linux-serial/20260629075510.32854-1-yang.yicong@picoheart.com/
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Link: https://patch.msgid.link/20260908141524.20302-1-yang.yicong@picoheart.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions