From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Chris Ball <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>,
Pavan Kunapuli
<pkunapuli-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: sdhci-tegra and power-gpios
Date: Mon, 01 Oct 2012 10:05:55 -0600 [thread overview]
Message-ID: <5069BF63.20104@wwwdotorg.org> (raw)
In-Reply-To: <87vceunrzi.fsf-DGHOrqG7t0YzNDMTQreKSUB+6BGkLq7r@public.gmane.org>
On 10/01/2012 09:15 AM, Chris Ball wrote:
> Hi Stephen, tegra folks,
>
> sdhci-tegra uses a power-gpios property in the DT:
>
> sdhci@c8000400 {
...
> power-gpios = <&gpio 70 0>; /* gpio PI6 */
...
> It's quite easy to set up a regulator and attach it to an MMC node:
...
> sdhci@c8000400 {
...
> vmmc-supply = <&vmmc1>;
...
> Any interest in making this change?
Yes, it's certainly something we should be doing. Most Tegra boards will
only have all the regulators defined in device tree for the first time
in kernel 3.7, and so we've been holding off making any of the client
nodes use regulators because of that. Now that we have all the
regulators defined, I do hope we will quickly move to using them for
SDHCI. Pavan (now CC'd) will hopefully be doing this.
prev parent reply other threads:[~2012-10-01 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 15:15 sdhci-tegra and power-gpios Chris Ball
[not found] ` <87vceunrzi.fsf-DGHOrqG7t0YzNDMTQreKSUB+6BGkLq7r@public.gmane.org>
2012-10-01 16:05 ` Stephen Warren [this message]
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=5069BF63.20104@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org \
--cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pkunapuli-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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).