From: "Yicong Yang" <yang.yicong@picoheart.com>
To: <ilpo.jarvinen@linux.intel.com>,
<andriy.shevchenko@linux.intel.com>,
<linux-serial@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <gregkh@linuxfoundation.org>, <jirislaby@kernel.org>,
<geshijian@picoheart.com>, <yangyang.8776@picoheart.com>,
<yanligen@picoheart.com>, <yang.yicong@picoheart.com>
Subject: [PATCH v2] serial: 8250_dw: Prefer SRBR in bogus RX timeout workaround if available
Date: Mon, 7 Sep 2026 15:40:35 +0800 [thread overview]
Message-ID: <20260907074035.77796-1-yang.yicong@picoheart.com> (raw)
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>
---
Change since v2:
- simply the workaround path per Ilpo and Andy
- run ~48k reboot tests and didn't reproduce the issue
Link: https://lore.kernel.org/linux-serial/20260629075510.32854-1-yang.yicong@picoheart.com/
drivers/tty/serial/8250/8250_dw.c | 9 ++++++++-
drivers/tty/serial/8250/8250_dwlib.c | 5 +++++
drivers/tty/serial/8250/8250_dwlib.h | 4 ++++
3 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/drivers/tty/serial/8250/8250_dw.c b/drivers/tty/serial/8250/8250_dw.c
index 51d026f20825..b8a0bca8b536 100644
--- a/drivers/tty/serial/8250/8250_dw.c
+++ b/drivers/tty/serial/8250/8250_dw.c
@@ -439,8 +439,15 @@ static int dw8250_handle_irq(struct uart_port *p)
if (!up->dma && rx_timeout) {
status = serial_lsr_in(up);
+ /*
+ * Do the bogus read from Shadow RBR (SRBR) if provided.
+ * Both RBR and SRBR are supported ways to workaround
+ * this problem. But read RBR can cause hardware error
+ * (PSLVERR) if hardware choose to implement in this way
+ * (implement REG_TIMEOUT_WIDTH to 0), whereas SRBR won't.
+ */
if (!(status & (UART_LSR_DR | UART_LSR_BI)))
- serial_port_in(p, UART_RX);
+ serial_port_in(p, d->data.srbr);
}
/* Manually stop the Rx DMA transfer when acting as flow controller */
diff --git a/drivers/tty/serial/8250/8250_dwlib.c b/drivers/tty/serial/8250/8250_dwlib.c
index 8859e66d2d71..9bb02a4ab11f 100644
--- a/drivers/tty/serial/8250/8250_dwlib.c
+++ b/drivers/tty/serial/8250/8250_dwlib.c
@@ -247,5 +247,10 @@ void dw8250_setup_port(struct uart_port *p)
if (reg & DW_UART_CPR_SIR_MODE)
up->capabilities |= UART_CAP_IRDA;
+
+ if (reg & DW_UART_CPR_SHADOW)
+ pd->srbr = DW_UART_SRBR_0;
+ else
+ pd->srbr = UART_RX;
}
EXPORT_SYMBOL_GPL(dw8250_setup_port);
diff --git a/drivers/tty/serial/8250/8250_dwlib.h b/drivers/tty/serial/8250/8250_dwlib.h
index 1fe52332e774..6cfe2ab2e2a0 100644
--- a/drivers/tty/serial/8250/8250_dwlib.h
+++ b/drivers/tty/serial/8250/8250_dwlib.h
@@ -13,6 +13,7 @@
#include "8250.h"
/* Offsets for the DesignWare specific registers */
+#define DW_UART_SRBR_0 0x0c /* Shadow Receive Buffer Register */
#define DW_UART_USR 0x1f /* UART Status Register */
#define DW_UART_DMASA 0xa8 /* DMA Software Ack */
#define DW_UART_TCR 0xac /* Transceiver Control Register (RS485) */
@@ -90,6 +91,9 @@ struct dw8250_port_data {
/* RS485 variables */
bool hw_rs485_support;
+
+ /* Shadow RBR offset, fallback to RBR if no shadow register support */
+ unsigned int srbr;
};
void dw8250_do_set_termios(struct uart_port *p, struct ktermios *termios, const struct ktermios *old);
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-09-07 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 7:40 Yicong Yang [this message]
2026-09-07 7:49 ` [PATCH v2] serial: 8250_dw: Prefer SRBR in bogus RX timeout workaround if available sashiko-bot
2026-09-08 10:25 ` Andy Shevchenko
2026-09-08 11:52 ` Yicong Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260907074035.77796-1-yang.yicong@picoheart.com \
--to=yang.yicong@picoheart.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=geshijian@picoheart.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=yangyang.8776@picoheart.com \
--cc=yanligen@picoheart.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox