Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Anssi Hannula <anssi.hannula@bitwise.fi>,
	Michal Simek <michal.simek@xilinx.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.com>,
	linux-serial@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org,
	Shubhrajyoti Datta <shubhraj@xilinx.com>
Subject: Re: [PATCH] serial: uartps: Fix stuck ISR if RX disabled with non-empty FIFO
Date: Thu, 14 Feb 2019 07:35:46 +0100	[thread overview]
Message-ID: <d58d8b99-71ee-d9d4-7217-767cc09989ac@xilinx.com> (raw)
In-Reply-To: <20190206140813.15349-1-anssi.hannula@bitwise.fi>

+ Shubhrajyoti

On 06. 02. 19 15:08, Anssi Hannula wrote:
> If RX is disabled while there are still unprocessed bytes in RX FIFO,
> cdns_uart_handle_rx() called from interrupt handler will get stuck in
> the receive loop as read bytes will not get removed from the RX FIFO
> and CDNS_UART_SR_RXEMPTY bit will never get set.
> 
> Avoid the stuck handler by checking first if RX is disabled. port->lock
> protects against race with RX-disabling functions.
> 
> This HW behavior was mentioned by Nathan Rossi in 43e98facc4a3 ("tty:
> xuartps: Fix RX hang, and TX corruption in termios call") which fixed a
> similar issue in cdns_uart_set_termios().
> The behavior can also be easily verified by e.g. setting
> CDNS_UART_CR_RX_DIS at the beginning of cdns_uart_handle_rx() - the
> following loop will then get stuck.
> 
> Resetting the FIFO using RXRST would not set RXEMPTY either so simply
> issuing a reset after RX-disable would not work.
> 
> I observe this frequently on a ZynqMP board during heavy RX load at 1M
> baudrate when the reader process exits and thus RX gets disabled.
> 
> Fixes: 61ec9016988f ("tty/serial: add support for Xilinx PS UART")
> Signed-off-by: Anssi Hannula <anssi.hannula@bitwise.fi>
> Cc: stable@vger.kernel.org
> ---
>  drivers/tty/serial/xilinx_uartps.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/tty/serial/xilinx_uartps.c b/drivers/tty/serial/xilinx_uartps.c
> index 094f2958cb2b..f0c4f59d9314 100644
> --- a/drivers/tty/serial/xilinx_uartps.c
> +++ b/drivers/tty/serial/xilinx_uartps.c
> @@ -219,6 +219,13 @@ static void cdns_uart_handle_rx(void *dev_id, unsigned int isrstatus)
>  
>  	is_rxbs_support = cdns_uart->quirks & CDNS_UART_RXBS_SUPPORT;
>  
> +	/*
> +	 * RXEMPTY will never be set if RX is disabled as read bytes
> +	 * will not be removed from the FIFO
> +	 */
> +	if (readl(port->membase + CDNS_UART_CR) & CDNS_UART_CR_RX_DIS)
> +		return;
> +
>  	while ((readl(port->membase + CDNS_UART_SR) &
>  		CDNS_UART_SR_RXEMPTY) != CDNS_UART_SR_RXEMPTY) {
>  		if (is_rxbs_support)
> 


Please review.
M

  reply	other threads:[~2019-02-14  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 14:08 [PATCH] serial: uartps: Fix stuck ISR if RX disabled with non-empty FIFO Anssi Hannula
2019-02-14  6:35 ` Michal Simek [this message]
2019-02-14  6:46   ` Shubhrajyoti Datta
2019-02-15 16:45     ` [PATCH v2] " Anssi Hannula

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=d58d8b99-71ee-d9d4-7217-767cc09989ac@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=anssi.hannula@bitwise.fi \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=shubhraj@xilinx.com \
    --cc=stable@vger.kernel.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