From: Jiri Slaby <jirislaby@kernel.org>
To: Sherry Sun <sherry.sun@nxp.com>,
gregkh@linuxfoundation.org, tomonori.sakita@sord.co.jp,
atsushi.nemoto@sord.co.jp
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-imx@nxp.com
Subject: Re: [PATCH] tty: serial: fsl_lpuart: Clear the error flags by writing 1 for lpuart32 platforms
Date: Mon, 31 Jul 2023 07:23:54 +0200 [thread overview]
Message-ID: <51a7f260-59f9-2cd4-9d49-484df00fb3b2@kernel.org> (raw)
In-Reply-To: <20230731015053.15150-1-sherry.sun@nxp.com>
On 31. 07. 23, 3:50, Sherry Sun wrote:
> Do not read the data register to clear the error flags for lpuart32
> platforms, the additional read may cause the receive FIFO underflow
> since the DMA has already read the data register.
> Now all lpuart32 platforms support write 1 to clear those error bits,
What does this "Now" mean? Will this change break some older platforms?
> let's use this method to better clear the error flags.
>
> Fixes: 42b68768e51b ("serial: fsl_lpuart: DMA support for 32-bit variant")
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> ---
> drivers/tty/serial/fsl_lpuart.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serial/fsl_lpuart.c b/drivers/tty/serial/fsl_lpuart.c
> index f6644c5989d3..f72e1340b47d 100644
> --- a/drivers/tty/serial/fsl_lpuart.c
> +++ b/drivers/tty/serial/fsl_lpuart.c
> @@ -1120,8 +1120,8 @@ static void lpuart_copy_rx_to_tty(struct lpuart_port *sport)
> unsigned long sr = lpuart32_read(&sport->port, UARTSTAT);
>
> if (sr & (UARTSTAT_PE | UARTSTAT_FE)) {
> - /* Read DR to clear the error flags */
> - lpuart32_read(&sport->port, UARTDATA);
> + /* Clear the error flags */
> + lpuart32_write(&sport->port, sr, UARTSTAT);
>
> if (sr & UARTSTAT_PE)
> sport->port.icount.parity++;
thanks,
--
js
suse labs
next prev parent reply other threads:[~2023-07-31 5:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 1:50 [PATCH] tty: serial: fsl_lpuart: Clear the error flags by writing 1 for lpuart32 platforms Sherry Sun
2023-07-31 5:23 ` Jiri Slaby [this message]
2023-07-31 5:50 ` Sherry Sun
2023-07-31 15:13 ` gregkh
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=51a7f260-59f9-2cd4-9d49-484df00fb3b2@kernel.org \
--to=jirislaby@kernel.org \
--cc=atsushi.nemoto@sord.co.jp \
--cc=gregkh@linuxfoundation.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sherry.sun@nxp.com \
--cc=tomonori.sakita@sord.co.jp \
/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