Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH 1/2] mmc: mmci: enable MMC_CAP_NEED_RSP_BUSY
To:     Yann GAUTIER <yann.gautier@foss.st.com>, ulf.hansson@linaro.org
Cc:     linux@armlinux.org.uk, linus.walleij@linaro.org,
        ludovic.barre@foss.st.com, per.forlin@linaro.org,
        huyue2@yulong.com, wsa+renesas@sang-engineering.com,
        vbadigan@codeaurora.org, adrian.hunter@intel.com,
        p.zabel@pengutronix.de, swboyd@chromium.org,
        linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
References: <20210204120547.15381-1-yann.gautier@foss.st.com>
 <20210204120547.15381-2-yann.gautier@foss.st.com>
 <0ac77e8d-9400-abc8-f963-943e9cba94db@denx.de>
 <9fbd2fca-e4f5-d28f-74de-d9906cc232bf@foss.st.com>
From:   Marek Vasut <marex@denx.de>
Message-ID: <50d92d9a-b42e-b313-a0c7-ff0848a3c673@denx.de>
Date:   Thu, 4 Feb 2021 14:07:20 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <9fbd2fca-e4f5-d28f-74de-d9906cc232bf@foss.st.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 2/4/21 1:54 PM, Yann GAUTIER wrote:
> On 2/4/21 1:26 PM, Marek Vasut wrote:
>> On 2/4/21 1:05 PM, yann.gautier@foss.st.com wrote:
>>> From: Yann Gautier <yann.gautier@foss.st.com>
>>>
>>> To properly manage commands awaiting R1B responses, the capability
>>> MMC_CAP_NEED_RSP_BUSY is enabled in mmci driver, for variants that
>>> manage busy detection.
>>> This R1B management needs both the flags MMC_CAP_NEED_RSP_BUSY and
>>> MMC_CAP_WAIT_WHILE_BUSY to be enabled together.
>>>
>> Shouldn't this have Fixes: tag ?
> 
> Hi Marek,
> 
> There is no unique patch that brought the issue, but a combination of 
> several things:
> - The series that brought the MMC_CAP_NEED_RSP_BUSY flag [1]
> - The series that enabled MMC_ERASE for all hosts [2] (removal of 
> MMC_CAP_ERASE)
> 
> But you're right, this patch may go on v5.8.x kernel and newer versions.

I think there will be quite some interest in 5.10.y LTS on the MP1 from 
the various industrial/embedded users, so it would be nice to have that 
5.10.y well maintained with necessary backports / fixes :)