From: Stephen Warren <swarren@wwwdotorg.org>
To: Rhyland Klein <rklein@nvidia.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Anton Vorontsov <cbou@mail.ru>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [Patch v3 3/4] power_supply: tps65090-charger: Add binding doc
Date: Tue, 12 Mar 2013 17:10:15 -0600 [thread overview]
Message-ID: <513FB5D7.5090800@wwwdotorg.org> (raw)
In-Reply-To: <1363126089-9071-4-git-send-email-rklein@nvidia.com>
On 03/12/2013 04:08 PM, Rhyland Klein wrote:
> This change adds the binding documentation for the tps65090-charger.
> diff --git a/Documentation/devicetree/bindings/power_supply/tps65090.txt b/Documentation/devicetree/bindings/power_supply/tps65090.txt
> +Example:
> +
> + tps65090@48 {
> + compatible = "ti,tps65090";
> + reg = <0x48>;
> + interrupts = <0 88 0x4>;
> +
> + ti,enable-low-current-chrg;
> +
> + regulators {
> + ...
> + };
I'm a little confused by this binding.
What goes in the regulators sub-node; is that specified by another
binding file in bindings/regulator/tps65090.txt?
I would expect one of the following:
1) A single binding file that describes absolutely everything in the
chip. In this case, the main TPS65909 node wouldn't have child nodes for
the MFD components, although the regulators sub-node, which in turn
contains children does still make sense.
2) A separate binding for each component block, and perhaps also some
top-level binding that indicates which child bindings can "plug into"
it. In this case, I'd expect each block to be represented as a sub-node
in DT. The overall regulator component might then still have a
regulators child DT node itself, to represent each regulator's
configuration. In this scenario, each binding document describes the
entirety of a single node.
I think what you've got here is a hybrid; a single top-level node, but
different binding documents defining the various properties that are
relevant to each component block in the device. That seems odd to me.
next prev parent reply other threads:[~2013-03-12 23:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 22:08 [Patch v3 0/4] Add support for tps65090-charger Rhyland Klein
2013-03-12 22:08 ` [Patch v3 1/4] mfd: tps65090: Fix enum in header file Rhyland Klein
2013-03-12 22:08 ` [Patch v3 2/4] mfd: tps65090: Add resources for charger Rhyland Klein
2013-03-19 16:17 ` Rhyland Klein
2013-03-12 22:08 ` [Patch v3 3/4] power_supply: tps65090-charger: Add binding doc Rhyland Klein
2013-03-12 23:10 ` Stephen Warren [this message]
2013-03-13 19:25 ` Rhyland Klein
2013-03-13 20:41 ` Stephen Warren
2013-03-13 21:08 ` Rhyland Klein
2013-03-12 22:08 ` [Patch v3 4/4] power: tps65090: Add support for tps65090-charger Rhyland Klein
2013-03-19 2:24 ` [Patch v3 0/4] " Anton Vorontsov
2013-03-19 15:55 ` Rhyland Klein
2013-03-19 15:59 ` Anton Vorontsov
2013-03-19 16:05 ` Rhyland Klein
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=513FB5D7.5090800@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cbou@mail.ru \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rklein@nvidia.com \
--cc=rob.herring@calxeda.com \
--cc=sameo@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox