From: Rajendra Nayak <rnayak@ti.com>
To: Olof Johansson <olof@lixom.net>
Cc: Mark Brown <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:57:27 +0530 [thread overview]
Message-ID: <4EB77A4F.5010007@ti.com> (raw)
In-Reply-To: <CAOesGMjkcExKXhNN1nFGey=wBie0PQGp2XS_r-5Rr3X0p4eNhg@mail.gmail.com>
On Saturday 05 November 2011 03:46 AM, Olof Johansson wrote:
>>> Yeah, ok, but it shouldn't be part of the description of regulator
>>> >> properties per se. See how gpio does it, defining how a gpio-specifier
>>> >> is crafted. The equivalent should be done for regulators.
>> >
>> > That seems to be pretty much exactly what's being done here, and like
>> > the GPIO bindings it's specified in the core document. Though perhaps
>> > there's some aspect of how the document is written that's missing.
>
> Yep, sounds good. A slightly more elaborate description of the binding
> inspired by the gpio.txt document would be the way to do that.
>
Ok, will add more elaborate documentation for this in the core
bindings.
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:57:27 +0530 [thread overview]
Message-ID: <4EB77A4F.5010007@ti.com> (raw)
In-Reply-To: <CAOesGMjkcExKXhNN1nFGey=wBie0PQGp2XS_r-5Rr3X0p4eNhg@mail.gmail.com>
On Saturday 05 November 2011 03:46 AM, Olof Johansson wrote:
>>> Yeah, ok, but it shouldn't be part of the description of regulator
>>> >> properties per se. See how gpio does it, defining how a gpio-specifier
>>> >> is crafted. The equivalent should be done for regulators.
>> >
>> > That seems to be pretty much exactly what's being done here, and like
>> > the GPIO bindings it's specified in the core document. Though perhaps
>> > there's some aspect of how the document is written that's missing.
>
> Yep, sounds good. A slightly more elaborate description of the binding
> inspired by the gpio.txt document would be the way to do that.
>
Ok, will add more elaborate documentation for this in the core
bindings.
next prev parent reply other threads:[~2011-11-07 6:27 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 [this message]
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=4EB77A4F.5010007@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.