public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Zhoujie Wu <zjwu@marvell.com>,
	ulf.hansson@linaro.org, linux-mmc@vger.kernel.org
Cc: nadavh@marvell.com, xigu@marvell.com, xswang@marvell.com,
	dingwei@marvell.com, kostap@marvell.com, hannah@marvell.com,
	hongd@marvell.com, dougj@marvell.com, ygao@marvell.com,
	liuw@marvell.com, gregory.clement@free-electrons.com,
	thomas.petazzoni@free-electrons.com
Subject: Re: [PATCH v3] mmc: sdhci: wait 5ms after set 1.8V signal enable
Date: Mon, 18 Dec 2017 15:19:14 +0200	[thread overview]
Message-ID: <472f0d18-e529-2477-4809-079a5970a362@intel.com> (raw)
In-Reply-To: <1513366136-20302-1-git-send-email-zjwu@marvell.com>

On 15/12/17 21:28, Zhoujie Wu wrote:
> According to SD spec 3.00 3.6.1 signal voltage switch
> procedure step 6~8,
> (6) Set 1.8V Signal Enable in the Host Control 2 register.
> (7) Wait 5ms. 1.8V voltage regulator shall be stable within this period.
> (8) If 1.8V Signal Enable is cleared by Host Controller, go to step (12).
> 
> Host should wait 5ms after set 1.8V signal enable bit in
> Host Control 2 register and check if 1.8V is stable or not.
> 
> But current code checks if this bit is cleared by controller
> right after set it. On some platforms found the bit is not
> cleared right away and host reports "1.8V regulator output
> did not became stable" and 5ms delay can help.

The check is for the bit set not cleared.

> 
> Follow the spec and add 5ms delay to make sure the 1.8V Signal Enable
> bit is cleared.
> 
> Signed-off-by: Zhoujie Wu <zjwu@marvell.com>
> ---
>  drivers/mmc/host/sdhci.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
> index e9290a3..fe5f208 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -1933,6 +1933,9 @@ int sdhci_start_signal_voltage_switch(struct mmc_host *mmc,
>  		if (host->ops->voltage_switch)
>  			host->ops->voltage_switch(host);
>  
> +		/* Wait for 5ms */
> +		usleep_range(5000, 5500);

We have managed without this delay for a while and I am reluctant to add
delays that might anyway be specific to the controller.  What do you think
about implementing ->voltage_switch() and putting the delay there?

> +
>  		/* 1.8V regulator output should be stable within 5 ms */
>  		ctrl = sdhci_readw(host, SDHCI_HOST_CONTROL2);
>  		if (ctrl & SDHCI_CTRL_VDD_180)
> 


  reply	other threads:[~2017-12-18 13:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 19:28 [PATCH v3] mmc: sdhci: wait 5ms after set 1.8V signal enable Zhoujie Wu
2017-12-18 13:19 ` Adrian Hunter [this message]
2017-12-18 22:26   ` [EXT] " Zhoujie Wu

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=472f0d18-e529-2477-4809-079a5970a362@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=dingwei@marvell.com \
    --cc=dougj@marvell.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=hannah@marvell.com \
    --cc=hongd@marvell.com \
    --cc=kostap@marvell.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=liuw@marvell.com \
    --cc=nadavh@marvell.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=ulf.hansson@linaro.org \
    --cc=xigu@marvell.com \
    --cc=xswang@marvell.com \
    --cc=ygao@marvell.com \
    --cc=zjwu@marvell.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