From: Jiri Slaby <jirislaby@kernel.org>
To: Yunhui Cui <cuiyunhui@bytedance.com>,
arnd@arndb.de, andriy.shevchenko@linux.intel.com,
benjamin.larsson@genexis.eu, gregkh@linuxfoundation.org,
heikki.krogerus@linux.intel.com, ilpo.jarvinen@linux.intel.com,
jkeeping@inmusicbrands.com, john.ogness@linutronix.de,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
markus.mayer@linaro.org, matt.porter@linaro.org,
namcao@linutronix.de, paulmck@kernel.org, pmladek@suse.com,
schnelle@linux.ibm.com, sunilvl@ventanamicro.com,
tim.kryger@linaro.org
Subject: Re: [PATCH v4 4/4] serial: 8250_dw: fix PSLVERR on RX_TIMEOUT
Date: Fri, 25 Apr 2025 08:43:22 +0200 [thread overview]
Message-ID: <9d4e7002-48fe-4fa0-8e23-7c2160419910@kernel.org> (raw)
In-Reply-To: <57d75d55-81e3-445f-a705-e8c116281515@kernel.org>
On 25. 04. 25, 8:41, Jiri Slaby wrote:
> On 25. 04. 25, 8:24, Yunhui Cui wrote:
>> In the case of RX_TIMEOUT, to avoid PSLVERR, disable the FIFO
>> before reading UART_RX when UART_LSR_DR is not set.
>>
>> Fixes: 424d79183af0 ("serial: 8250_dw: Avoid "too much work" from
>> bogus rx timeout interrupt")
>> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
>> ---
>> drivers/tty/serial/8250/8250_dw.c | 13 ++++++++++++-
>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/tty/serial/8250/8250_dw.c b/drivers/tty/
>> serial/8250/8250_dw.c
>> index 07f9be074b4b..1e364280a108 100644
>> --- a/drivers/tty/serial/8250/8250_dw.c
>> +++ b/drivers/tty/serial/8250/8250_dw.c
>> @@ -273,6 +273,7 @@ static int dw8250_handle_irq(struct uart_port *p)
>> unsigned int quirks = d->pdata->quirks;
>> unsigned int status;
>> unsigned long flags;
>> + unsigned char old_fcr;
>
> No more unsigned char, please. Use u8.
>
>> @@ -288,9 +289,19 @@ static int dw8250_handle_irq(struct uart_port *p)
>> uart_port_lock_irqsave(p, &flags);
>> status = serial_lsr_in(up);
>> - if (!(status & (UART_LSR_DR | UART_LSR_BI)))
>> + if (!(status & (UART_LSR_DR | UART_LSR_BI))) {
>> + /* To avoid PSLVERR, disable the FIFO first. */
>> + if (up->fcr & UART_FCR_ENABLE_FIFO) {
>> + old_fcr = serial_in(up, UART_FCR);
Wait, read(FCR) actually means read(IIR). FCR is write only. Or is DW
special in this?
>> + serial_out(up, UART_FCR, old_fcr & ~1);
>
> s/1/UART_FCR_ENABLE_FIFO/
>
>> + }
>> +
>> (void) p->serial_in(p, UART_RX);
>> + if (up->fcr & UART_FCR_ENABLE_FIFO)
>> + serial_out(up, UART_FCR, old_fcr);
>> + }
>> +
>> uart_port_unlock_irqrestore(p, flags);
>> }
>
>
--
js
suse labs
next prev parent reply other threads:[~2025-04-25 6:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 6:24 [PATCH v4 1/4] serial: 8250: fix panic due to PSLVERR Yunhui Cui
2025-04-25 6:24 ` [PATCH v4 2/4] serial: 8250: introduce serial8250_discard_data() Yunhui Cui
2025-04-25 6:48 ` Jiri Slaby
2025-05-06 10:38 ` [External] " yunhui cui
2025-04-25 8:22 ` John Ogness
2025-04-26 4:47 ` kernel test robot
2025-04-26 5:59 ` kernel test robot
2025-04-25 6:24 ` [PATCH v4 3/4] serial: 8250: warning on entering dw8250_force_idle unlocked Yunhui Cui
2025-04-25 6:24 ` [PATCH v4 4/4] serial: 8250_dw: fix PSLVERR on RX_TIMEOUT Yunhui Cui
2025-04-25 6:41 ` Jiri Slaby
2025-04-25 6:43 ` Jiri Slaby [this message]
2025-04-27 11:17 ` [External] " yunhui cui
2025-04-29 3:41 ` yunhui cui
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=9d4e7002-48fe-4fa0-8e23-7c2160419910@kernel.org \
--to=jirislaby@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=benjamin.larsson@genexis.eu \
--cc=cuiyunhui@bytedance.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jkeeping@inmusicbrands.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=markus.mayer@linaro.org \
--cc=matt.porter@linaro.org \
--cc=namcao@linutronix.de \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=schnelle@linux.ibm.com \
--cc=sunilvl@ventanamicro.com \
--cc=tim.kryger@linaro.org \
/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