From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934733AbdBQSXO (ORCPT ); Fri, 17 Feb 2017 13:23:14 -0500 Received: from foss.arm.com ([217.140.101.70]:58678 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934232AbdBQSXN (ORCPT ); Fri, 17 Feb 2017 13:23:13 -0500 Date: Fri, 17 Feb 2017 18:14:41 +0000 From: Will Deacon To: Christopher Covington Cc: Catalin Marinas , Jonathan Corbet , linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Greg Kroah-Hartman , Marc Zyngier , Russell King , Mark Rutland , Peter Hurley , Aleksey Makarov , Robin Murphy , Shanker Donthineni , Timur Tabi , Mark Langsdorf , Mark Salter , Jon Masters , Neil Leeder , Steve Ulrich Subject: Re: [PATCH] Documentation: Note QDF2400 SoC Erratum 44 Message-ID: <20170217181440.GP15431@arm.com> References: <20170215215407.25854-1-cov@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170215215407.25854-1-cov@codeaurora.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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 > Acked-by: Russell King > Acked-by: Mark Rutland > Acked-by: Timur Tabi > --- > 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