From: Rob Herring <robh@kernel.org>
To: Karl-Heinz Schneider <karl-heinz@schneider-inet.de>
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 1/2] Documentation: Add sbs-manager device tree node documentation
Date: Fri, 24 Jun 2016 12:50:14 -0500 [thread overview]
Message-ID: <20160624175014.GA29990@rob-hp-laptop> (raw)
In-Reply-To: <1466622436-27963-2-git-send-email-karl-heinz@schneider-inet.de>
On Wed, Jun 22, 2016 at 09:07:15PM +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 | 58 ++++++++++++++++++++++
> 1 file changed, 58 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..d52b466
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/sbs,sbs-manager.txt
> @@ -0,0 +1,58 @@
> +Binding for sbs-manager
> +
> +Required properties:
> +- compatible: should be "sbs,sbs-manager" or "lltc,ltc1760" if device is a
> + ltc1760.
sbs is not a vendor. What chip is sbs-manager? I suspect you should drop
it and only list specific chips.
> +- reg: integer, i2c address of the device. Should be <0xa>.
> +
> +Optional properties:
> +- sbsm,i2c-retry-count: integer, number of retries for trying to read or write
> + to registers. Default: 1
Seems like a driver setting. Is having a retry in the driver a problem
if the h/w works and never actually needs it?
> +
> +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.
> +
> +Example:
> +
> +batman@0a {
> + compatible = "sbs,sbs-manager";
> + reg = <0x0a>;
> + sbsm,i2c-retry-count = <3>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + channel1@1 {
channel@1
Do we have a standard node name for mux nodes? If not, we should.
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <1>;
> +
> + battery1@0b {
battery@b
> + compatible = "sbs-battery";
This should be an actual battery model. Or all this information is
generic, you don't really need it in DT.
> + reg = <0x0b>;
> + };
> + };
> +
> + channel2@2 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <2>;
> +
> + battery2@0b {
> + compatible = "sbs-battery";
> + reg = <0x0b>;
> + };
> + };
> +
> + channel3@4 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <4>;
> +
> + battery3@0b {
> + compatible = "sbs-battery";
> + reg = <0x0b>;
> + };
> + };
> +};
> --
> 1.9.1
>
next prev parent reply other threads:[~2016-06-24 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 19:07 [PATCH 0/2] Add support for Smart Battery System Manager Karl-Heinz Schneider
2016-06-22 19:07 ` [PATCH 1/2] Documentation: Add sbs-manager device tree node documentation Karl-Heinz Schneider
2016-06-24 17:50 ` Rob Herring [this message]
2016-06-26 5:21 ` Phil Reid
2016-06-26 14:05 ` Rob Herring
2016-06-27 21:10 ` Karl-Heinz Schneider
2016-06-28 1:13 ` Phil Reid
2016-06-28 20:54 ` Rob Herring
2016-06-26 7:10 ` Karl-Heinz Schneider
2016-06-26 22:35 ` Peter Rosin
2016-06-27 15:28 ` Rob Herring
2016-06-27 20:37 ` Karl-Heinz Schneider
2016-06-22 19:07 ` [PATCH 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=20160624175014.GA29990@rob-hp-laptop \
--to=robh@kernel.org \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=karl-heinz@schneider-inet.de \
--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=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 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.