public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Daniel Mack <zonque@gmail.com>
Cc: linux-mmc@vger.kernel.org, Venkatraman S <svenkatr@ti.com>,
	Chris Ball <cjb@laptop.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH 4/4] MMC: omap_hsmmc: add DT property for max bus frequency
Date: Fri, 12 Oct 2012 10:25:37 -0500	[thread overview]
Message-ID: <50783671.1090308@gmail.com> (raw)
In-Reply-To: <1350039495-360-5-git-send-email-zonque@gmail.com>

On 10/12/2012 05:58 AM, Daniel Mack wrote:
> Maximum bus frequency can be limited by external circuitry like level
> shifters etc. Allow passing this value from DT.
> 
> Signed-off-by: Daniel Mack <zonque@gmail.com>
> Cc: Venkatraman S <svenkatr@ti.com>
> Cc: Chris Ball <cjb@laptop.org>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Cc: Rob Herring <rob.herring@calxeda.com>
> Cc: linux-omap@vger.kernel.org
> ---
>  drivers/mmc/host/omap_hsmmc.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
> index 86f0759..4650ef7 100644
> --- a/drivers/mmc/host/omap_hsmmc.c
> +++ b/drivers/mmc/host/omap_hsmmc.c
> @@ -1676,7 +1676,7 @@ static struct omap_mmc_platform_data *of_get_hsmmc_pdata(struct device *dev)
>  {
>  	struct omap_mmc_platform_data *pdata;
>  	struct device_node *np = dev->of_node;
> -	u32 bus_width;
> +	u32 bus_width, max_freq;
>  
>  	pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
>  	if (!pdata)
> @@ -1703,6 +1703,9 @@ static struct omap_mmc_platform_data *of_get_hsmmc_pdata(struct device *dev)
>  	if (of_find_property(np, "ti,needs-special-reset", NULL))
>  		pdata->slots[0].features |= HSMMC_HAS_UPDATED_RESET;
>  
> +	if (!of_property_read_u32(np, "max-frequency", &max_freq))
> +		pdata->max_freq = max_freq;
> +

Is this property documented?

Rob

>  	return pdata;
>  }
>  #else
> 

  reply	other threads:[~2012-10-12 15:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 10:58 [PATCH 0/4] MMC: some omap_hsmmc fixes Daniel Mack
2012-10-12 10:58 ` [PATCH 1/4] MMC: omap_hsmmc: set platform data after probe from DT node Daniel Mack
2012-10-12 14:29   ` Daniel Mack
2012-10-12 14:56     ` Balaji T K
2012-10-12 15:14       ` Daniel Mack
2012-10-12 15:23         ` Balaji T K
2012-10-13  0:05           ` Grant Likely
2012-10-13  8:05             ` Daniel Mack
2012-10-13  8:48               ` Grant Likely
2012-10-13  8:53                 ` Daniel Mack
2012-10-13 12:37                   ` Grant Likely
2012-10-12 10:58 ` [PATCH 2/4] MMC: omap_hsmmc: fix DMA config block Daniel Mack
2012-10-12 11:07   ` Porter, Matt
2012-10-12 11:12   ` Russell King - ARM Linux
2012-10-12 14:19     ` Daniel Mack
2012-10-12 10:58 ` [PATCH 3/4] MMC: omap_hsmmc: claim pinctrl at probe time Daniel Mack
2012-10-12 11:08   ` Linus Walleij
2012-10-12 10:58 ` [PATCH 4/4] MMC: omap_hsmmc: add DT property for max bus frequency Daniel Mack
2012-10-12 15:25   ` Rob Herring [this message]
2012-10-12 15:26     ` Daniel Mack
2012-10-13  9:01 ` [PATCH 0/4] MMC: some omap_hsmmc fixes Daniel Mack
2012-10-15 16:07   ` Venkatraman S

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=50783671.1090308@gmail.com \
    --to=robherring2@gmail.com \
    --cc=cjb@laptop.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=svenkatr@ti.com \
    --cc=zonque@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