From: Mark Brown <broonie@kernel.org>
To: Alban Bedel <alban.bedel@avionic-design.de>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Grant Likely <grant.likely@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 1/4] devicetree: add a binding for a regulator that constrains its supply
Date: Mon, 24 Nov 2014 18:04:22 +0000 [thread overview]
Message-ID: <20141124180422.GO7712@sirena.org.uk> (raw)
In-Reply-To: <20141124181233.53580998@avionic-0020>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Mon, Nov 24, 2014 at 06:12:33PM +0100, Alban Bedel wrote:
> Using this driver the DTS for the add-on board can further constrain
> this supply to get the voltage it need, for example 3.3V. I understand
> I saw 3 ways to solve this problem:
> 1) This, use a "filter" regulator
> 2) Extend each and every driver that use a voltage regulator to
> optionally set the voltage
> 3) Include the required range in the phandle reference
> #1 was the easiest :) #2 doesn't seems practical to me, #3 seems pretty
> good but I'm really not sure if that would be acceptable.
The DT overlay for the add on board should be setting the constraints
for the parent regulator. I wouldn't expect the final DT to look any
different to how it looks with no hardware modularity unless the actual
module is interesting enough to have a driver of its own.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-11-24 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 13:02 [PATCH 1/4] devicetree: add a binding for a regulator that constrains its supply Alban Bedel
2014-11-24 13:02 ` [PATCH 2/4] regulator: add a regulator that constrain " Alban Bedel
2014-11-24 13:02 ` [PATCH 3/4] devicetree: add a binding for a group of regulator Alban Bedel
2014-11-24 15:24 ` Mark Brown
2014-11-24 17:32 ` Alban Bedel
2014-11-24 17:55 ` Mark Brown
2014-11-24 13:02 ` [PATCH 4/4] regulator: add a regulator group driver Alban Bedel
2014-11-24 15:15 ` [PATCH 1/4] devicetree: add a binding for a regulator that constrains its supply Mark Brown
2014-11-24 17:12 ` Alban Bedel
2014-11-24 18:04 ` Mark Brown [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=20141124180422.GO7712@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alban.bedel@avionic-design.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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