From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933229AbdBHPZ7 (ORCPT ); Wed, 8 Feb 2017 10:25:59 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:48540 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753221AbdBHPZy (ORCPT ); Wed, 8 Feb 2017 10:25:54 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 1386F608A5 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=timur@codeaurora.org Subject: Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit To: Mark Rutland Cc: Robin Murphy , Christopher Covington , Jonathan Corbet , Marc Zyngier , Catalin Marinas , Will Deacon , linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, shankerd@codeaurora.org, Greg Kroah-Hartman , Jiri Slaby , Russell King , linux-serial@vger.kernel.org, Jon Masters , Neil Leeder , Mark Langsdorf , Mark Salter References: <20170208005736.18724-1-cov@codeaurora.org> <7151be59-000c-d50b-f8f5-5fef0c053d91@arm.com> <20170208133306.GE15459@leverpostej> From: Timur Tabi Message-ID: Date: Wed, 8 Feb 2017 08:09:12 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 MIME-Version: 1.0 In-Reply-To: <20170208133306.GE15459@leverpostej> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mark Rutland wrote: >> No, only Kryo and Falkor V1 based SOCs have this problem. Falkor V2 >> will have this fixed. We intend to revert these fixes after Falkor >> V1 SOCs are no longer supported. > > Supported by whom? Qualcomm. > Generally, once something's upstreamed we expect it to remain supported. The V1 SOCs are technically pre-production, but still in wide use and it will be a while before they are all replaced by V2 SOCs. It's only because of the "ugliness" of the erratum and its work-around that we want to git rid of it when we can. Cov is better equipped to answer your other questions. -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Subject: Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit Date: Wed, 8 Feb 2017 08:09:12 -0600 Message-ID: References: <20170208005736.18724-1-cov@codeaurora.org> <7151be59-000c-d50b-f8f5-5fef0c053d91@arm.com> <20170208133306.GE15459@leverpostej> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170208133306.GE15459@leverpostej> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Mark Rutland Cc: Mark Salter , Mark Langsdorf , Jon Masters , Jonathan Corbet , Marc Zyngier , Catalin Marinas , Neil Leeder , linux-doc@vger.kernel.org, Will Deacon , linux-kernel@vger.kernel.org, Russell King , shankerd@codeaurora.org, Christopher Covington , linux-serial@vger.kernel.org, Greg Kroah-Hartman , Jiri Slaby , Robin Murphy , linux-arm-kernel@lists.infradead.org List-Id: linux-serial@vger.kernel.org Mark Rutland wrote: >> No, only Kryo and Falkor V1 based SOCs have this problem. Falkor V2 >> will have this fixed. We intend to revert these fixes after Falkor >> V1 SOCs are no longer supported. > > Supported by whom? Qualcomm. > Generally, once something's upstreamed we expect it to remain supported. The V1 SOCs are technically pre-production, but still in wide use and it will be a while before they are all replaced by V2 SOCs. It's only because of the "ugliness" of the erratum and its work-around that we want to git rid of it when we can. Cov is better equipped to answer your other questions. -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation. From mboxrd@z Thu Jan 1 00:00:00 1970 From: timur@codeaurora.org (Timur Tabi) Date: Wed, 8 Feb 2017 08:09:12 -0600 Subject: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit In-Reply-To: <20170208133306.GE15459@leverpostej> References: <20170208005736.18724-1-cov@codeaurora.org> <7151be59-000c-d50b-f8f5-5fef0c053d91@arm.com> <20170208133306.GE15459@leverpostej> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Mark Rutland wrote: >> No, only Kryo and Falkor V1 based SOCs have this problem. Falkor V2 >> will have this fixed. We intend to revert these fixes after Falkor >> V1 SOCs are no longer supported. > > Supported by whom? Qualcomm. > Generally, once something's upstreamed we expect it to remain supported. The V1 SOCs are technically pre-production, but still in wide use and it will be a while before they are all replaced by V2 SOCs. It's only because of the "ugliness" of the erratum and its work-around that we want to git rid of it when we can. Cov is better equipped to answer your other questions. -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation.