From: Adrian Hunter <adrian.hunter@intel.com>
To: Sarthak Garg <quic_sartgarg@quicinc.com>, ulf.hansson@linaro.org
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, quic_kamasali@quicinc.com,
quic_rampraka@quicinc.com, quic_pragalla@quicinc.com,
quic_sayalil@quicinc.com, "Jens Axboe" <axboe@kernel.dk>,
"Avri Altman" <Avri.Altman@wdc.com>,
"Chaitanya Kulkarni" <kch@nvidia.com>,
"Christian Löhle" <CLoehle@hyperstone.com>,
"Bean Huo" <beanhuo@micron.com>,
"Vincent Whitchurch" <vincent.whitchurch@axis.com>,
"Dmitry Osipenko" <digetx@gmail.com>,
"Stephen Boyd" <swboyd@chromium.org>
Subject: Re: [PATCH V1 1/2] mmc: core: Introduce new flag to force hardware reset
Date: Fri, 3 Jun 2022 08:33:46 +0300 [thread overview]
Message-ID: <bbcd824b-457a-1009-835d-3e51ed04c1c2@intel.com> (raw)
In-Reply-To: <20220603051534.22672-2-quic_sartgarg@quicinc.com>
On 3/06/22 08:15, Sarthak Garg wrote:
> Introduce new flag cqe_recovery_reset_always to allow vendors to force
> hardware reset during cqe recovery.
>
> Signed-off-by: Sarthak Garg <quic_sartgarg@quicinc.com>
You should re-base on top of "mmc: block: Fix CQE recovery reset success"
Also you may want to consider fixes / stable tags.
Otherwise, for both patches:
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
> drivers/mmc/core/block.c | 2 +-
> include/linux/mmc/host.h | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/core/block.c b/drivers/mmc/core/block.c
> index 1259ca22d625..496cdd8a2999 100644
> --- a/drivers/mmc/core/block.c
> +++ b/drivers/mmc/core/block.c
> @@ -1497,7 +1497,7 @@ void mmc_blk_cqe_recovery(struct mmc_queue *mq)
> pr_debug("%s: CQE recovery start\n", mmc_hostname(host));
>
> err = mmc_cqe_recovery(host);
> - if (err)
> + if (err || host->cqe_recovery_reset_always)
> mmc_blk_reset(mq->blkdata, host, MMC_BLK_CQE_RECOVERY);
> else
> mmc_blk_reset_success(mq->blkdata, MMC_BLK_CQE_RECOVERY);
> diff --git a/include/linux/mmc/host.h b/include/linux/mmc/host.h
> index c193c50ccd78..3e2fe950b4ec 100644
> --- a/include/linux/mmc/host.h
> +++ b/include/linux/mmc/host.h
> @@ -492,6 +492,7 @@ struct mmc_host {
> int cqe_qdepth;
> bool cqe_enabled;
> bool cqe_on;
> + bool cqe_recovery_reset_always;
>
> /* Inline encryption support */
> #ifdef CONFIG_MMC_CRYPTO
next prev parent reply other threads:[~2022-06-03 5:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 5:15 [PATCH V1 0/2] Introduce new flag to force hardware reset Sarthak Garg
2022-06-03 5:15 ` [PATCH V1 1/2] mmc: core: " Sarthak Garg
2022-06-03 5:33 ` Adrian Hunter [this message]
2025-05-14 10:48 ` Sarthak Garg
2022-06-03 5:15 ` [PATCH V1 2/2] mmc: sdhci-msm: Enable force hw reset during cqe recovery Sarthak Garg
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=bbcd824b-457a-1009-835d-3e51ed04c1c2@intel.com \
--to=adrian.hunter@intel.com \
--cc=Avri.Altman@wdc.com \
--cc=CLoehle@hyperstone.com \
--cc=axboe@kernel.dk \
--cc=beanhuo@micron.com \
--cc=digetx@gmail.com \
--cc=kch@nvidia.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=quic_kamasali@quicinc.com \
--cc=quic_pragalla@quicinc.com \
--cc=quic_rampraka@quicinc.com \
--cc=quic_sartgarg@quicinc.com \
--cc=quic_sayalil@quicinc.com \
--cc=swboyd@chromium.org \
--cc=ulf.hansson@linaro.org \
--cc=vincent.whitchurch@axis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox