From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-omap@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: 4.16 OMAP serial transmit corruption?
Date: Mon, 16 Apr 2018 18:48:26 +0100 [thread overview]
Message-ID: <20180416174826.GJ10990@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20180416155259.GB5671@atomide.com>
On Mon, Apr 16, 2018 at 08:52:59AM -0700, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@armlinux.org.uk> [180416 15:19]:
> > Since this uses a USB adapter (built onto the board) it could be
> > that there could be a bug in the driver for that rather than the
> > OMAP4430 SDP, but I've no way to check that hypothesis.
>
> Does it go away when you do a warm reboot of the sdp? Then
> it should not be related to the USB iff the ftdi chip is bus
> powered by VBUS.
Yes, the FTDI chip is bus powered.
I booted, ran vi, quit vi, saw corruption, typed reboot, waited for
it to reboot, ran vi, quit vi, and still saw corruption. So the
reboot seems to have had no effect.
I don't see it with other USB serial consoles on other machines...
I have two of these using the same FTDI chipset:
Bus 001 Device 021: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 020: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Device 20 is the SDP board, and device 21 is a ZII board. Both use
port 2 on the quad ftdi device. The serial console on the ZII board
is fine, so that seems to rule out the FTDI driver / FTDI hardware.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
According to speedtest.net: 8.21Mbps down 510kbps up
prev parent reply other threads:[~2018-04-16 17:48 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
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 [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=20180416174826.GJ10990@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=tony@atomide.com \
/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