From: Mark Brown <broonie@kernel.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Tomasz Figa <t.figa@samsung.com>,
Arend van Spriel <arend@broadcom.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: [RFC] dt: bindings: add bindings for Broadcom bcm43xx sdio devices
Date: Mon, 31 Mar 2014 17:10:42 +0100 [thread overview]
Message-ID: <20140331161042.GW2269@sirena.org.uk> (raw)
In-Reply-To: <CAPDyKFpU=nQAgfjMm6KNRAEKwChAx_SxFMC-pLbq8yis2mgB=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
On Mon, Mar 31, 2014 at 10:24:00AM +0200, Ulf Hansson wrote:
> Using a gpio regulator would simplify here, since the driver don't
> need specific "SDIO hacks" but can use the mmc_regulator_get_supply()
> API, which calculates the OCR mask, based upon the regulator's
> supported voltages.
If that makes life easier the driver could also just instantiate a fixed
regulator itself rather than requiring that one be put in the DT?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-31 16:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 19:17 Arend van Spriel
2014-02-13 7:41 ` Chen-Yu Tsai
2014-02-13 9:13 ` Tomasz Figa
2014-02-13 9:28 ` Chen-Yu Tsai
2014-03-30 8:56 ` Arend van Spriel
2014-04-10 21:27 ` Jörg Krause
2014-04-11 8:06 ` Arend van Spriel
2014-02-13 12:07 ` Arend van Spriel
2014-02-13 12:35 ` Tomasz Figa
2014-02-13 16:22 ` Mark Brown
2014-03-31 8:24 ` Ulf Hansson
2014-03-31 16:10 ` Mark Brown [this message]
2014-02-25 22:51 ` Stephen Warren
2014-03-13 10:16 ` Arend van Spriel
2014-03-13 10:42 ` Tomasz Figa
2014-03-13 13:00 ` Arend van Spriel
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=20140331161042.GW2269@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arend@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=t.figa@samsung.com \
--cc=tomasz.figa@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®