From: rklein@nvidia.com (Rhyland Klein)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2 v2] power: bq20z75: Add Device Tree Binding
Date: Fri, 9 Sep 2011 17:47:49 -0700 [thread overview]
Message-ID: <1315615669-8701-2-git-send-email-rklein@nvidia.com> (raw)
In-Reply-To: <1315615669-8701-1-git-send-email-rklein@nvidia.com>
Adding the binding for the TI bq20z75 fuel gadge and the
bq20z75 driver.
Signed-off-by: Rhyland Klein <rklein@nvidia.com>
---
.../bindings/power_supply/ti_bq20z75.txt | 25 ++++++++++++++++++++
1 files changed, 25 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/power_supply/ti_bq20z75.txt
diff --git a/Documentation/devicetree/bindings/power_supply/ti_bq20z75.txt b/Documentation/devicetree/bindings/power_supply/ti_bq20z75.txt
new file mode 100644
index 0000000..3deccfe
--- /dev/null
+++ b/Documentation/devicetree/bindings/power_supply/ti_bq20z75.txt
@@ -0,0 +1,25 @@
+TI bq20z75
+~~~~~~~~~~
+
+Required properties :
+ - compatible : "ti,bq20z75"
+
+Optional properties :
+ - i2c-retry-count : The number of times to retry i2c transactions on i2c
+ IO failure.
+ - poll-retry-count : The number of times to try looking for new status
+ after an external change notification.
+ - battery-detect : The GPIO which is used to detect battery presence.
+ - battery-detect-present : The state of the GPIO when the battery is
+ present ( 0 or 1).
+
+Example:
+
+ bq20z75 at b {
+ compatible = "ti,bq20z75";
+ reg = < 0xb >;
+ i2c-retry-count = <2>;
+ poll-retry-count = <10>;
+ battery-detect = <314>;
+ battery-detect-present = <0>;
+ }
--
1.7.6
next prev parent reply other threads:[~2011-09-10 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 0:47 [PATCH 1/2 v2] power: bq20z75: devicetree init support Rhyland Klein
2011-09-10 0:47 ` Rhyland Klein [this message]
2011-09-12 20:43 ` [PATCH 2/2 v2] power: bq20z75: Add Device Tree Binding Grant Likely
2011-09-12 20:45 ` [PATCH 1/2 v2] power: bq20z75: devicetree init support Grant Likely
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=1315615669-8701-2-git-send-email-rklein@nvidia.com \
--to=rklein@nvidia.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 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).