From: Scott Wood <scottwood@freescale.com>
To: Zhang Haijun-B42677 <B42677@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Fleming Andy-AFLEMING <afleming@freescale.com>,
"cbouatmailru@gmail.com" <cbouatmailru@gmail.com>,
"cjb@laptop.org" <cjb@laptop.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] mmc: esdhc: get voltage from dts file
Date: Mon, 22 Jul 2013 21:41:34 -0500 [thread overview]
Message-ID: <1374547294.15592.22@snotra> (raw)
In-Reply-To: <99E897753B6F7048BD8CCDB4661D02E13E49EC@039-SN2MPN1-022.039d.mgd.msft.net> (from B42677@freescale.com on Mon Jul 22 21:38:33 2013)
On 07/22/2013 09:38:33 PM, Zhang Haijun-B42677 wrote:
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Tuesday, July 23, 2013 1:41 AM
> > To: Zhang Haijun-B42677
> > Cc: linux-mmc@vger.kernel.org; linuxppc-dev@lists.ozlabs.org;
> > cbouatmailru@gmail.com; cjb@laptop.org; Fleming Andy-AFLEMING; Zhang
> > Haijun-B42677; Zhang Haijun-B42677
> > Subject: Re: [PATCH 2/2] mmc: esdhc: get voltage from dts file
> >
> > On 07/22/2013 02:53:56 AM, Haijun Zhang wrote:
> > > Add voltage-range support in esdhc of T4, So we can choose to read
> > > voltages from dts file as one optional.
> > > If we can get a valid voltage-range from device node, we use this
> > > voltage as the final voltage support. Else we still read from =20
> capacity
> > > or from other provider.
> > >
> > > Signed-off-by: Haijun Zhang <haijun.zhang@freescale.com>
> > > Signed-off-by: Anton Vorontsov <cbouatmailru@gmail.com>
> > > ---
> > > drivers/mmc/host/sdhci-of-esdhc.c | 31
> > > +++++++++++++++++++++++++++++++
> > > drivers/mmc/host/sdhci.c | 3 +++
> > > include/linux/mmc/sdhci.h | 1 +
> > > 3 files changed, 35 insertions(+)
> > >
> > > diff --git a/drivers/mmc/host/sdhci-of-esdhc.c
> > > b/drivers/mmc/host/sdhci-of-esdhc.c
> > > index 15039e2..8b4b27a 100644
> > > --- a/drivers/mmc/host/sdhci-of-esdhc.c
> > > +++ b/drivers/mmc/host/sdhci-of-esdhc.c
> > > @@ -262,6 +262,35 @@ static int esdhc_pltfm_bus_width(struct
> > > sdhci_host *host, int width)
> > > return 0;
> > > }
> > >
> > > +static void esdhc_get_voltage(struct sdhci_host *host,
> > > + struct platform_device *pdev)
> > > +{
> > > + const u32 *voltage_ranges;
> > > + int num_ranges, i;
> > > + struct device_node *np;
> > > + np =3D pdev->dev.of_node;
> > > +
> > > + voltage_ranges =3D of_get_property(np, "voltage-ranges",
> > > &num_ranges);
> > > + num_ranges =3D num_ranges / sizeof(*voltage_ranges) / 2;
> > > + if (!voltage_ranges || !num_ranges) {
> > > + dev_info(&pdev->dev, "OF: voltage-ranges
> > > unspecified\n");
> > > + return;
> > > + }
> > > +
> > > + for (i =3D 0; i < num_ranges; i++) {
> > > + const int j =3D i * 2;
> > > + u32 mask;
> > > + mask =3D
> > > mmc_vddrange_to_ocrmask(be32_to_cpu(voltage_ranges[j]),
> > > + be32_to_cpu(voltage_ranges[j + 1]));
> > > + if (!mask) {
> > > + dev_info(&pdev->dev,
> > > + "OF: false voltage-ranges specified\n");
> > > + return;
> > > + }
> > > + host->ocr_mask |=3D mask;
> > > + }
> > > +}
> >
> > Don't duplicate this code. Move it somewhere common and share it.
> [Haijun Wrote:] So, move it drivers/mmc/host/sdhci-pltfm.c and share =20
> it as
> Sdhc_get_voltage()....?
I'll let the MMC maintainer say what the appropriate place would be... =20
Don't capitalize the function name, though. :-)
-Scott=
next prev parent reply other threads:[~2013-07-23 2:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 7:53 [PATCH 1/2] Powerpc: Add voltage ranges support for T4 Haijun Zhang
2013-07-22 7:53 ` [PATCH 2/2] mmc: esdhc: get voltage from dts file Haijun Zhang
2013-07-22 17:40 ` Scott Wood
2013-07-23 2:38 ` Zhang Haijun-B42677
2013-07-23 2:41 ` Scott Wood [this message]
2013-07-23 3:41 ` Zhang Haijun-B42677
2013-07-26 19:06 ` Anton Vorontsov
2013-07-22 9:47 ` [PATCH 1/2] Powerpc: Add voltage ranges support for T4 Wrobel Heinz-R39252
2013-07-22 14:39 ` Kumar Gala
2013-07-23 2:05 ` Zhang Haijun-B42677
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=1374547294.15592.22@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B42677@freescale.com \
--cc=afleming@freescale.com \
--cc=cbouatmailru@gmail.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).