From: Rajendra Nayak <rnayak@ti.com>
To: Olof Johansson <olof@lixom.net>
Cc: broonie@opensource.wolfsonmicro.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: Mon, 07 Nov 2011 11:53:36 +0530 [thread overview]
Message-ID: <4EB77968.803@ti.com> (raw)
In-Reply-To: <20111104202905.GA3918@quad.lixom.net>
Hi Olof,
On Saturday 05 November 2011 01:59 AM, Olof Johansson wrote:
>> +- regulator-min-uV: smallest voltage consumers may set
>> > +- regulator-max-uV: largest voltage consumers may set
>> > +- regulator-uV-offset: Offset applied to voltages to compensate for voltage drops
>> > +- regulator-min-uA: smallest current consumers may set
>> > +- regulator-max-uA: largest current consumers may set
>> > +- regulator-always-on: boolean, regulator should never be disabled
>> > +- regulator-boot-on: bootloader/firmware enabled regulator
>
> Once you have a compatible field that can determine what kind of device node,
> and binding, this is, you can drop the regulator- prefix and save some space in
> the device tree. Properties are rarely prefixed by their subsystem. Only
> exception would/could be the regulator-name property where it could make
> sense to keep the prefix.
given that we decided not to have a compatible field like "regulator"
for the top-level bindings and instead have a device specific one,
and based on the discussions with Grant here[1], I hope its OK to keep
these the way they are.
regards,
Rajendra
[1]
http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-September/008196.html
WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/4] regulator: helper routine to extract regulator_init_data
Date: Mon, 07 Nov 2011 11:53:36 +0530 [thread overview]
Message-ID: <4EB77968.803@ti.com> (raw)
In-Reply-To: <20111104202905.GA3918@quad.lixom.net>
Hi Olof,
On Saturday 05 November 2011 01:59 AM, Olof Johansson wrote:
>> +- regulator-min-uV: smallest voltage consumers may set
>> > +- regulator-max-uV: largest voltage consumers may set
>> > +- regulator-uV-offset: Offset applied to voltages to compensate for voltage drops
>> > +- regulator-min-uA: smallest current consumers may set
>> > +- regulator-max-uA: largest current consumers may set
>> > +- regulator-always-on: boolean, regulator should never be disabled
>> > +- regulator-boot-on: bootloader/firmware enabled regulator
>
> Once you have a compatible field that can determine what kind of device node,
> and binding, this is, you can drop the regulator- prefix and save some space in
> the device tree. Properties are rarely prefixed by their subsystem. Only
> exception would/could be the regulator-name property where it could make
> sense to keep the prefix.
given that we decided not to have a compatible field like "regulator"
for the top-level bindings and instead have a device specific one,
and based on the discussions with Grant here[1], I hope its OK to keep
these the way they are.
regards,
Rajendra
[1]
http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-September/008196.html
next prev parent reply other threads:[~2011-11-07 6:23 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
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 [this message]
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=4EB77968.803@ti.com \
--to=rnayak@ti.com \
--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=olof@lixom.net \
--cc=patches@linaro.org \
--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.