From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: 4.16 OMAP serial transmit corruption?
Date: Mon, 16 Apr 2018 08:45:45 -0700 [thread overview]
Message-ID: <20180416154545.GA5671@atomide.com> (raw)
In-Reply-To: <20180416151732.GU16141@n2100.armlinux.org.uk>
* Russell King - ARM Linux <linux@armlinux.org.uk> [180416 15:19]:
> Hi,
>
> I'm not entirely sure what's going on, but I see corrupted characters
> with the serial console on the OMAP4430 SDP board. During boot,
> everything seems fine, the problem appears to be userspace output.
>
> For example, if I edit a file, then quit vi:
>
> :q??%??B??Z?root at omap-4430sdp:~#
I don't think I've seen that one. What I've seen few times is
typing a key on the serial console echoing back the previous
character typed while the new character won't get displayed
until hitting keyboard again. Only rebooting the device seems
to solve this. This is with 4430 ES2.3 revision.
I wonder if we're missing some parts of errata i202 handling
in omap_8250_mdr1_errataset()?
Also, I'm seeing an issue where the UARTs won't idle on init
with 8250_omap driver if connected to the wl12xx bluetooth port
unless I write some data to the port first. It does not seem
to be related to the rts/cts lines being wired as I've tested
muxing them out of the way.
Regards,
Tony
next prev parent reply other threads:[~2018-04-16 15:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 15:17 4.16 OMAP serial transmit corruption? Russell King - ARM Linux
2018-04-16 15:45 ` Tony Lindgren [this message]
2018-04-16 21:26 ` Tony Lindgren
2018-04-16 23:01 ` Russell King - ARM Linux
2018-04-17 9:20 ` Vignesh R
2018-04-17 17:31 ` Tony Lindgren
2018-04-17 22:10 ` Russell King - ARM Linux
2018-04-18 0:57 ` Tony Lindgren
2018-04-18 8:18 ` Russell King - ARM Linux
2018-04-18 9:11 ` Vignesh R
2018-04-18 9:59 ` Russell King - ARM Linux
2018-04-18 10:27 ` Michael Nazzareno Trimarchi
2018-04-18 11:00 ` Russell King - ARM Linux
2018-04-18 11:45 ` Michael Nazzareno Trimarchi
2018-04-18 12:17 ` Russell King - ARM Linux
2018-04-18 12:47 ` Russell King - ARM Linux
2018-04-16 15:52 ` Tony Lindgren
2018-04-16 17:48 ` Russell King - ARM Linux
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=20180416154545.GA5671@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).