From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753724AbdBHP6s (ORCPT <rfc822;w@1wt.eu>);
        Wed, 8 Feb 2017 10:58:48 -0500
Received: from foss.arm.com ([217.140.101.70]:51150 "EHLO foss.arm.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751748AbdBHP6q (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 8 Feb 2017 10:58:46 -0500
From: Marc Zyngier <marc.zyngier@arm.com>
To: Timur Tabi <timur@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
        Robin Murphy <robin.murphy@arm.com>,
        Christopher Covington <cov@codeaurora.org>,
        Jonathan Corbet <corbet@lwn.net>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will.deacon@arm.com>, linux-doc@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        shankerd@codeaurora.org,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Jiri Slaby <jslaby@suse.com>, Russell King <linux@armlinux.org.uk>,
        linux-serial@vger.kernel.org, Jon Masters <jcm@redhat.com>,
        Neil Leeder <nleeder@codeaurora.org>,
        Mark Langsdorf <mlangsdo@redhat.com>, Mark Salter <msalter@redhat.com>
Subject: Re: [PATCH 1/2] tty: pl011: Work around QDF2400 E44 stuck BUSY bit
In-Reply-To: <e16986de-31fa-8d34-05be-aa8a585500d4@codeaurora.org> (Timur
        Tabi's message of "Wed, 8 Feb 2017 08:09:12 -0600")
Organization: ARM Ltd
References: <20170208005736.18724-1-cov@codeaurora.org>
        <7151be59-000c-d50b-f8f5-5fef0c053d91@arm.com>
        <f9504cde-a87a-ba99-2f72-fc3029ef5fe5@codeaurora.org>
        <20170208133306.GE15459@leverpostej>
        <e16986de-31fa-8d34-05be-aa8a585500d4@codeaurora.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Date: Wed, 08 Feb 2017 15:35:27 +0000
Message-ID: <87lgtg7l1c.fsf@on-the-bus.cambridge.arm.com>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Feb 08 2017 at  2:09:12 pm GMT, Timur Tabi <timur@codeaurora.org> wrote:
> 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.

Interesting. How will you guarantee that nobody will ever want to run a
mainline kernel on this box after a certain date? Self-destruct timer?
;-)

As someone who runs mainline on HW that exceeded its "sell-by" date by a
few decades, I'm genuinely interested.

Thanks,

	M.
-- 
Jazz is not dead, it just smell funny.