From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Olof Johansson <olof@lixom.net>
Cc: patches@linaro.org, tony@atomide.com,
devicetree-discuss@lists.ozlabs.org,
Rajendra Nayak <rnayak@ti.com>,
linux-kernel@vger.kernel.org, grant.likely@secretlab.ca,
linux-omap@vger.kernel.org, lrg@ti.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/4] regulator: adapt fixed regulator driver to dt
Date: Fri, 4 Nov 2011 21:57:33 +0000 [thread overview]
Message-ID: <20111104215733.GD8266@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAOesGMh2_C+yx=_5PjqoKxZmAMvx-puRjq45s+G2kz2EaEEtqw@mail.gmail.com>
On Fri, Nov 04, 2011 at 02:47:05PM -0700, Olof Johansson wrote:
> On Fri, Nov 4, 2011 at 2:25 PM, Mark Brown
> > I don't see how you can usefully do that, the task of plumbing a
> > regulator into a board is largely orthogonal to the specific feature set
> > of a given regulator. The specific bindings for a fixed voltage
> > regulator would be useful or unhelpful for most regultors controlled via
> > I2C.
> I meant more that the fixed regulators should reuse as much as
> possible from the generic regulator bindings, instead of completely
> forking them.
That appears to be what's going on? The fixed voltage regulator
includes by reference the core regulator binding, all of the properties
it defines with the possible exception of the supply name are not
covered in the core binding.
> Then, depending on how they are controlled, there will be more
> specific bindings. So the case of a gpio-controlled fixed regulator
> would have a binding where the format of the properties to find the
> gpio, etc, would be described. But things like voltage (without a
> range, obviously) would be using the same bindings as the other
> regulators.
The only overlap I'm seeing is the voltage?
The intended semantic for the voltage is rather different. The core
binding for the voltage specifies the range of voltages it is possible
to set a regulator to on a given board and is used to give permission to
the system to reconfigure the regulator. The binding here tells the
system what voltage a fixed voltage regulator is running at. We could
have the fixed voltage regulator read the same binding - though there's
some risk of mild confusion it shouldn't be too bad.
next prev parent reply other threads:[~2011-11-04 21:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 7:56 [PATCH v3 0/4] Device tree support for regulators Rajendra Nayak
[not found] ` <1319702185-16108-1-git-send-email-rnayak-l0cyMroinI0@public.gmane.org>
2011-10-27 7:56 ` [PATCH v3 1/4] regulator: helper routine to extract regulator_init_data Rajendra Nayak
2011-10-27 8:09 ` Mark Brown
2011-10-27 10:43 ` Nayak, Rajendra
2011-10-27 11:49 ` Mark Brown
2011-10-27 13:27 ` Rajendra Nayak
2011-10-27 7:56 ` [PATCH v3 2/4] regulator: adapt fixed regulator driver to dt Rajendra Nayak
[not found] ` <1319702185-16108-3-git-send-email-rnayak-l0cyMroinI0@public.gmane.org>
2011-10-27 12:18 ` Mark Brown
2011-11-04 20:34 ` Olof Johansson
2011-11-04 21:01 ` Mark Brown
2011-11-04 21:18 ` Olof Johansson
2011-11-04 21:25 ` Mark Brown
2011-11-04 21:47 ` Olof Johansson
2011-11-04 21:57 ` Mark Brown [this message]
2011-11-04 22:09 ` Olof Johansson
2011-11-04 22:23 ` Mark Brown
[not found] ` <20111104203422.GB3918-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2011-11-07 6:27 ` Rajendra Nayak
2011-10-27 7:56 ` [PATCH v3 3/4] regulator: pass additional of_node to regulator_register() Rajendra Nayak
[not found] ` <1319702185-16108-4-git-send-email-rnayak-l0cyMroinI0@public.gmane.org>
2011-10-27 12:20 ` Mark Brown
2011-10-27 7:56 ` [PATCH v3 4/4] regulator: map consumer regulator based on device tree Rajendra Nayak
2011-10-27 12:20 ` Mark Brown
2011-10-27 9:08 ` [PATCH v3 0/4] Device tree support for regulators Mark Brown
2011-11-04 20:21 ` Olof Johansson
[not found] ` <CAOesGMii8v3DOCjWpuF3=+EVu+-HYGys=7RRgpk+9U=FxTHwOA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-04 21:02 ` Mark Brown
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=20111104215733.GD8266@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=olof@lixom.net \
--cc=patches@linaro.org \
--cc=rnayak@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).