From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] tty: serial: OMAP: work around broken driver, IP block
Date: Sat, 21 Jan 2012 00:27:37 -0700 [thread overview]
Message-ID: <20120121071934.18707.64258.stgit@dusk> (raw)
[ This series is targeted for merging during v3.3-rc ]
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 a combination of a silicon bug in the UART IP
block and broken FIFO settings in the OMAP serial driver.
This patch series attempts to work around these problems. The workarounds
are not perfect; see the patch descriptions for more details.
Tested on OMAP3530 BeagleBoard. This series will need to be tested on
OMAP2 and OMAP4 before it is ready to merge.
- Paul
---
Paul Walmsley (2):
tty: serial: OMAP: ensure FIFO levels are set correctly in non-DMA mode
tty: serial: OMAP: transmit FIFO threshold interrupts don't wake the chip
arch/arm/plat-omap/include/plat/omap-serial.h | 1
drivers/tty/serial/omap-serial.c | 86 ++++++++++++++++++++++++-
2 files changed, 82 insertions(+), 5 deletions(-)
next reply other threads:[~2012-01-21 7:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 7:27 Paul Walmsley [this message]
2012-01-21 7:27 ` [PATCH 1/2] tty: serial: OMAP: ensure FIFO levels are set correctly in non-DMA mode Paul Walmsley
2012-01-23 10:21 ` Govindraj
2012-01-23 10:25 ` Govindraj
2012-01-21 7:27 ` [PATCH 2/2] tty: serial: OMAP: transmit FIFO threshold interrupts don't wake the chip Paul Walmsley
2012-01-23 8:50 ` Govindraj
2012-01-23 9:49 ` Paul Walmsley
2012-01-23 9:50 ` Govindraj
2012-01-21 12:55 ` [PATCH 0/2] tty: serial: OMAP: work around broken driver, IP block Greg KH
2012-01-21 20:31 ` Paul Walmsley
2012-01-21 20:46 ` Alan Cox
2012-01-22 14:04 ` Paul Walmsley
2012-01-23 8:15 ` Tomi Valkeinen
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=20120121071934.18707.64258.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).