From: Philipp Zabel <p.zabel@pengutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
Krystian Garbaciak <krystian.garbaciak@diasemi.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
devicetree@vger.kernel.org
Subject: [PATCH v3 5/6] Documentation: Add device tree bindings for DA9063 PMIC
Date: Mon, 29 Jul 2013 19:00:46 +0200 [thread overview]
Message-ID: <1375117247-6376-6-git-send-email-p.zabel@pengutronix.de> (raw)
In-Reply-To: <1375117247-6376-1-git-send-email-p.zabel@pengutronix.de>
This patch adds device tree binding documentation for the Dialog Semiconductors
DA9063 PMIC and its regulator nodes.
Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Cc: devicetree@vger.kernel.org
---
.../devicetree/bindings/mfd/da9063-i2c.txt | 68 ++++++++++++++++++++++
1 file changed, 68 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/da9063-i2c.txt
diff --git a/Documentation/devicetree/bindings/mfd/da9063-i2c.txt b/Documentation/devicetree/bindings/mfd/da9063-i2c.txt
new file mode 100644
index 0000000..776b662
--- /dev/null
+++ b/Documentation/devicetree/bindings/mfd/da9063-i2c.txt
@@ -0,0 +1,68 @@
+* Dialog DA9063 Power Management Integrated Circuit (PMIC)
+
+Required properties:
+- compatible : Should be "dialog,da9063"
+- interrupt-parent : phandle pointing to the interrupt controller
+- interrupts : interrupt number and flags in interrupt-parent
+ for the chip IRQ line. Interrupt bindings are documented here:
+ Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
+
+Sub-nodes:
+- regulators : Contain the regulator nodes. The DA9063 regulators are
+ bound using their names as listed below:
+
+ bcore1 : regulator BCORE1
+ bcore2 : regulator BCORE2
+ bpro : regulator BPRO
+ bmem : regulator BMEM
+ bio : regulator BIO
+ bperi : regulator BPERI
+ ldo1 : regulator LDO1
+ ldo2 : regulator LDO4
+ ldo3 : regulator LDO3
+ ldo4 : regulator LDO4
+ ldo5 : regulator LDO5
+ ldo6 : regulator LDO6
+ ldo7 : regulator LDO7
+ ldo8 : regulator LDO8
+ ldo9 : regulator LDO9
+ ldo10 : regulator LDO10
+ ldo11 : regulator LDO11
+
+ The PMIC can also be configured to merge both bcore1/2 into a single
+ supply and to merge bmem and bio into a single supply. In this case,
+ the following regulators are bound instead of bcore1/2 and bpro/bmem:
+
+ bcores-merged : merged regulators BCORE1, BCORE2
+ bmem-bio-merged : merged regulators BMEM, BIO
+
+ See Documentation/devicetree/bindings/regulator/regulator.txt for
+ binding details of individual regulator device nodes.
+
+
+Examples:
+
+&i2c1 {
+ status = "okay";
+
+ pmic@58 {
+ compatible = "dialog,da9063";
+ reg = <0x58>;
+ interrupt-parent = <&gpio4>;
+ interrupts = <17 0x8>; /* active-low GPIO4_17 */
+
+ regulators {
+ bcore1 {
+ regulator-min-microvolt = <300000>;
+ regulator-max-microvolt = <1570000>;
+ };
+
+ bcore2 {
+ regulator-min-microvolt = <300000>;
+ regulator-max-microvolt = <1570000>;
+ };
+
+ /* ... */
+ };
+ };
+};
--
1.8.3.2
parent reply other threads:[~2013-07-29 17:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1375117247-6376-1-git-send-email-p.zabel@pengutronix.de>]
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=1375117247-6376-6-git-send-email-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krystian.garbaciak@diasemi.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).