From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "J, KEERTHY" <j-keerthy@ti.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"rob@landley.net" <rob@landley.net>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>
Subject: Re: [PATCH 1/4] documentation: add palmas dts definition
Date: Sat, 2 Mar 2013 12:07:33 +0800 [thread overview]
Message-ID: <20130302040730.GI6610@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <512E4D99.6030201@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
On Wed, Feb 27, 2013 at 11:16:57AM -0700, Stephen Warren wrote:
> I believe what Mark wants is something like the following in this file
> (take from Documentation/devicetree/bindings/regulator/tps6586x.txt):
> > - regulators: A node that houses a sub-node for each regulator within the
> > device. Each sub-node is identified using the node's name (or the deprecated
> > regulator-compatible property if present), with valid values listed below.
> > The content of each sub-node is defined by the standard binding for
> > regulators; see regulator.txt.
> > sys, sm[0-2], ldo[0-9] and ldo_rtc
Yes, exactly.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-02 4:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 4:00 [PATCH 1/4] documentation: add palmas dts definition J Keerthy
2013-02-20 11:26 ` Mark Brown
2013-02-20 13:49 ` J, KEERTHY
2013-02-27 18:16 ` Stephen Warren
2013-03-02 4:07 ` Mark Brown [this message]
2013-02-25 8:55 ` J, KEERTHY
-- strict thread matches above, loose matches on Subject: below --
2013-02-18 5:11 J Keerthy
2013-02-27 18:32 ` Stephen Warren
2013-02-28 8:52 ` Laxman Dewangan
2013-02-28 9:58 ` Graeme Gregory
2013-02-28 10:27 ` Laxman Dewangan
2013-02-28 10:57 ` Graeme Gregory
2013-02-28 11:21 ` Graeme Gregory
2013-02-28 19:01 ` Stephen Warren
2013-02-28 18:58 ` Stephen Warren
2013-02-28 18:51 ` Stephen Warren
2013-02-28 12:09 ` J, KEERTHY
2013-02-28 19:07 ` Stephen Warren
2013-03-01 2:24 ` J, KEERTHY
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=20130302040730.GI6610@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=j-keerthy@ti.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).