[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <81be9ca0-5c61-6e94-8398-85354764b429@nvidia.com>
Date: Fri, 24 Apr 2020 19:42:16 -0700
From: Sowjanya Komatineni <skomatineni@...dia.com>
To: Sasha Levin <sashal@...nel.org>
CC: <adrian.hunter@...el.com>, <ulf.hansson@...aro.org>,
<baolin.wang@...aro.org>, <kstewart@...uxfoundation.org>,
<tglx@...utronix.de>, <bradleybolen@...il.com>,
<gregkh@...uxfoundation.org>, <thierry.reding@...il.com>,
<jonathanh@...dia.com>, <anrao@...dia.com>,
<linux-tegra@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-mmc@...r.kernel.org>, <stable@...r.kernel.org>
Subject: Re: [PATCH 5.4.33 0/2] Fix for long operation cmds busy detection
On 4/24/20 6:45 PM, Sasha Levin wrote:
> External email: Use caution opening links or attachments
>
>
> On Fri, Apr 24, 2020 at 01:06:04PM -0700, Sowjanya Komatineni wrote:
>> This series is to backport the upstream patches that fixes busy
>> detection
>> for long operation mmc commands by implementing Tegra specific timeout
>> callback to switch between finite and infinite HW busy detection wait
>> modes.
>>
>>
>> Sowjanya Komatineni (2):
>> sdhci: tegra: Implement Tegra specific set_timeout callback
>> sdhci: tegra: Enable MMC_CAP_WAIT_WHILE_BUSY host capability
>
> What regression do these patches fix?
>
This isn't a regression as we don't have any known failures as of today
with the specific mmc devices we are using on our platforms.
But this patch fixes a long outstanding bug for sdhci-tegra to handle
long busy wait for mmc command operations that may take longer than host
max busy timeout. So, this is something that's missing from the
beginning and good to have.
> --
> Thanks,
> Sasha
Powered by blists - more mailing lists