From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] mfd: mc13xxx: add device tree probe support
Date: Tue, 20 Dec 2011 01:59:32 +0000 [thread overview]
Message-ID: <20111220015931.GX2860@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111220020101.GD5683@S2100-06.ap.freescale.net>
On Tue, Dec 20, 2011 at 10:01:02AM +0800, Shawn Guo wrote:
> On Tue, Dec 20, 2011 at 12:57:09AM +0000, Mark Brown wrote:
> > On Mon, Dec 12, 2011 at 11:15:56PM +0800, Shawn Guo wrote:
> > > +Sub-nodes:
> > > +- regulators : Contain the regulator nodes. The name of regulator node
> > > + is being used by mc13xxx regulator driver to find the correct relator
> > > + device.
> > Reading this I'm not clear what the name of the node is, or what the
> > valid node names are.
> In the example below, the name would be 'mc13892__sw1'.
You're missing the point - someone reading the documentation needs to be
able to figure out what strings they need to use for all the different
regulators on the chip are without groveling through the driver code.
> > > + sw1_reg: mc13892__sw1 {
> > The examples don't really elucidate this either (and the __ is rather
> > odd).
> Yes, that's because the name defined by mc13892 regulator driver is odd.
That's *not* something that we should be exposing in the device tree
bindings. This is an implementation detail of the Linux driver which
might well change in future.
next prev parent reply other threads:[~2011-12-20 1:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 15:15 [PATCH v3 0/3] Add device tree support for mc13892 regulator driver Shawn Guo
2011-12-12 15:15 ` [PATCH v3 1/3] mfd: mc13xxx: add device tree probe support Shawn Guo
2011-12-20 0:57 ` Mark Brown
2011-12-20 2:01 ` Shawn Guo
2011-12-20 1:59 ` Mark Brown [this message]
2011-12-20 3:03 ` Shawn Guo
2011-12-20 11:25 ` Mark Brown
2011-12-20 13:52 ` Shawn Guo
2011-12-20 14:35 ` Mark Brown
2011-12-20 15:31 ` Shawn Guo
2011-12-20 23:25 ` Mark Brown
2011-12-21 1:25 ` Shawn Guo
2011-12-21 1:37 ` Mark Brown
2011-12-21 2:12 ` Shawn Guo
2011-12-12 15:15 ` [PATCH v3 2/3] regulator: mc13892: " Shawn Guo
2011-12-19 14:07 ` Shawn Guo
2011-12-20 0:54 ` Mark Brown
2011-12-20 1:37 ` Shawn Guo
2011-12-20 1:34 ` Mark Brown
2011-12-20 2:02 ` Shawn Guo
2011-12-12 15:15 ` [PATCH v3 3/3] arm/imx: add mc13892 support into imx51-babbage.dts Shawn Guo
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=20111220015931.GX2860@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).