From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/2] [for 2018.03] RPi: Drain RX queue on setbrg
Date: Wed, 7 Mar 2018 22:08:23 +0100 [thread overview]
Message-ID: <20180307210825.50709-1-agraf@suse.de> (raw)
We had a few reports coming in from people that had their autoboot chain
aborted after pinmuxing support was added for the RPi.
The culprit is easy: The UARTs may have been enabled before, but muxed
to an incorrect pin. That pin may have pulled the RX line down which again
lead to lots of zero bytes gathered in the RX buffer.
The easy fix for that is to drain the RX queue every time we set the baud
rate.
This patch set is the minimally intrusive fix for the RPi. We may want to
do that generically for all serial devices later.
v1 -> v2:
- fix pl011 draining
Alexander Graf (2):
serial_bcm283x_mu: Flush RX queue after setting baud rate
bcm283x_pl011: Flush RX queue after setting baud rate
drivers/serial/serial_bcm283x_mu.c | 8 +++++++-
drivers/serial/serial_bcm283x_pl011.c | 25 ++++++++++++++++++++++++-
drivers/serial/serial_pl01x.c | 10 +++++-----
drivers/serial/serial_pl01x_internal.h | 7 ++++++-
4 files changed, 42 insertions(+), 8 deletions(-)
--
2.12.3
next reply other threads:[~2018-03-07 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 21:08 Alexander Graf [this message]
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
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=20180307210825.50709-1-agraf@suse.de \
--to=agraf@suse.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