devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"Opensource [Steve Twiss]"
	<stwiss.opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: [PATCH] Documentation: Add device tree bindings for DA9063 PMIC
Date: Wed, 19 Mar 2014 10:03:56 +0100	[thread overview]
Message-ID: <1395219836-25018-1-git-send-email-p.zabel@pengutronix.de> (raw)

This patch adds device tree binding documentation for the Dialog Semiconductors
DA9063 PMIC and its regulator nodes.

Signed-off-by: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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.9.0

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

                 reply	other threads:[~2014-03-19  9:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1395219836-25018-1-git-send-email-p.zabel@pengutronix.de \
    --to=p.zabel-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=stwiss.opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.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).