From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] tty: serial: OMAP: work around broken IP block, driver
Date: Wed, 25 Jan 2012 19:50:32 -0700 [thread overview]
Message-ID: <20120126024903.31613.24730.stgit@dusk> (raw)
[ This series is targeted for merging during v3.3-rc ]
Hi
Here's an updated version of OMAP serial bugfix series against v3.3-rc1.
This revision has:
- reduced TX path interrupts by 5x compared to the first version
- a fix for the power management regression in v3.3-rc1 caused by the
bogus wakeup latency computation
- left the the TX FIFO threshold unchanged - this is left for a 3.4 patch
series
- improved commit messages
This series is also available via git in git://git.pwsan.com/linux-2.6
in the branch "omap_serial_fixes_3.3rc".
...
On v3.3-rc1, the OMAP serial console doesn't behave properly when
power management is enabled (the default with omap2plus_defconfig).
This seems to be due to one or more silicon bugs in the UART IP block
and a bug in the OMAP serial driver.
This patch series works around these problems. It's been tested under
the following conditions:
On 35xx Beagleboard
- in PIO mode
- with CPUidle enabled
- with off-mode disabled
- with off-mode enabled
- with CPUidle disabled
- with off-mode disabled
- with off-mode enabled
- in DMA mode
- with CPUidle enabled
- with off-mode disabled
- with off-mode enabled
- with CPUidle disabled
- with off-mode disabled
- with off-mode enabled
On N800 (242x)
- in PIO mode
- with CPUidle disabled
On 4430 ES2 Pandaboard
- in PIO mode
- with CPUidle disabled
- in DMA mode
- with CPUidle disabled
- Paul
---
omap_serial_fixes_3.3rc
text data bss dec hex filename
6592293 678588 5590684 12861565 c4407d vmlinux.orig
6592429 678588 5590684 12861701 c44105 vmlinux.patched
Paul Walmsley (3):
tty: serial: OMAP: use a 1-byte RX FIFO threshold in PIO mode
tty: serial: OMAP: block idle while the UART is transferring data in PIO mode
tty: serial: omap-serial: wakeup latency constraint is in microseconds, not milliseconds
arch/arm/mach-omap2/serial.c | 8 ++++----
drivers/tty/serial/omap-serial.c | 30 +++++++++++++++++++++++++-----
2 files changed, 29 insertions(+), 9 deletions(-)
next reply other threads:[~2012-01-26 2:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 2:50 Paul Walmsley [this message]
2012-01-26 2:50 ` [PATCH v2 1/3] tty: serial: OMAP: use a 1-byte RX FIFO threshold in PIO mode Paul Walmsley
2012-01-26 2:50 ` [PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data " Paul Walmsley
2012-01-26 2:58 ` Paul Walmsley
2012-01-27 7:23 ` Govindraj
2012-02-20 12:35 ` Cousson, Benoit
2012-02-21 22:02 ` Paul Walmsley
2012-02-24 14:35 ` Cousson, Benoit
2012-02-28 17:13 ` Paul Walmsley
2012-02-28 17:22 ` [PATCH] tty: serial: OMAP: Fix oops due to NULL pdata in DT boot Cousson, Benoit
2012-02-28 17:28 ` Greg KH
2012-02-28 18:23 ` Kevin Hilman
2012-01-26 2:50 ` [PATCH v2 3/3] tty: serial: omap-serial: wakeup latency constraint is in microseconds, not milliseconds Paul Walmsley
2012-01-27 7:19 ` Govindraj
2012-01-30 19:13 ` [PATCH v2 0/3] tty: serial: OMAP: work around broken IP block, driver Kevin Hilman
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=20120126024903.31613.24730.stgit@dusk \
--to=paul@pwsan.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).