From: Tuomas Tynkkynen <tuomas@tuxera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] serial_bcm283x_mu: Flush RX queue after setting baud rate
Date: Fri, 9 Mar 2018 18:04:15 +0200 [thread overview]
Message-ID: <20180309180415.752cce2a@duuni> (raw)
In-Reply-To: <20180307210825.50709-2-agraf@suse.de>
On Wed, 7 Mar 2018 22:08:24 +0100
Alexander Graf <agraf@suse.de> wrote:
> After the UART was initialized, we may still have bogus data in the
> RX queue if it was enabled with incorrect pin muxing before.
>
> So let's flush the RX queue whenever we initialize baud rates.
>
> This fixes a regression with the dynamic pinmuxing code when enable_uart=1
> is not set in config.txt.
>
> Fixes: caf2233b28 ("bcm283x: Add pinctrl driver")
> Reported-by: Göran Lundberg <goran@lundberg.email>
> Reported-by: Peter Robinson <pbrobinson@gmail.com>
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
> drivers/serial/serial_bcm283x_mu.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
On a RPi 1, with no enable_uart in config.txt:
Tested-by: Tuomas Tynkkynen <tuomas@tuxera.com>
next prev parent reply other threads:[~2018-03-09 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 21:08 [U-Boot] [PATCH v2 0/2] [for 2018.03] RPi: Drain RX queue on setbrg Alexander Graf
2018-03-07 21:08 ` [U-Boot] [PATCH v2 1/2] serial_bcm283x_mu: Flush RX queue after setting baud rate Alexander Graf
2018-03-08 10:05 ` Peter Robinson
2018-03-09 16:04 ` Tuomas Tynkkynen [this message]
2018-03-09 18:29 ` [U-Boot] [U-Boot, v2, " Tom Rini
2018-03-07 21:08 ` [U-Boot] [PATCH v2 2/2] bcm283x_pl011: " Alexander Graf
2018-03-08 10:06 ` Peter Robinson
2018-03-09 16:04 ` Tuomas Tynkkynen
2018-03-09 18:29 ` [U-Boot] [U-Boot, v2, " 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=20180309180415.752cce2a@duuni \
--to=tuomas@tuxera.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.