From: Jiri Slaby <jirislaby@kernel.org>
To: Sherry Sun <sherry.sun@nxp.com>, gregkh@linuxfoundation.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-imx@nxp.com
Subject: Re: [PATCH V3] tty: serial: fsl_lpuart: count tty buffer overruns
Date: Thu, 13 Jan 2022 08:23:41 +0100 [thread overview]
Message-ID: <96b68539-d561-8ed6-f87f-d7fd2f9fe685@kernel.org> (raw)
In-Reply-To: <20220111085130.5817-1-sherry.sun@nxp.com>
On 11. 01. 22, 9:51, Sherry Sun wrote:
> Added support for counting the tty buffer overruns in fsl_lpuart driver
> like other uart drivers.
>
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
> ---
> changes in V3
>
> 1. Remove the initialization for copied as it is not necessary.
> ---
> drivers/tty/serial/fsl_lpuart.c | 20 +++++++++++++-------
> 1 file changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/tty/serial/fsl_lpuart.c b/drivers/tty/serial/fsl_lpuart.c
> index ce3e26144689..7d90c5a530ee 100644
> --- a/drivers/tty/serial/fsl_lpuart.c
> +++ b/drivers/tty/serial/fsl_lpuart.c
> @@ -931,7 +931,8 @@ static void lpuart_rxint(struct lpuart_port *sport)
> sport->port.sysrq = 0;
> }
>
> - tty_insert_flip_char(port, rx, flg);
> + if (tty_insert_flip_char(port, rx, flg) == 0)
> + sport->port.icount.buf_overrun++;
> }
>
> out:
> @@ -1024,7 +1025,8 @@ static void lpuart32_rxint(struct lpuart_port *sport)
> flg = TTY_OVERRUN;
> }
>
> - tty_insert_flip_char(port, rx, flg);
> + if (tty_insert_flip_char(port, rx, flg) == 0)
> + sport->port.icount.buf_overrun++;
> }
>
> out:
> @@ -1116,7 +1118,7 @@ static void lpuart_copy_rx_to_tty(struct lpuart_port *sport)
> struct dma_chan *chan = sport->dma_rx_chan;
> struct circ_buf *ring = &sport->rx_ring;
> unsigned long flags;
> - int count = 0;
> + int count = 0, copied;
>
> if (lpuart_is_32(sport)) {
> unsigned long sr = lpuart32_read(&sport->port, UARTSTAT);
> @@ -1218,20 +1220,24 @@ static void lpuart_copy_rx_to_tty(struct lpuart_port *sport)
> if (ring->head < ring->tail) {
> count = sport->rx_sgl.length - ring->tail;
>
> - tty_insert_flip_string(port, ring->buf + ring->tail, count);
> + copied = tty_insert_flip_string(port, ring->buf + ring->tail, count);
> + if (copied != count)
> + sport->port.icount.buf_overrun++;
> ring->tail = 0;
> - sport->port.icount.rx += count;
> + sport->port.icount.rx += copied;
> }
>
> /* Finally we read data from tail to head */
> if (ring->tail < ring->head) {
> count = ring->head - ring->tail;
> - tty_insert_flip_string(port, ring->buf + ring->tail, count);
> + copied = tty_insert_flip_string(port, ring->buf + ring->tail, count);
> + if (copied != count)
> + sport->port.icount.buf_overrun++;
> /* Wrap ring->head if needed */
> if (ring->head >= sport->rx_sgl.length)
> ring->head = 0;
> ring->tail = ring->head;
> - sport->port.icount.rx += count;
> + sport->port.icount.rx += copied;
> }
>
> exit:
--
js
suse labs
prev parent reply other threads:[~2022-01-13 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 8:51 Sherry Sun
2022-01-13 7:23 ` Jiri Slaby [this message]
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=96b68539-d561-8ed6-f87f-d7fd2f9fe685@kernel.org \
--to=jirislaby@kernel.org \
--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 \
/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
all inboxes | Powered by JetHome®