From: "Pali Rohár" <pali@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: "Simon Glass" <sjg@chromium.org>,
u-boot@lists.denx.de, "Marek Behún" <kabel@kernel.org>
Subject: Re: [PATCH] serial: ns16550: Wait in debug_uart_init until tx buffer is empty
Date: Mon, 4 Jul 2022 10:41:36 +0200 [thread overview]
Message-ID: <20220704084136.pgxsddnvshsx7a6p@pali> (raw)
In-Reply-To: <32ac71aa-2d33-6b8b-a0aa-122a71973867@denx.de>
On Friday 01 July 2022 09:21:34 Stefan Roese wrote:
> On 23.06.22 14:13, Pali Rohár wrote:
> > Commit d293759d55cc ("serial: ns16550: Add support for
> > SPL_DEBUG_UART_BASE") fixed support for setting correct early debug UART
> > base address in SPL.
> >
> > But after this commit, output from Marvell A385 BootROM is truncated or
> > lost and not fully present on serial console.
> >
> > Debugging this issue showed that BootROM just put bytes into UART HW output
> > buffer and does not wait until UART HW transmit all characters. U-Boot
> > ns16550 early debug is initialized very early and during its initialization
> > is resetting UART HW and flushing remaining transmit buffer (which still
> > contains BootROM output).
> >
> > Fix this issue by waiting in init function prior resetting UART HW until
> > TxEmpty bit in UART Line Status Register is set. TxEmpty is set when all
> > remaining bytes from HW buffer are transmitted.
> >
> > Signed-off-by: Pali Rohár <pali@kernel.org>
>
> Just checking, do you need a "Fixes" tag as well here?
Well, ns16550_init() function already contains that waiting for
UART_LSR_TEMT bit. This was introduced in following commit years ago:
https://source.denx.de/u-boot/u-boot/-/commit/cb55b3320014b7f6014416c556fe506efbf0a84b
So probably the "fixes" tag could contain commit which introduced
_debug_uart_init() function. It was in this commit years ago:
https://source.denx.de/u-boot/u-boot/-/commit/21d004368fc8a4da07147c58dfe9a4e16d4ab761
Support for SPL_DEBUG_UART_BASE in my recent commit just caused to hit
issue that in _debug_uart_init() is missing waiting until TxEmpty.
> > ---
> > drivers/serial/ns16550.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/serial/ns16550.c b/drivers/serial/ns16550.c
> > index 78bfe6281ce3..13418004e2b0 100644
> > --- a/drivers/serial/ns16550.c
> > +++ b/drivers/serial/ns16550.c
> > @@ -328,6 +328,8 @@ static inline void _debug_uart_init(void)
> > struct ns16550 *com_port = (struct ns16550 *)CONFIG_VAL(DEBUG_UART_BASE);
> > int baud_divisor;
> > + while (!(serial_din(&com_port->lsr) & UART_LSR_TEMT));
>
> I personally prefer the ";" in a separate line instead. Not sure what
> the official coding style mentions to such constructs.
I have no problem with this change. If you prefer it, feel free to move
";" to next separate line.
> Anyways:
>
> Reviewed-by: Stefan Roese <sr@denx.de>
>
> Thanks,
> Stefan
next prev parent reply other threads:[~2022-07-04 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 12:13 [PATCH] serial: ns16550: Wait in debug_uart_init until tx buffer is empty Pali Rohár
2022-07-01 7:21 ` Stefan Roese
2022-07-04 8:41 ` Pali Rohár [this message]
2022-07-08 16:39 ` Tom Rini
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=20220704084136.pgxsddnvshsx7a6p@pali \
--to=pali@kernel.org \
--cc=kabel@kernel.org \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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).