From: Michael Walle <michael@walle.cc>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yangbo Lu <yangbo.lu@nxp.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH] mmc: sdhci-of-esdhc: set timeout to max before tuning
Date: Wed, 21 Oct 2020 19:29:47 +0200 [thread overview]
Message-ID: <63b574bbda356f93fe706301416195a7@walle.cc> (raw)
In-Reply-To: <CAPDyKFrLtYmPpVumSMr0TAqSWx8+vc2Hzhfw-14aiJudPw7xeA@mail.gmail.com>
Am 2020-10-21 17:04, schrieb Ulf Hansson:
> On Fri, 16 Oct 2020 at 14:50, Michael Walle <michael@walle.cc> wrote:
>>
>> Am 2020-10-16 12:53, schrieb Ulf Hansson:
>> > On Fri, 16 Oct 2020 at 01:12, Michael Walle <michael@walle.cc> wrote:
>> >>
>> >> On rare occations there is the following error:
>> >>
>> >> mmc0: Tuning timeout, falling back to fixed sampling clock
>> >>
>> >> There are SD cards which takes a significant longer time to reply to
>> >> the
>> >> first CMD19 command. The eSDHC takes the data timeout value into
>> >> account
>> >> during the tuning period. The SDHCI core doesn't explicitly set this
>> >> timeout for the tuning procedure. Thus on the slow cards, there might
>> >> be
>> >> a spurious "Buffer Read Ready" interrupt, which in turn triggers a
>> >> wrong
>> >> sequence of events. In the end this will lead to an unsuccessful
>> >> tuning
>> >> procedure and to the above error.
>> >>
>> >> To workaround this, set the timeout to the maximum value (which is the
>> >> best we can do) and the SDHCI core will take care of the proper
>> >> timeout
>> >> handling.
>> >>
>> >> Signed-off-by: Michael Walle <michael@walle.cc>
>> >
>> > Sound like this should be tagged for stable, right?
>>
>> Yes, but I was unsure about that. I didn't find a lot of Fixes: tags
>> in
>> the history of this driver (eg. for errata etc.)
>>
>> I could repost a v2 with a fixes tag if you like.
>
> If this is regression and you can point to a specific commit it fixes,
> then please yes!
That would be commit ba49cbd0936e ("mmc: sdhci-of-esdhc: add tuning
support"). But as of today it isn't much left of that original code.
So I don't know if adding that fixes tag will help a lot. Correct me
if I'm wrong.
-michael
prev parent reply other threads:[~2020-10-21 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 23:11 [PATCH] mmc: sdhci-of-esdhc: set timeout to max before tuning Michael Walle
2020-10-16 8:45 ` Adrian Hunter
2020-10-16 10:53 ` Ulf Hansson
2020-10-16 12:50 ` Michael Walle
2020-10-21 15:04 ` Ulf Hansson
2020-10-21 17:29 ` Michael Walle [this message]
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=63b574bbda356f93fe706301416195a7@walle.cc \
--to=michael@walle.cc \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=yangbo.lu@nxp.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