From: Karl-Heinz Schneider <karl-heinz@schneider-inet.de>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Sebastian Reichel <sre@kernel.org>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Peter Rosin <peda@axentia.se>,
Phil Reid <preid@electromag.com.au>
Subject: Re: [PATCH v4 1/2] Documentation: Add sbs-manager device tree node documentation
Date: Wed, 31 Aug 2016 21:52:31 +0200 [thread overview]
Message-ID: <1472673151.5102.12.camel@schneider-inet.de> (raw)
In-Reply-To: <20160831144349.GA18510@rob-hp-laptop>
Hi Rob,
Am Mittwoch, den 31.08.2016, 09:43 -0500 schrieb Rob Herring:
> On Thu, Aug 25, 2016 at 10:21:00PM +0200, Karl-Heinz Schneider wrote:
> >
> > This patch adds device tree documentation for the sbs-manager
> >
> > Reviewed-by: Phil Reid <preid@electromag.com.au>
> > Signed-off-by: Karl-Heinz Schneider <karl-heinz@schneider-inet.de>
> > ---
> > .../devicetree/bindings/power/sbs,sbs-manager.txt | 53
> > ++++++++++++++++++++++
> > 1 file changed, 53 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/power/sbs,sbs-manager.txt
> >
> > diff --git a/Documentation/devicetree/bindings/power/sbs,sbs-
> > manager.txt b/Documentation/devicetree/bindings/power/sbs,sbs-
> > manager.txt
> > new file mode 100644
> > index 0000000..6b1a87ce
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/power/sbs,sbs-manager.txt
> > @@ -0,0 +1,53 @@
> > +Binding for sbs-manager
> > +
> > +Required properties:
> > +- compatible: should be "lltc,ltc1760" or use "sbs,sbs-manager" as
> > fallback.
> > +- reg: integer, i2c address of the device. Should be <0xa>.
> What happened to adding Phil's interrupt support into this? You
> don't
> have to add the whole patch, just the binding part. The driver
> support
> can come later.
Phil revoked his patch. Right now it's not clear how the interrupt/gpio
solution will look like and if they will need an device tree binding at
all...
>
> >
> > +
> > +From OS view the device is basically an i2c-mux used to
> > communicate with up to
> > +four smart battery devices at address 0xb. The driver actually
> > implements this
> > +behaviour. So standard i2c-mux nodes can be used to register up to
> > four slave
> > +batteries. See Documentation/devicetree/bindings/i2c/i2c-mux.txt
> > for more
> > +information on i2c-mux nodes. Channels will be numerated starting
> > from 1 to 4.
> > +
> > +Example:
> > +
> > +batman@0a {
> drop leading 0.
OK.
> >
> > + compatible = "lltc,ltc1760";
> > + reg = <0x0a>;
Will remove leading 0 at this places too.
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + i2c@1 {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + reg = <1>;
> > +
> > + battery@0b {
> and here...
OK.
> >
> > + compatible = "ti,bq2060", "sbs,sbs-battery";
> > + reg = <0x0b>;
> > + };
> > + };
> > +
> > + i2c@2 {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + reg = <2>;
> > +
> > + battery@0b {
> > + compatible = "ti,bq2060", "sbs,sbs-battery";
> > + reg = <0x0b>;
> > + };
> > + };
> > +
> > + i2c@3 {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + reg = <3>;
> > +
> > + battery@0b {
> > + compatible = "ti,bq2060", "sbs,sbs-battery";
> > + reg = <0x0b>;
> > + };
> > + };
> > +};
Thanks for review Rob.
--
Karl-Heinz
next prev parent reply other threads:[~2016-08-31 19:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1bIiDr-0004G1-0P>
2016-07-12 18:48 ` [PATCH v3 0/2] Add support for Smart Battery System Manager Karl-Heinz Schneider
2016-07-12 18:48 ` [PATCH v3 1/2] Documentation: Add sbs-manager device tree node documentation Karl-Heinz Schneider
2016-07-16 22:05 ` Rob Herring
2016-07-17 21:15 ` Karl-Heinz Schneider
2016-07-19 4:14 ` Wolfram Sang
2016-07-25 10:33 ` Peter Rosin
2016-07-25 11:24 ` Wolfram Sang
2016-07-12 18:48 ` [PATCH v3 2/2] power: Adds support for Smart Battery System Manager Karl-Heinz Schneider
2016-07-12 20:06 ` kbuild test robot
2016-07-12 20:06 ` [PATCH] power: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-07-19 4:17 ` [PATCH v3 2/2] power: Adds support for Smart Battery System Manager Wolfram Sang
2016-07-19 18:51 ` Karl-Heinz Schneider
2016-07-25 10:44 ` Peter Rosin
2016-07-25 19:49 ` Karl-Heinz Schneider
2016-08-25 20:20 ` [PATCH v4 0/2] Add " Karl-Heinz Schneider
2016-08-25 20:21 ` [PATCH v4 1/2] Documentation: Add sbs-manager device tree node documentation Karl-Heinz Schneider
2016-08-31 14:43 ` Rob Herring
2016-08-31 19:52 ` Karl-Heinz Schneider [this message]
[not found] ` <1472673151.5102.12.camel-X5L7DgJ4l23oE99TX8zNy7NAH6kLmebB@public.gmane.org>
2016-09-01 9:00 ` Phil Reid
2016-08-31 22:34 ` Karl-Heinz Schneider
2016-09-01 9:37 ` Phil Reid
2016-08-25 20:21 ` [PATCH v4 2/2] power: Adds support for Smart Battery System Manager Karl-Heinz Schneider
2016-08-31 15:10 ` [PATCH v4 0/2] Add " Sebastian Reichel
2016-08-31 19:54 ` Karl-Heinz Schneider
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=1472673151.5102.12.camel@schneider-inet.de \
--to=karl-heinz@schneider-inet.de \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=preid@electromag.com.au \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sre@kernel.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).