From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
"Jiri Slaby" <jirislaby@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>
Subject: Re: [PATCH 2/2] serial: bcm63xx-uart: fix tx after conversion to uart_port_tx_limited()
Date: Sun, 25 Feb 2024 17:14:49 +0100 [thread overview]
Message-ID: <2024022537-sprite-vocalize-fe3f@gregkh> (raw)
In-Reply-To: <20240225151426.1342285-2-jonas.gorski@gmail.com>
On Sun, Feb 25, 2024 at 04:14:26PM +0100, Jonas Gorski wrote:
> When bcm63xx-uart was converted to uart_port_tx_limited(), it implicitly
> added a call to stop_tx(). This causes garbage to be put out on the
> serial console. To fix this, pass UART_TX_NOSTOP in flags, and manually
> call stop_tx() ourselves analogue to how a similar issue was fixed in
> commit 7be50f2e8f20 ("serial: mxs-auart: fix tx").
>
> Fixes: d11cc8c3c4b6 ("tty: serial: use uart_port_tx_limited()")
> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
> ---
> drivers/tty/serial/bcm63xx_uart.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serial/bcm63xx_uart.c b/drivers/tty/serial/bcm63xx_uart.c
> index a3cefa153456..259fe5895032 100644
> --- a/drivers/tty/serial/bcm63xx_uart.c
> +++ b/drivers/tty/serial/bcm63xx_uart.c
> @@ -309,8 +309,8 @@ static void bcm_uart_do_tx(struct uart_port *port)
>
> val = bcm_uart_readl(port, UART_MCTL_REG);
> val = (val & UART_MCTL_TXFIFOFILL_MASK) >> UART_MCTL_TXFIFOFILL_SHIFT;
> -
> - pending = uart_port_tx_limited(port, ch, port->fifosize - val,
> + pending = uart_port_tx_limited_flags(port, ch, UART_TX_NOSTOP,
> + port->fifosize - val,
> true,
> bcm_uart_writel(port, ch, UART_FIFO_REG),
> ({}));
> @@ -321,6 +321,9 @@ static void bcm_uart_do_tx(struct uart_port *port)
> val = bcm_uart_readl(port, UART_IR_REG);
> val &= ~UART_TX_INT_MASK;
> bcm_uart_writel(port, val, UART_IR_REG);
> +
> + if (uart_tx_stopped(port))
> + bcm_uart_stop_tx(port);
> }
>
> /*
> --
> 2.34.1
>
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- You have marked a patch with a "Fixes:" tag for a commit that is in an
older released kernel, yet you do not have a cc: stable line in the
signed-off-by area at all, which means that the patch will not be
applied to any older kernel releases. To properly fix this, please
follow the documented rules in the
Documentation/process/stable-kernel-rules.rst file for how to resolve
this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
prev parent reply other threads:[~2024-02-25 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 15:14 [PATCH 1/2] serial: core: introduce uart_port_tx_limited_flags() Jonas Gorski
2024-02-25 15:14 ` [PATCH 2/2] serial: bcm63xx-uart: fix tx after conversion to uart_port_tx_limited() Jonas Gorski
2024-02-25 16:14 ` Greg Kroah-Hartman [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=2024022537-sprite-vocalize-fe3f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=florian.fainelli@broadcom.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).