From: Olof Johansson <olof@lixom.net>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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 v4 1/4] regulator: helper routine to extract regulator_init_data
Date: Fri, 4 Nov 2011 14:22:16 -0700 [thread overview]
Message-ID: <20111104212216.GA5756@quad.lixom.net> (raw)
In-Reply-To: <20111104211447.GC2541@opensource.wolfsonmicro.com>
On Fri, Nov 04, 2011 at 09:14:48PM +0000, Mark Brown wrote:
> On Fri, Nov 04, 2011 at 01:29:05PM -0700, Olof Johansson wrote:
> > On Thu, Oct 27, 2011 at 06:54:24PM +0530, Rajendra Nayak wrote:
>
> > > @@ -0,0 +1,33 @@
> > > +Voltage/Current Regulators
>
> > There should be a mandatory compatible field here, right? I.e. a topmost
> > generic one, "regulator" or similar.
>
> It's not really useful for the regulator subsystem to directly bind to
> the device as something needs to actually control it, the idea is that
> this binding is included by reference in the bindings for specific
> devices.
Right, same goes for many other devices. Some use a toplevel compatible field,
some do not. Either way, not a big deal if you don't want to include one.
> > Also, lower-caps is common instead of V and A.
>
> On the other hand the case is pretty important for SI units
Yeah, true. The fixed regulators used microvolt instead, which could be a good
way to do it.
> > > +- <name>-supply: phandle to the parent supply/regulator node
>
> > Having a fixed name here instead of a free form string would probably be a good
> > idea?
>
> The name will be fixed by the individual device bindings, this is
> specifying the general form of a supply property. Each device binding
> will define the set of supplies that the device can use.
Ah, ok. It shouldn't be a part of this binding then and instead be added
to the bindings for the consumers.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/4] regulator: helper routine to extract regulator_init_data
Date: Fri, 4 Nov 2011 14:22:16 -0700 [thread overview]
Message-ID: <20111104212216.GA5756@quad.lixom.net> (raw)
In-Reply-To: <20111104211447.GC2541@opensource.wolfsonmicro.com>
On Fri, Nov 04, 2011 at 09:14:48PM +0000, Mark Brown wrote:
> On Fri, Nov 04, 2011 at 01:29:05PM -0700, Olof Johansson wrote:
> > On Thu, Oct 27, 2011 at 06:54:24PM +0530, Rajendra Nayak wrote:
>
> > > @@ -0,0 +1,33 @@
> > > +Voltage/Current Regulators
>
> > There should be a mandatory compatible field here, right? I.e. a topmost
> > generic one, "regulator" or similar.
>
> It's not really useful for the regulator subsystem to directly bind to
> the device as something needs to actually control it, the idea is that
> this binding is included by reference in the bindings for specific
> devices.
Right, same goes for many other devices. Some use a toplevel compatible field,
some do not. Either way, not a big deal if you don't want to include one.
> > Also, lower-caps is common instead of V and A.
>
> On the other hand the case is pretty important for SI units
Yeah, true. The fixed regulators used microvolt instead, which could be a good
way to do it.
> > > +- <name>-supply: phandle to the parent supply/regulator node
>
> > Having a fixed name here instead of a free form string would probably be a good
> > idea?
>
> The name will be fixed by the individual device bindings, this is
> specifying the general form of a supply property. Each device binding
> will define the set of supplies that the device can use.
Ah, ok. It shouldn't be a part of this binding then and instead be added
to the bindings for the consumers.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof@lixom.net>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Rajendra Nayak <rnayak@ti.com>,
grant.likely@secretlab.ca, patches@linaro.org, tony@atomide.com,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
lrg@ti.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/4] regulator: helper routine to extract regulator_init_data
Date: Fri, 4 Nov 2011 14:22:16 -0700 [thread overview]
Message-ID: <20111104212216.GA5756@quad.lixom.net> (raw)
In-Reply-To: <20111104211447.GC2541@opensource.wolfsonmicro.com>
On Fri, Nov 04, 2011 at 09:14:48PM +0000, Mark Brown wrote:
> On Fri, Nov 04, 2011 at 01:29:05PM -0700, Olof Johansson wrote:
> > On Thu, Oct 27, 2011 at 06:54:24PM +0530, Rajendra Nayak wrote:
>
> > > @@ -0,0 +1,33 @@
> > > +Voltage/Current Regulators
>
> > There should be a mandatory compatible field here, right? I.e. a topmost
> > generic one, "regulator" or similar.
>
> It's not really useful for the regulator subsystem to directly bind to
> the device as something needs to actually control it, the idea is that
> this binding is included by reference in the bindings for specific
> devices.
Right, same goes for many other devices. Some use a toplevel compatible field,
some do not. Either way, not a big deal if you don't want to include one.
> > Also, lower-caps is common instead of V and A.
>
> On the other hand the case is pretty important for SI units
Yeah, true. The fixed regulators used microvolt instead, which could be a good
way to do it.
> > > +- <name>-supply: phandle to the parent supply/regulator node
>
> > Having a fixed name here instead of a free form string would probably be a good
> > idea?
>
> The name will be fixed by the individual device bindings, this is
> specifying the general form of a supply property. Each device binding
> will define the set of supplies that the device can use.
Ah, ok. It shouldn't be a part of this binding then and instead be added
to the bindings for the consumers.
-Olof
next prev parent reply other threads:[~2011-11-04 21:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 13:24 [PATCH v4 1/4] regulator: helper routine to extract regulator_init_data Rajendra Nayak
2011-10-27 13:24 ` Rajendra Nayak
2011-10-27 13:24 ` Rajendra Nayak
2011-11-04 20:29 ` Olof Johansson
2011-11-04 20:29 ` Olof Johansson
2011-11-04 20:29 ` Olof Johansson
[not found] ` <20111104202905.GA3918-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2011-11-04 21:14 ` Mark Brown
2011-11-04 21:14 ` Mark Brown
2011-11-04 21:14 ` Mark Brown
2011-11-04 21:22 ` Olof Johansson [this message]
2011-11-04 21:22 ` Olof Johansson
2011-11-04 21:22 ` Olof Johansson
2011-11-04 21:29 ` Mark Brown
2011-11-04 21:29 ` Mark Brown
2011-11-04 21:29 ` Mark Brown
2011-11-04 21:34 ` Olof Johansson
2011-11-04 21:34 ` Olof Johansson
2011-11-04 21:34 ` Olof Johansson
2011-11-04 21:46 ` Mark Brown
2011-11-04 21:46 ` Mark Brown
2011-11-04 22:16 ` Olof Johansson
2011-11-04 22:16 ` Olof Johansson
2011-11-04 22:35 ` Mark Brown
2011-11-04 22:35 ` Mark Brown
2011-11-04 22:35 ` Mark Brown
2011-11-04 22:50 ` Olof Johansson
2011-11-04 22:50 ` Olof Johansson
2011-11-04 22:50 ` Olof Johansson
2011-11-07 6:27 ` Rajendra Nayak
2011-11-07 6:27 ` Rajendra Nayak
[not found] ` <20111104212216.GA5756-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2011-11-07 6:27 ` Rajendra Nayak
2011-11-07 6:27 ` Rajendra Nayak
2011-11-07 6:27 ` Rajendra Nayak
2011-11-07 6:23 ` Rajendra Nayak
2011-11-07 6:23 ` Rajendra Nayak
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=20111104212216.GA5756@quad.lixom.net \
--to=olof@lixom.net \
--cc=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.