public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Yunhui Cui <cuiyunhui@bytedance.com>
Cc: arnd@arndb.de,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	 benjamin.larsson@genexis.eu,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 heikki.krogerus@linux.intel.com,
	Jiri Slaby <jirislaby@kernel.org>,
	 jkeeping@inmusicbrands.com, john.ogness@linutronix.de,
	 LKML <linux-kernel@vger.kernel.org>,
	 linux-serial <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 v5 4/4] serial: 8250_dw: fix PSLVERR on RX_TIMEOUT
Date: Tue, 6 May 2025 15:25:35 +0300 (EEST)	[thread overview]
Message-ID: <85e57aad-c612-7f1a-03cf-cabd406a1c44@linux.intel.com> (raw)
In-Reply-To: <20250506112321.61710-4-cuiyunhui@bytedance.com>

I think shortlog should include mention to "dummy read" to make it a 
bit more specific.

On Tue, 6 May 2025, Yunhui Cui wrote:

> In the case of RX_TIMEOUT, to avoid PSLVERR, disable the FIFO

As with patch 2, please don't assume it is know to the reader how PSLVERR 
is triggered.

> before reading UART_RX when UART_LSR_DR is not set.

IMO, it would be better to explain the problem better first, something 
along these lines:

DW UART can fire RX_TIMEOUT interrupt without data and remain in that 
state forever. dw8250_handle_irq() detects this condition by checking if 
UART_LSR_DR is not asserted when RX_TIMEOUT occurred, and if detected, 
performs a dummy read to kick DW UART out of this state.

Performing dummy read from UART_RX is problematic because with ... it lead 
to ...

And only then explain the solution (disable FIFO for while performing of 
the dummy read).

> 
> 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 | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/tty/serial/8250/8250_dw.c b/drivers/tty/serial/8250/8250_dw.c
> index f41c4a9ed58b..ffa8cb10b39c 100644
> --- a/drivers/tty/serial/8250/8250_dw.c
> +++ b/drivers/tty/serial/8250/8250_dw.c
> @@ -288,9 +288,17 @@ 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)
> +				serial_out(up, UART_FCR, 0);
> +
>  			(void) p->serial_in(p, UART_RX);
>  
> +			if (up->fcr & UART_FCR_ENABLE_FIFO)
> +				serial_out(up, UART_FCR, up->fcr);
> +		}
> +
>  		uart_port_unlock_irqrestore(p, flags);
>  	}
>  
> 

-- 
 i.


  reply	other threads:[~2025-05-06 12:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 11:23 [PATCH v5 1/4] serial: 8250: fix panic due to PSLVERR Yunhui Cui
2025-05-06 11:23 ` [PATCH v5 2/4] serial: 8250: avoid potential PSLVERR issue Yunhui Cui
2025-05-06 12:00   ` Ilpo Järvinen
2025-05-12  6:37     ` [External] " yunhui cui
2025-05-12 10:27       ` Ilpo Järvinen
2025-05-12 11:46         ` yunhui cui
2025-05-12 12:02           ` Ilpo Järvinen
2025-05-12 14:00             ` yunhui cui
2025-05-06 11:23 ` [PATCH v5 3/4] serial: 8250_dw: warning on entering dw8250_force_idle unlocked Yunhui Cui
2025-05-06 12:06   ` Ilpo Järvinen
2025-05-06 12:08     ` Ilpo Järvinen
2025-05-06 11:23 ` [PATCH v5 4/4] serial: 8250_dw: fix PSLVERR on RX_TIMEOUT Yunhui Cui
2025-05-06 12:25   ` Ilpo Järvinen [this message]
2025-05-08 11:51     ` [External] " yunhui cui
2025-05-06 12:34 ` [PATCH v5 1/4] serial: 8250: fix panic due to PSLVERR Ilpo Järvinen
2025-05-12  3:06   ` [External] " 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=85e57aad-c612-7f1a-03cf-cabd406a1c44@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --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=jirislaby@kernel.org \
    --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