From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] mfd: mc13xxx: add device tree probe support
Date: Tue, 6 Dec 2011 10:13:05 +0000 [thread overview]
Message-ID: <20111206101304.GA28840@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111206032642.GI2980@S2100-06.ap.freescale.net>
On Tue, Dec 06, 2011 at 11:26:43AM +0800, Shawn Guo wrote:
> On Mon, Dec 05, 2011 at 07:09:47PM +0000, Mark Brown wrote:
> > That doesn't answer the question - I've still no idea how the binding is
> > supposed to map the nodes contained within regulators onto the physical
> > regulators.
> And here it is. It finds the regulator node by looking for the
> regulator name.
OK, this needs to be documented in the binding documentation - people
shouldn't need to look at the code to figure this out.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: "Sascha Hauer" <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Samuel Ortiz" <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
"Uwe Kleine-König"
<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"Liam Girdwood" <lrg-l0cyMroinI0@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2 1/4] mfd: mc13xxx: add device tree probe support
Date: Tue, 6 Dec 2011 10:13:05 +0000 [thread overview]
Message-ID: <20111206101304.GA28840@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111206032642.GI2980-+NayF8gZjK2ctlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
On Tue, Dec 06, 2011 at 11:26:43AM +0800, Shawn Guo wrote:
> On Mon, Dec 05, 2011 at 07:09:47PM +0000, Mark Brown wrote:
> > That doesn't answer the question - I've still no idea how the binding is
> > supposed to map the nodes contained within regulators onto the physical
> > regulators.
> And here it is. It finds the regulator node by looking for the
> regulator name.
OK, this needs to be documented in the binding documentation - people
shouldn't need to look at the code to figure this out.
next prev parent reply other threads:[~2011-12-06 10:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 9:21 [PATCH 0/4] Add device tree support for mc13892 regulator driver Shawn Guo
2011-12-01 9:21 ` Shawn Guo
2011-12-01 9:21 ` [PATCH v2 1/4] mfd: mc13xxx: add device tree probe support Shawn Guo
2011-12-01 9:21 ` Shawn Guo
2011-12-02 15:36 ` Mark Brown
2011-12-02 15:36 ` Mark Brown
2011-12-05 6:41 ` Shawn Guo
2011-12-05 6:41 ` Shawn Guo
2011-12-05 19:09 ` Mark Brown
2011-12-05 19:09 ` Mark Brown
2011-12-06 3:26 ` Shawn Guo
2011-12-06 3:26 ` Shawn Guo
2011-12-06 10:13 ` Mark Brown [this message]
2011-12-06 10:13 ` Mark Brown
2011-12-06 15:04 ` [PATCH v3] " Shawn Guo
2011-12-06 15:04 ` Shawn Guo
2011-12-12 1:20 ` Shawn Guo
2011-12-12 1:20 ` Shawn Guo
2011-12-12 17:56 ` Samuel Ortiz
2011-12-12 17:56 ` Samuel Ortiz
2011-12-01 9:21 ` [PATCH v2 2/4] regulator: pass device_node to of_get_regulator_init_data() Shawn Guo
2011-12-01 9:21 ` Shawn Guo
2011-12-05 18:22 ` Thomas Abraham
2011-12-05 18:22 ` Thomas Abraham
2011-12-05 19:28 ` Mark Brown
2011-12-05 19:28 ` Mark Brown
2011-12-01 9:21 ` [PATCH v2 3/4] regulator: mc13892: add device tree probe support Shawn Guo
2011-12-01 9:21 ` Shawn Guo
2011-12-12 1:21 ` Shawn Guo
2011-12-12 1:21 ` Shawn Guo
2011-12-12 3:16 ` Mark Brown
2011-12-12 3:16 ` Mark Brown
2011-12-12 17:56 ` Samuel Ortiz
2011-12-12 17:56 ` Samuel Ortiz
2011-12-01 9:21 ` [PATCH v2 4/4] arm/imx: add mc13892 support into imx51-babbage.dts Shawn Guo
2011-12-01 9:21 ` 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=20111206101304.GA28840@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 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.