From: Adrian Hunter <adrian.hunter@intel.com>
To: Chaotian Jing <chaotian.jing@mediatek.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Johan Rudholm <johan.rudholm@axis.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Shawn Lin <shawn.lin@rock-chips.com>,
Andrew Gabbasov <andrew_gabbasov@mentor.com>,
David Jander <david@protonic.nl>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, srv_heupstream@mediatek.com,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH] mmc: core: fix dead loop of mmc_retune
Date: Wed, 30 Sep 2015 15:01:31 +0300 [thread overview]
Message-ID: <560BCF1B.7050302@intel.com> (raw)
In-Reply-To: <1443605838-5948-1-git-send-email-chaotian.jing@mediatek.com>
On 30/09/15 12:37, Chaotian Jing wrote:
> When get a CRC error, start the mmc_retune, it will issue CMD19/CMD21
> to do tune, assume there were 10 clock phase need to try, phase 0 to
> phase 6 is ok, phase 7 to phase 9 is NG, we try it from 0 to 9, so
> the last CMD19/CMD21 will get CRC error, host->need_retune was set and
> cause mmc_retune was called, then dead loop of mmc_retune
>
> Signed-off-by: Chaotian Jing <chaotian.jing@mediatek.com>
Wasn't my idea to have this CRC checking in the core ;-) and sdhci
doesn't put it's tuning commands through a mmc request so it doesn't
see this issue.
But definitely the CRC logic is not meant for the tuning commands, so
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
> drivers/mmc/core/core.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> index 0520064..a3eb20b 100644
> --- a/drivers/mmc/core/core.c
> +++ b/drivers/mmc/core/core.c
> @@ -134,9 +134,11 @@ void mmc_request_done(struct mmc_host *host, struct mmc_request *mrq)
> int err = cmd->error;
>
> /* Flag re-tuning needed on CRC errors */
> - if (err == -EILSEQ || (mrq->sbc && mrq->sbc->error == -EILSEQ) ||
> + if ((cmd->opcode != MMC_SEND_TUNING_BLOCK &&
> + cmd->opcode != MMC_SEND_TUNING_BLOCK_HS200) &&
> + (err == -EILSEQ || (mrq->sbc && mrq->sbc->error == -EILSEQ) ||
> (mrq->data && mrq->data->error == -EILSEQ) ||
> - (mrq->stop && mrq->stop->error == -EILSEQ))
> + (mrq->stop && mrq->stop->error == -EILSEQ)))
> mmc_retune_needed(host);
>
> if (err && cmd->retries && mmc_host_is_spi(host)) {
>
WARNING: multiple messages have this Message-ID (diff)
From: adrian.hunter@intel.com (Adrian Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: core: fix dead loop of mmc_retune
Date: Wed, 30 Sep 2015 15:01:31 +0300 [thread overview]
Message-ID: <560BCF1B.7050302@intel.com> (raw)
In-Reply-To: <1443605838-5948-1-git-send-email-chaotian.jing@mediatek.com>
On 30/09/15 12:37, Chaotian Jing wrote:
> When get a CRC error, start the mmc_retune, it will issue CMD19/CMD21
> to do tune, assume there were 10 clock phase need to try, phase 0 to
> phase 6 is ok, phase 7 to phase 9 is NG, we try it from 0 to 9, so
> the last CMD19/CMD21 will get CRC error, host->need_retune was set and
> cause mmc_retune was called, then dead loop of mmc_retune
>
> Signed-off-by: Chaotian Jing <chaotian.jing@mediatek.com>
Wasn't my idea to have this CRC checking in the core ;-) and sdhci
doesn't put it's tuning commands through a mmc request so it doesn't
see this issue.
But definitely the CRC logic is not meant for the tuning commands, so
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
> ---
> drivers/mmc/core/core.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> index 0520064..a3eb20b 100644
> --- a/drivers/mmc/core/core.c
> +++ b/drivers/mmc/core/core.c
> @@ -134,9 +134,11 @@ void mmc_request_done(struct mmc_host *host, struct mmc_request *mrq)
> int err = cmd->error;
>
> /* Flag re-tuning needed on CRC errors */
> - if (err == -EILSEQ || (mrq->sbc && mrq->sbc->error == -EILSEQ) ||
> + if ((cmd->opcode != MMC_SEND_TUNING_BLOCK &&
> + cmd->opcode != MMC_SEND_TUNING_BLOCK_HS200) &&
> + (err == -EILSEQ || (mrq->sbc && mrq->sbc->error == -EILSEQ) ||
> (mrq->data && mrq->data->error == -EILSEQ) ||
> - (mrq->stop && mrq->stop->error == -EILSEQ))
> + (mrq->stop && mrq->stop->error == -EILSEQ)))
> mmc_retune_needed(host);
>
> if (err && cmd->retries && mmc_host_is_spi(host)) {
>
next prev parent reply other threads:[~2015-09-30 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 9:37 [PATCH] mmc: core: fix dead loop of mmc_retune Chaotian Jing
2015-09-30 9:37 ` Chaotian Jing
2015-09-30 9:37 ` Chaotian Jing
2015-09-30 12:01 ` Adrian Hunter [this message]
2015-09-30 12:01 ` Adrian Hunter
2015-09-30 12:47 ` Ulf Hansson
2015-09-30 12:47 ` Ulf Hansson
2015-09-30 13:03 ` Ulf Hansson
2015-09-30 13:03 ` Ulf Hansson
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=560BCF1B.7050302@intel.com \
--to=adrian.hunter@intel.com \
--cc=andrew_gabbasov@mentor.com \
--cc=chaotian.jing@mediatek.com \
--cc=david@protonic.nl \
--cc=javier.martinez@collabora.co.uk \
--cc=johan.rudholm@axis.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.lin@rock-chips.com \
--cc=srv_heupstream@mediatek.com \
--cc=ulf.hansson@linaro.org \
/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.