All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: philipspatches@gmail.com
Cc: linux-mmc@vger.kernel.org, aaron.lu@amd.com,
	mark.brown314@gmail.com, Philip Rakity <prakity@marvell.com>
Subject: Re: [PATCH 2/2] mmc: only support voltage (vdd) that regulator agree's with
Date: Wed, 27 Jun 2012 12:46:05 -0400	[thread overview]
Message-ID: <871ul08zzm.fsf@octavius.laptop.org> (raw)
In-Reply-To: <1339183573-21688-1-git-send-email-prakity@marvell.com> (philipspatches@gmail.com's message of "Fri, 8 Jun 2012 12:26:13 -0700")

Hi,

On Fri, Jun 08 2012, philipspatches@gmail.com wrote:
> From: Philip Rakity <prakity@marvell.com>
>
> If we are using a regulator the SD Host Controller and the
> regulator should agree about the voltages supported.  Use
> the common subset that is supported.
>
> Signed-off-by: Philip Rakity <prakity@marvell.com>
> ---
>  drivers/mmc/host/sdhci.c |   15 +++++++++++++++
>  1 files changed, 15 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
> index 248f68b..78be427 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -2894,6 +2894,21 @@ int sdhci_add_host(struct sdhci_host *host)
>  	 * register is set. The actual current value is 4 times the register
>  	 * value.
>  	 */
> +	if (host->vmmc) {
> +		ret = regulator_is_supported_voltage(host->vmmc, 3300000,
> +			3300000);
> +		if ((ret <= 0) || (!(caps[0] & SDHCI_CAN_VDD_330)))
> +			caps[0] &= ~SDHCI_CAN_VDD_330;
> +		ret = regulator_is_supported_voltage(host->vmmc, 3000000,
> +			3000000);
> +		if ((ret <= 0) || (!(caps[0] & SDHCI_CAN_VDD_300)))
> +			caps[0] &= ~SDHCI_CAN_VDD_300;
> +		ret = regulator_is_supported_voltage(host->vmmc, 1800000,
> +			1800000);
> +		if ((ret <= 0) || (!(caps[0] & SDHCI_CAN_VDD_180)))
> +			caps[0] &= ~SDHCI_CAN_VDD_180;
> +	}
> +
>  	max_current_caps = sdhci_readl(host, SDHCI_MAX_CURRENT);
>  	if (!max_current_caps && host->vmmc) {
>  		u32 curr = regulator_get_current_limit(host->vmmc);

Thanks, pushed to mmc-next for 3.6.

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2012-06-27 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 19:26 [PATCH 2/2] mmc: only support voltage (vdd) that regulator agree's with philipspatches
2012-06-27 16:46 ` Chris Ball [this message]
2012-06-29 23:19 ` Chris Ball
2012-07-03  6:06   ` Aaron Lu
2012-07-03  6:12     ` Chris Ball
2012-11-09  9:50 ` Tushar Behera

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=871ul08zzm.fsf@octavius.laptop.org \
    --to=cjb@laptop.org \
    --cc=aaron.lu@amd.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mark.brown314@gmail.com \
    --cc=philipspatches@gmail.com \
    --cc=prakity@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 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.