All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Documentation: Note QDF2400 SoC Erratum 44
Date: Fri, 17 Feb 2017 18:14:41 +0000	[thread overview]
Message-ID: <20170217181440.GP15431@arm.com> (raw)
In-Reply-To: <20170215215407.25854-1-cov@codeaurora.org>

On Wed, Feb 15, 2017 at 04:54:07PM -0500, Christopher Covington wrote:
> The Qualcomm Datacenter Technologies QDF2400 family of SoCs contains a
> custom (non-PrimeCell) implementation of the SBSA UART. Occasionally the
> BUSY bit in the Flag Register gets stuck as 1, erratum 44 for both 2432v1
> and 2400v1 SoCs.Checking that the Transmit FIFO Empty (TXFE) bit is 0,
> instead of checking that the BUSY bit is 1, works around the issue. Note
> this in the customary location. To minimize conflicts, this documentation
> update is separate from the code changes, "tty: pl011: Work around QDF2400
> E44 stuck BUSY bit".
> 
> Signed-off-by: Christopher Covington <cov@codeaurora.org>
> Acked-by: Russell King <rmk+kernel@armlinux.org.uk>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
> Acked-by: Timur Tabi <timur@codeaurora.org>
> ---
> Documentation to go with https://patchwork.kernel.org/patch/9575103/

Please poke me when that goes into -next. I don't want to merge the doc
until the patch is queued too.

Thanks,

Will

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Christopher Covington <cov@codeaurora.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Mark Rutland <mark.rutland@arm.com>,
	Peter Hurley <peter@hurleysoftware.com>,
	Aleksey Makarov <aleksey.makarov@linaro.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Shanker Donthineni <shankerd@codeaurora.org>,
	Timur Tabi <timur@codeaurora.org>,
	Mark Langsdorf <mlangsdo@redhat.com>,
	Mark Salter <msalter@redhat.com>, Jon Masters <jcm@redhat.com>,
	Neil Leeder <nleeder@codeaurora.org>,
	Steve Ulrich <sulrich@codeaurora.org>
Subject: Re: [PATCH] Documentation: Note QDF2400 SoC Erratum 44
Date: Fri, 17 Feb 2017 18:14:41 +0000	[thread overview]
Message-ID: <20170217181440.GP15431@arm.com> (raw)
In-Reply-To: <20170215215407.25854-1-cov@codeaurora.org>

On Wed, Feb 15, 2017 at 04:54:07PM -0500, Christopher Covington wrote:
> The Qualcomm Datacenter Technologies QDF2400 family of SoCs contains a
> custom (non-PrimeCell) implementation of the SBSA UART. Occasionally the
> BUSY bit in the Flag Register gets stuck as 1, erratum 44 for both 2432v1
> and 2400v1 SoCs.Checking that the Transmit FIFO Empty (TXFE) bit is 0,
> instead of checking that the BUSY bit is 1, works around the issue. Note
> this in the customary location. To minimize conflicts, this documentation
> update is separate from the code changes, "tty: pl011: Work around QDF2400
> E44 stuck BUSY bit".
> 
> Signed-off-by: Christopher Covington <cov@codeaurora.org>
> Acked-by: Russell King <rmk+kernel@armlinux.org.uk>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
> Acked-by: Timur Tabi <timur@codeaurora.org>
> ---
> Documentation to go with https://patchwork.kernel.org/patch/9575103/

Please poke me when that goes into -next. I don't want to merge the doc
until the patch is queued too.

Thanks,

Will

  reply	other threads:[~2017-02-17 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 21:54 [PATCH] Documentation: Note QDF2400 SoC Erratum 44 Christopher Covington
2017-02-15 21:54 ` Christopher Covington
2017-02-17 18:14 ` Will Deacon [this message]
2017-02-17 18:14   ` Will Deacon

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=20170217181440.GP15431@arm.com \
    --to=will.deacon@arm.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 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.