From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Gabriel Matni <gabriel.matni@exfo.com>
Cc: "Miquel Raynal" <miquel.raynal@bootlin.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Grégory Clement" <gregory.clement@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v3] serial: mvebu-uart: fix tx lost characters
Date: Thu, 22 Mar 2018 18:35:29 +0100 [thread overview]
Message-ID: <20180322173529.GA24597@kroah.com> (raw)
In-Reply-To: <3B588D51285A4A4D8D39C94212E07826279E39@SPQCMBX02.exfo.com>
On Tue, Mar 20, 2018 at 04:09:38PM +0000, Gabriel Matni wrote:
> From: Gabriel Matni <gabriel.matni@exfo.com>
>
> Fixes missing characters on kernel console at low baud rates (i.e.9600).
> The driver should poll TX_RDY or TX_FIFO_EMP instead of TX_EMP to ensure
> that the transmitter holding register (THR) is ready to receive a new byte.
>
> TX_EMP tells us when it is possible to send a break sequence via
> SND_BRK_SEQ. While this also indicates that both the THR and the TSR are
> empty, it does not guarantee that a new byte can be written just yet.
>
> Fixes: 30530791a7a0 ("serial: mvebu-uart: initial support for Armada-3700 serial port")
> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
> Acked-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> Signed-off-by: Gabriel Matni <gabriel.matni@exfo.com>
> ---
> Changes since v2:
> - use one line for the "Fixes" entry
> - removed trailing space between Signed-off-by entry and ---
> - start using versioning, previous fixes in v1
>
> Changes since v1:
> - patch was corrupt, could not be applied
> - fixed line indent
> ---
> drivers/tty/serial/mvebu-uart.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/mvebu-uart.c b/drivers/tty/serial/mvebu-uart.c
> index a100e98259d7..f0df0640208e 100644
> --- a/drivers/tty/serial/mvebu-uart.c
> +++ b/drivers/tty/serial/mvebu-uart.c
> @@ -618,7 +618,7 @@ static void wait_for_xmitr(struct uart_port *port)
> u32 val;
>
> readl_poll_timeout_atomic(port->membase + UART_STAT, val,
> - (val & STAT_TX_EMP), 1, 10000);
> + (val & STAT_TX_RDY(port)), 1, 10000);
> }
>
> static void mvebu_uart_console_putchar(struct uart_port *port, int ch)
> --
> 2.7.4
>
>
> > -----Original Message-----
> > From: gregkh@linuxfoundation.org <gregkh@linuxfoundation.org>
> > Sent: March 20, 2018 5:32 AM
> > To: Gabriel Matni <gabriel.matni@exfo.com>
> > Cc: Miquel Raynal <miquel.raynal@bootlin.com>; linux-
> > serial@vger.kernel.org; linux-arm-kernel@lists.infradead.org;
> > stable@vger.kernel.org; Grégory Clement <gregory.clement@bootlin.com>;
> > Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> > Subject: Re: [PATCH] serial: mvebu-uart: fix tx lost characters
<snip>
What is all of this below the patch for?
Please clean up and send this properly, in a clean email, with no "Re:"
on the subject line, as a new patch/email.
thanks,
greg k-h
prev parent reply other threads:[~2018-03-22 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 16:09 [PATCH v3] serial: mvebu-uart: fix tx lost characters Gabriel Matni
2018-03-22 17:35 ` gregkh [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=20180322173529.GA24597@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=gabriel.matni@exfo.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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