* Tony Lindgren <tony@xxxxxxxxxxx> [180416 15:47]:
> * Russell King - ARM Linux <linux@xxxxxxxxxxxxxxx> [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@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()?
Trying to see what we might be missing in 8250_omap compared
to omap-serial, your description sounds like it could be similar
issue compared to what got fixed for omap-serial earlier with
commit 0ba5f66836c9 ("tty: serial: OMAP: use a 1-byte RX FIFO
threshold in PIO mode").
> 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.
I'll try to debug this one a bit.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
