From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [ARM] serial/pxa: work around Errata #75
Date: Fri, 6 Nov 2009 21:40:46 +0100 [thread overview]
Message-ID: <20091106204046.GA8952@pengutronix.de> (raw)
In-Reply-To: <1257245235-14783-1-git-send-email-u.kleine-koenig@pengutronix.de>
Hello,
[Added Greg to Cc:]
On Tue, Nov 03, 2009 at 11:47:15AM +0100, Uwe Kleine-K?nig wrote:
> Intel(R) PXA27x Processor Family Specification Update (Nov 2005)
> says:
>
> E75. UART: Baud rate may not be programmed correctly on
> back-to-back writes.
>
> Problem:
> When programming the Divisor Latch registers, Low and High (DLL and
> DLH), with back-to-back writes, the second register write may not
> take effect. The result is an incorrect baud rate.
>
> Workaround:
> After programming the first Divisor Latch register, read and verify
> it before programming the second Divisor Latch register.
>
> This was hit when changing the baud rate from 115200 to 9600 while
> receiving characters at 9600 Bd.
>
> And fixed indention of some comments nearby.
I havn't received any feed-back for this up to now.
Did I address the right people? Are you just burried in work?
Assuming the patch is OK, which is the right path into mainline?
Some patches touching drivers/serial/pxa.c went in via Russell's tree,
bdc04e3 (serial: move delta_msr_wait into the tty_port) went in via
gregkh/tty-2.6.
Greg: as you didn't get the original patch you can find it below.
Best regards
Uwe
next prev parent reply other threads:[~2009-11-06 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 10:47 [PATCH] [ARM] serial/pxa: work around Errata #75 Uwe Kleine-König
2009-11-06 20:40 ` Uwe Kleine-König [this message]
2009-11-07 9:45 ` Haojian Zhuang
2009-11-07 11:33 ` Uwe Kleine-König
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=20091106204046.GA8952@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).