All of lore.kernel.org
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/6] ARM: LPC32xx: serial.c: HW bug workaround
Date: Mon, 27 Feb 2012 16:37:03 +0100	[thread overview]
Message-ID: <4F4BA31F.8040201@antcom.de> (raw)
In-Reply-To: <20120227141430.GB3550@pengutronix.de>

Hi Kevin,

On 02/27/2012 03:14 PM, Wolfram Sang wrote:
> If you have a reference (errata ID or similar) it would be nice to
> have it in the comment and description.

Can you please help out with this one?

In the LPC32xx errata, there is a note about a similar HS UART issue,
but this one here (Standard UART) must be a different one (or it's a
bug and the fix is actually targeted at HS UART).

I actually just ported this code from lpclinux.com and assumed that
NXP knows best about LPC HW bugs. ;-)

Thanks in advance,

Roland

  reply	other threads:[~2012-02-27 15:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 15:35 [PATCH v2 0/6] ARM: LPC32xx: Patch set with further fixes for LPC32xx Roland Stigge
2012-02-25 15:35 ` [PATCH v2 1/6] ARM: LPC32xx: Fix irq on GPI_28 Roland Stigge
2012-02-25 15:35 ` [PATCH v2 2/6] ARM: LPC32xx: Fix missing and bad LPC32XX macros Roland Stigge
2012-02-25 15:35 ` [PATCH v2 3/6] ARM: LPC32xx: Fix interrupt controller init Roland Stigge
2012-02-25 15:35 ` [PATCH v2 4/6] ARM: LPC32xx: irq.c: Clear latched event Roland Stigge
2012-02-25 15:35 ` [PATCH v2 5/6] ARM: LPC32xx: serial.c: HW bug workaround Roland Stigge
2012-02-27 14:14   ` Wolfram Sang
2012-02-27 15:37     ` Roland Stigge [this message]
2012-02-27 15:48       ` Wolfram Sang
2012-02-27 19:02       ` Kevin Wells
2012-02-27 21:59         ` Roland Stigge
2012-02-25 15:35 ` [PATCH v2 6/6] ARM: LPC32xx: serial.c: Fixed loop limit Roland Stigge
2012-02-27 19:16 ` [PATCH v2 0/6] ARM: LPC32xx: Patch set with further fixes for LPC32xx Kevin Wells

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=4F4BA31F.8040201@antcom.de \
    --to=stigge@antcom.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 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.