From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Govindraj Raja <govindraj.r@ti.com>,
Kevin Hilman <khilman@ti.com>,
alan@linux.intel.com
Subject: Re: [PATCH 0/2] tty: serial: OMAP: work around broken driver, IP block
Date: Mon, 23 Jan 2012 10:15:22 +0200 [thread overview]
Message-ID: <1327306522.1916.11.camel@deskari> (raw)
In-Reply-To: <20120121071934.18707.64258.stgit@dusk>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
On Sat, 2012-01-21 at 00:27 -0700, Paul Walmsley wrote:
> [ 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.
Thanks, this makes the console usable on my OMAP3 overo.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: tomi.valkeinen@ti.com (Tomi Valkeinen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] tty: serial: OMAP: work around broken driver, IP block
Date: Mon, 23 Jan 2012 10:15:22 +0200 [thread overview]
Message-ID: <1327306522.1916.11.camel@deskari> (raw)
In-Reply-To: <20120121071934.18707.64258.stgit@dusk>
On Sat, 2012-01-21 at 00:27 -0700, Paul Walmsley wrote:
> [ 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.
Thanks, this makes the console usable on my OMAP3 overo.
Tomi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120123/8301390e/attachment.sig>
next prev parent reply other threads:[~2012-01-23 8:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 7:27 [PATCH 0/2] tty: serial: OMAP: work around broken driver, IP block Paul Walmsley
2012-01-21 7:27 ` Paul Walmsley
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-21 7:27 ` Paul Walmsley
2012-01-23 10:21 ` Govindraj
2012-01-23 10:21 ` Govindraj
2012-01-23 10:25 ` 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-21 7:27 ` Paul Walmsley
2012-01-23 8:50 ` Govindraj
2012-01-23 8:50 ` Govindraj
2012-01-23 9:49 ` Paul Walmsley
2012-01-23 9:49 ` Paul Walmsley
2012-01-23 9:50 ` Govindraj
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 12:55 ` Greg KH
2012-01-21 20:31 ` Paul Walmsley
2012-01-21 20:31 ` Paul Walmsley
2012-01-21 20:46 ` Alan Cox
2012-01-21 20:46 ` Alan Cox
2012-01-22 14:04 ` Paul Walmsley
2012-01-22 14:04 ` Paul Walmsley
2012-01-23 8:15 ` Tomi Valkeinen [this message]
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=1327306522.1916.11.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=alan@linux.intel.com \
--cc=govindraj.r@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.