From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: rick@efn.org, linux-omap@vger.kernel.org, nmonson@gmail.com,
felipe.contreras@gmail.com, tom.leiming@gmail.com
Subject: [PATCH] serial: Flush posted write on 34xx to make 8250 work (Re: What happened to the serial console on BeagleBoard with 2.6.28-rc2?)
Date: Sun, 2 Nov 2008 12:50:21 -0800 [thread overview]
Message-ID: <20081102205019.GJ28924@atomide.com> (raw)
In-Reply-To: <200811021126.13514.david-b@pacbell.net>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
* David Brownell <david-b@pacbell.net> [081102 11:26]:
> On Sunday 02 November 2008, Rick Bronson wrote:
> > > Is that what you saw too?
> >
> > Yep, that's what I saw, but only if I had DEBUG_LL=y. Without that
> > I had nothing except "Uncompressing Linux........".
>
> I don't have DEBUG_LL=y ... if you had some kind of network
> link configured over USB, could you SSH in? (I can.)
>
>
> > I guess we don't see this problem on the other 2 ports since they
> > are mapped MT_MEMORY_SO and not MT_DEVICE (L4_34XX_PHYS).
>
> Hmm, inconsistency is to be avoided. :)
>
> I wonder what the root cause is ... is the driver missing
> various barriers needed to make MT_DEVICE work? Or is the
> MT_DEVICE incorrect in the first place? "git whatchanged"
> didn't show any recent changes that seemed (on a quick
> glance) to affect I/O at that level. Maybe it was one of
> the other TTY changes interacting here.
Yeah I don't know what may have changed, or have things just
gotten faster now with cortex since 2.6.27?
Anyways, this patch fixes the issue for me without marking
things strongly ordered. Rick, does this work for you?
Regards,
Tony
[-- Attachment #2: flush-posted-8250.patch --]
[-- Type: text/x-diff, Size: 906 bytes --]
>From 57eea529292418a20a119c5b18d7636cf44992ae Mon Sep 17 00:00:00 2001
From: Tony Lindgren <tony@atomide.com>
Date: Fri, 31 Oct 2008 16:47:42 -0700
Subject: [PATCH] serial: Flush posted write on 34xx to make 8250 work
On omap34xx, we need to flush posted writes for TX.
Signed-off-by: Tony Lindgren <tony@atomide.com>
diff --git a/drivers/serial/8250.c b/drivers/serial/8250.c
index 5f383d8..629a16c 100644
--- a/drivers/serial/8250.c
+++ b/drivers/serial/8250.c
@@ -413,6 +413,13 @@ serial_out(struct uart_8250_port *up, int offset, int value)
case UPIO_MEM:
writeb(value, up->port.membase + offset);
+#ifdef CONFIG_ARCH_OMAP
+ /* Flush posted write for TX */
+ if (cpu_is_omap34xx() && is_omap_port(up) &&
+ (save_offset == UART_TX || save_offset == UART_IER ||
+ save_offset == UART_LCR))
+ value = serial_in(up, UART_LCR); /* Safe to read */
+#endif
break;
case UPIO_RM9000:
next prev parent reply other threads:[~2008-11-02 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 18:03 What happened to the serial console on BeagleBoard with 2.6.28-rc2? Rick Bronson
2008-11-02 19:26 ` David Brownell
2008-11-02 20:50 ` Tony Lindgren [this message]
2008-11-02 21:52 ` [PATCH] serial: Flush posted write on 34xx to make 8250 work (Re: Grazvydas Ignotas
2008-11-03 12:59 ` [PATCH] serial: Flush posted write on 34xx to make 8250 work (Re: What happened to the serial console on BeagleBoard with 2.6.28-rc2?) Ming Lei
2008-11-03 16:45 ` Tony Lindgren
2008-11-03 16:54 ` Woodruff, Richard
2008-11-02 22:07 ` What happened to the serial console on BeagleBoard with 2.6.28-rc2? Tony Lindgren
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=20081102205019.GJ28924@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=felipe.contreras@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=nmonson@gmail.com \
--cc=rick@efn.org \
--cc=tom.leiming@gmail.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