From: Jean Rene Dawin <jdawin@math.uni-bielefeld.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "H . Nikolaus Schaller" <hns@goldelico.com>,
Huijin Park <huijin.park@samsung.com>,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: core: Restore (almost) the busy polling for MMC_SEND_OP_COND
Date: Wed, 4 May 2022 07:46:52 +0200 [thread overview]
Message-ID: <20220504054652.GA7851@math.uni-bielefeld.de> (raw)
In-Reply-To: <CAPDyKFr1PzSaiKqB4ZoqTS_8bGsEH=aB3ARhxyGu+cYeRqeBew@mail.gmail.com>
Ulf Hansson wrote on Mon 7/03/22 13:17:
> On Fri, 4 Mar 2022 at 11:57, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> >
> > Commit 76bfc7ccc2fa ("mmc: core: adjust polling interval for CMD1"),
> > significantly decreased the polling period from ~10-12ms into just a couple
> > of us. The purpose was to decrease the total time spent in the busy polling
> > loop, but unfortunate it has lead to problems, that causes eMMC cards to
> > never gets out busy and thus fails to be initialized.
> >
> > To fix the problem, but also to try to keep some of the new improved
> > behaviour, let's start by using a polling period of 1-2ms, which then
> > increases for each loop, according to common polling loop in
> > __mmc_poll_for_busy().
> >
> > Reported-by: Jean Rene Dawin <jdawin@math.uni-bielefeld.de>
> > Reported-by: H. Nikolaus Schaller <hns@goldelico.com>
> > Cc: Huijin Park <huijin.park@samsung.com>
> > Fixes: 76bfc7ccc2fa ("mmc: core: adjust polling interval for CMD1")
> > Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
> > ---
> >
> > Jean Rene and H. Nikolaus, if this doesn't work, please try extending the
> > the MMC_OP_COND_PERIOD_US a bit, to so see if we can find a value that always
> > works.
> >
> > Kind regards
> > Uffe
>
> Applied for fixes and by adding two tested-by tags from you, thanks!
>
> Kind regards
> Uffe
Hi,
with the current value of MMC_OP_COND_PERIOD_US = 1ms I still see
mmc1: Card stuck being busy! __mmc_poll_for_busy
mmc1: error -110 doing runtime resume
regularly. The same with 2ms. Setting it to 4ms makes the messages go
away. Would it be ok to increase MMC_OP_COND_PERIOD_US to 4ms?
---
drivers/mmc/core/mmc_ops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/core/mmc_ops.c b/drivers/mmc/core/mmc_ops.c
index 180d7e9d3400..1fd57f342842 100644
--- a/drivers/mmc/core/mmc_ops.c
+++ b/drivers/mmc/core/mmc_ops.c
@@ -21,7 +21,7 @@
#define MMC_BKOPS_TIMEOUT_MS (120 * 1000) /* 120s */
#define MMC_SANITIZE_TIMEOUT_MS (240 * 1000) /* 240s */
-#define MMC_OP_COND_PERIOD_US (1 * 1000) /* 1ms */
+#define MMC_OP_COND_PERIOD_US (4 * 1000) /* 1ms */
#define MMC_OP_COND_TIMEOUT_MS 1000 /* 1s */
static const u8 tuning_blk_pattern_4bit[] = {
--
2.35.1
Regards,
Jean Rene
next prev parent reply other threads:[~2022-05-04 5:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 10:56 [PATCH] mmc: core: Restore (almost) the busy polling for MMC_SEND_OP_COND Ulf Hansson
2022-03-04 14:38 ` H. Nikolaus Schaller
2022-03-04 16:05 ` Jean Rene Dawin
2022-03-07 12:17 ` Ulf Hansson
2022-05-04 5:46 ` Jean Rene Dawin [this message]
2022-05-04 9:08 ` Ulf Hansson
2022-05-05 7:17 ` Jean Rene Dawin
2022-05-11 6:46 ` Jean Rene Dawin
2022-05-13 20:06 ` 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=20220504054652.GA7851@math.uni-bielefeld.de \
--to=jdawin@math.uni-bielefeld.de \
--cc=hns@goldelico.com \
--cc=huijin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox