linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
	Jean-Francois Dagenais <jeff.dagenais@gmail.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH v2] mmc: sdhci: make sure SDHCI_CLOCK_CARD_EN bit sticks
Date: Thu, 5 Mar 2020 09:35:01 +0200	[thread overview]
Message-ID: <a3ab359b-3f5a-90fb-a7d2-5e946c434713@intel.com> (raw)
In-Reply-To: <CAPDyKFr41yuESMuoKF_KUSW4sP_cZxzjW4gKMv_0ShtoEOmS3A@mail.gmail.com>

On 4/03/20 5:34 pm, Ulf Hansson wrote:
> On Wed, 19 Feb 2020 at 22:07, Jean-Francois Dagenais
> <jeff.dagenais@gmail.com> wrote:
>>
>> Regardless of the broken-cd quirk, when it silently doesn't stick,
>> no clock is applied to the bus lines, yet the code continues to
>> try to make CMDs and times out after 10 seconds for each. This
>> process can take up to a minute as mmc_rescan_try_freq tries the
>> different commands to discover the card.
>>
>> Short of changing sdhci_enable_clk's signature chain in all
>> dependent drivers, at least provide a hint that this might be the
>> problem. This will save tons of time for system integrators.
>>
>> Signed-off-by: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
> 
> The change looks reasonable to me. However I would like to get an ack
> by Adrian before applying, as I may not have thought of all the
> consequences this change may have.
> 
> Kind regards
> Uffe
> 
> 
>> ---
>> Changes in v2:
>>  * removed redundant wmb()
>> ---
>>  drivers/mmc/host/sdhci.c | 14 ++++++++++++++
>>  1 file changed, 14 insertions(+)
>>
>> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
>> index 63db84481dff..42a02d034fda 100644
>> --- a/drivers/mmc/host/sdhci.c
>> +++ b/drivers/mmc/host/sdhci.c
>> @@ -1894,6 +1894,20 @@ void sdhci_enable_clk(struct sdhci_host *host, u16 clk)
>>
>>         clk |= SDHCI_CLOCK_CARD_EN;
>>         sdhci_writew(host, clk, SDHCI_CLOCK_CONTROL);
>> +
>> +       clk = sdhci_readw(host, SDHCI_CLOCK_CONTROL);
>> +       if (clk & SDHCI_CLOCK_CARD_EN)
>> +               return;
>> +
>> +       /* The controller will clear this bit if card absent condition is

Please make the comment style consistent with the rest of sdhci.c e.g.

	/*
	 * The controller blah...
	 * blah ...
	 */

>> +        * detected. If card is indeed present, check platform configuration for
>> +        * how CD is reported to the SDHCI host controller. There may be an
>> +        * "assume present" mechanism in the platform registers, or your pin mux
>> +        * may be incorrect.
>> +        */
>> +       pr_err("%s: SDHCI_CLOCK_CARD_EN bit did not stick. Card absent?\n",
>> +               mmc_hostname(host->mmc));
>> +       sdhci_dumpregs(host);

The error message is ok, but for some controllers this could happen normally
if the card is removed suddenly, so let's not also do a register dump.

>>  }
>>  EXPORT_SYMBOL_GPL(sdhci_enable_clk);
>>
>> --
>> 2.25.0
>>

      reply	other threads:[~2020-03-05  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 21:07 [PATCH v2] mmc: sdhci: make sure SDHCI_CLOCK_CARD_EN bit sticks Jean-Francois Dagenais
2020-03-04 15:34 ` Ulf Hansson
2020-03-05  7:35   ` Adrian Hunter [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=a3ab359b-3f5a-90fb-a7d2-5e946c434713@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=jeff.dagenais@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).