linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <anton@enomsg.org>
To: Vincent Yang <vincent.yang.fujitsu@gmail.com>
Cc: andy.green@linaro.org, patches@linaro.org,
	linux-mmc@vger.kernel.org, chris@printf.net,
	Vincent.Yang@tw.fujitsu.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH 1/7] mmc: sdhci: add quirk for broken 3.0V support
Date: Fri, 20 Jun 2014 13:26:38 -0700	[thread overview]
Message-ID: <20140620202638.GA21349@teo> (raw)
In-Reply-To: <1403256928-11359-2-git-send-email-Vincent.Yang@tw.fujitsu.com>

On Fri, Jun 20, 2014 at 05:35:22PM +0800, Vincent Yang wrote:
> This patch defines a quirk for platforms unable
> to enable 3.0V support.
> It is a preparation and will be used by Fujitsu
> SDHCI controller f_sdh30 driver.
> 
> Signed-off-by: Vincent Yang <Vincent.Yang@tw.fujitsu.com>

I don't think you need this patch. Instead, you can exclude 3V using the
voltage-ranges = <> in the device tree.

Thanks,

Anton

>  drivers/mmc/host/sdhci.c  | 3 +++
>  include/linux/mmc/sdhci.h | 2 ++
>  2 files changed, 5 insertions(+)
> 
> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
> index 47055f3..523075f 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -3069,6 +3069,9 @@ int sdhci_add_host(struct sdhci_host *host)
>  	}
>  #endif /* CONFIG_REGULATOR */
>  
> +	if (host->quirks2 & SDHCI_QUIRK2_NO_3_0_V)
> +		caps[0] &= ~SDHCI_CAN_VDD_300;
> +
>  	/*
>  	 * According to SD Host Controller spec v3.00, if the Host System
>  	 * can afford more than 150mA, Host Driver should set XPC to 1. Also
> diff --git a/include/linux/mmc/sdhci.h b/include/linux/mmc/sdhci.h
> index 08abe99..cac0958 100644
> --- a/include/linux/mmc/sdhci.h
> +++ b/include/linux/mmc/sdhci.h
> @@ -98,6 +98,8 @@ struct sdhci_host {
>  #define SDHCI_QUIRK2_BROKEN_HS200			(1<<6)
>  /* Controller does not support DDR50 */
>  #define SDHCI_QUIRK2_BROKEN_DDR50			(1<<7)
> +/* The system physically doesn't support 3.0v, even if the host does */
> +#define SDHCI_QUIRK2_NO_3_0_V				(1<<8)
>  
>  	int irq;		/* Device IRQ */
>  	void __iomem *ioaddr;	/* Mapped address */
> -- 
> 1.9.0

  reply	other threads:[~2014-06-20 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20  9:35 [RFC PATCH 0/7] mmc: sdhci: adding support for a new Fujitsu sdhci IP Vincent Yang
2014-06-20  9:35 ` [RFC PATCH 1/7] mmc: sdhci: add quirk for broken 3.0V support Vincent Yang
2014-06-20 20:26   ` Anton Vorontsov [this message]
2014-06-21  4:29     ` Vincent Yang
2014-06-20  9:35 ` [RFC PATCH 2/7] mmc: sdhci: add quirk for voltage switch callback Vincent Yang
2014-06-20  9:35 ` [RFC PATCH 3/7] mmc: sdhci: add quirk for tuning work around Vincent Yang
2014-06-20  9:35 ` [RFC PATCH 4/7] mmc: sdhci: add quirk for single block transactions Vincent Yang
2014-06-20  9:35 ` [RFC PATCH 5/7] mmc: sdhci: host: add new f_sdh30 Vincent Yang
2014-06-20 10:00   ` Arnd Bergmann
2014-06-20 10:29     ` Vincent Yang
2014-06-20  9:35 ` [RFC PATCH 6/7] mmc: core: hold SD Clock before CMD11 during Signal Voltage Switch Procedure Vincent Yang
2014-06-20  9:35 ` [RFC PATCH 7/7] mmc: core: add manual resume capability Vincent Yang

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=20140620202638.GA21349@teo \
    --to=anton@enomsg.org \
    --cc=Vincent.Yang@tw.fujitsu.com \
    --cc=andy.green@linaro.org \
    --cc=chris@printf.net \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=patches@linaro.org \
    --cc=vincent.yang.fujitsu@gmail.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;
as well as URLs for NNTP newsgroup(s).