From: Karl-Heinz Schneider <karl-heinz@schneider-inet.de>
To: Sebastian Reichel <sre@kernel.org>
Cc: devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
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 v2 1/2] Documentation: Add sbs-manager device tree node documentation
Date: Fri, 01 Jul 2016 23:49:31 +0200 [thread overview]
Message-ID: <1467409771.9121.38.camel@amnesix> (raw)
In-Reply-To: <20160630225217.GA11555@earth>
Hi Sebastian,
Am Freitag, den 01.07.2016, 00:52 +0200 schrieb Sebastian Reichel:
> Hi,
>
> On Thu, Jun 30, 2016 at 10:05:41PM +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 | 52 ++++++++++++++++++++++
> > 1 file changed, 52 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..1d7e5ee
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/power/sbs,sbs-manager.txt
> > @@ -0,0 +1,52 @@
> > +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>.
> > +
> > +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. Channels will be numerated as 1, 2, 4 and 8.
>
> I think it's better to use channel 1-4 and do the translation in the
> driver's channel select method. It means one does not have to worry
> about anybody accidently configuring channel 3 and it also maps
> nicely to the datasheet talking about BAT1-BAT4.
You're not the first one pointing that out... Will fix that in the next
revision.
>
> -- Sebastian
--
Greetings
next prev parent reply other threads:[~2016-07-01 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1bFnWI-0000MX-9R>
2016-06-30 20:05 ` [PATCH v2 0/2] Add support for Smart Battery System Manager Karl-Heinz Schneider
2016-06-30 20:05 ` [PATCH v2 1/2] Documentation: Add sbs-manager device tree node documentation Karl-Heinz Schneider
2016-06-30 22:52 ` Sebastian Reichel
2016-07-01 21:49 ` Karl-Heinz Schneider [this message]
2016-06-30 20:05 ` [PATCH v2 2/2] power: Adds support for Smart Battery System Manager 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=1467409771.9121.38.camel@amnesix \
--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+dt@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).