From: Yann GAUTIER <yann.gautier@foss.st.com>
To: Marek Vasut <marex@denx.de>, <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>
Subject: Re: [PATCH 1/2] mmc: mmci: enable MMC_CAP_NEED_RSP_BUSY
Date: Thu, 4 Feb 2021 13:54:57 +0100 [thread overview]
Message-ID: <9fbd2fca-e4f5-d28f-74de-d9906cc232bf@foss.st.com> (raw)
In-Reply-To: <0ac77e8d-9400-abc8-f963-943e9cba94db@denx.de>
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.
Regards,
Yann
[1]
https://patchwork.kernel.org/project/linux-mmc/cover/20200310153340.5593-1-ulf.hansson@linaro.org/
[2]
https://patchwork.kernel.org/project/linux-mmc/patch/20200508112853.23525-1-ulf.hansson@linaro.org/
next prev parent reply other threads:[~2021-02-04 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 12:05 [PATCH 0/2] mmc: mmci/mmc_test: update mmc_erase management yann.gautier
2021-02-04 12:05 ` [PATCH 1/2] mmc: mmci: enable MMC_CAP_NEED_RSP_BUSY yann.gautier
2021-02-04 12:26 ` Marek Vasut
2021-02-04 12:54 ` Yann GAUTIER [this message]
2021-02-04 13:07 ` Marek Vasut
2021-02-05 9:53 ` Ulf Hansson
2021-02-05 12:19 ` Yann GAUTIER
2021-02-08 12:16 ` Yann GAUTIER
2021-02-08 13:31 ` Yann GAUTIER
2021-02-08 15:03 ` Ulf Hansson
2021-02-09 14:01 ` Yann Gautier
2021-02-10 12:03 ` Ulf Hansson
2021-02-04 12:05 ` [PATCH 2/2] mmc: mmc_test: use erase_arg for mmc_erase command yann.gautier
2021-02-05 6:33 ` Adrian Hunter
2021-02-05 9:05 ` Yann GAUTIER
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9fbd2fca-e4f5-d28f-74de-d9906cc232bf@foss.st.com \
--to=yann.gautier@foss.st.com \
--cc=adrian.hunter@intel.com \
--cc=huyue2@yulong.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ludovic.barre@foss.st.com \
--cc=marex@denx.de \
--cc=p.zabel@pengutronix.de \
--cc=per.forlin@linaro.org \
--cc=swboyd@chromium.org \
--cc=ulf.hansson@linaro.org \
--cc=vbadigan@codeaurora.org \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.