From: J Keerthy <j-keerthy@ti.com>
To: devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: j-keerthy@ti.com, grant.likely@secretlab.ca,
rob.herring@calxeda.com, rob@landley.net, gg@slimlogic.co.uk,
broonie@opensource.wolfsonmicro.com, sameo@linux.intel.com,
liam.r.girdwood@intel.com
Subject: [PATCH 1/4] documentation: add palmas dts definition
Date: Wed, 20 Feb 2013 09:30:15 +0530 [thread overview]
Message-ID: <1361332815-2348-1-git-send-email-j-keerthy@ti.com> (raw)
From: Graeme Gregory <gg@slimlogic.co.uk>
Add the DTS definition for the palmas device including the MFD children.
Signed-off-by: Graeme Gregory <gg@slimlogic.co.uk>
[j-keerthy@ti.com: changed the DT node property names to follow the
convention]
Signed-off-by: J Keerthy <j-keerthy@ti.com>
---
Documentation/devicetree/bindings/mfd/palmas.txt | 67 ++++++++++++++++++++++
1 files changed, 67 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/palmas.txt
diff --git a/Documentation/devicetree/bindings/mfd/palmas.txt b/Documentation/devicetree/bindings/mfd/palmas.txt
new file mode 100644
index 0000000..5fa922e
--- /dev/null
+++ b/Documentation/devicetree/bindings/mfd/palmas.txt
@@ -0,0 +1,67 @@
+Texas Instruments Palmas family
+
+The Palmas familly are Integrated Power Management Chips.
+These chips are connected to an i2c bus.
+
+
+Required properties:
+- compatible : Must be "ti,palmas";
+ For Integrated power-management in the palmas series, twl6035, twl6037,
+ tps65913
+- interrupts : This i2c device has an IRQ line connected to the main SoC
+- interrupt-controller : Since the palmas support several interrupts internally,
+ it is considered as an interrupt controller cascaded to the SoC one.
+- #interrupt-cells = <1>;
+- interrupt-parent : The parent interrupt controller.
+
+Optional node:
+- Child nodes contain in the palmas. The palmas family is made of several
+ variants that support a different number of features.
+ The child nodes will thus depend of the capability of the variant.
+- mux-pad1 if a value is given it will be used for the pad1 mux
+- mux-pad2 if a value us given it will be used for the pad2 mux
+- power-ctrl if a value is given it will be written to the POWER_CTRL register
+
+Example:
+/*
+ * Integrated Power Management Chip Palmas
+ */
+palmas@48 {
+ compatible = "ti,palmas";
+ reg = <0x48>;
+ interrupts = <39>; /* IRQ_SYS_1N cascaded to gic */
+ interrupt-controller;
+ #interrupt-cells = <1>;
+ interrupt-parent = <&gic>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ ti,mux-pad1 = <0x00>;
+ ti,mux-pad2 = <0x00>;
+ ti,power-ctrl = <0x03>;
+
+ palmas_pmic {
+ compatible = "ti,palmas_pmic";
+ regulators {
+ smps12_reg: smps12 {
+ regulator-min-microvolt = < 600000>;
+ regulator-max-microvolt = <1500000>;
+ regulator-always-on;
+ regulator-boot-on;
+ ti,warm-sleep = <0>;
+ ti,roof-floor = <0>;
+ ti,mode-sleep = <0>;
+ ti,warm-reset = <0>;
+ ti,tstep = <0>;
+ ti,vsel = <0>;
+ };
+ };
+ ti,ldo6-vibrator = <0>;
+ };
+
+ palmas_rtc {
+ compatible = "ti,palmas_rtc";
+ interrupts = <8 9>;
+ reg = <0>;
+ };
+};
--
1.7.5.4
next reply other threads:[~2013-02-20 4:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 4:00 J Keerthy [this message]
2013-02-20 11:26 ` [PATCH 1/4] documentation: add palmas dts definition Mark Brown
2013-02-20 13:49 ` J, KEERTHY
2013-02-27 18:16 ` Stephen Warren
2013-03-02 4:07 ` Mark Brown
2013-02-25 8:55 ` J, KEERTHY
-- strict thread matches above, loose matches on Subject: below --
2013-02-18 5:11 J Keerthy
2013-02-27 18:32 ` Stephen Warren
2013-02-28 8:52 ` Laxman Dewangan
2013-02-28 9:58 ` Graeme Gregory
2013-02-28 10:27 ` Laxman Dewangan
2013-02-28 10:57 ` Graeme Gregory
2013-02-28 11:21 ` Graeme Gregory
2013-02-28 19:01 ` Stephen Warren
2013-02-28 18:58 ` Stephen Warren
[not found] ` <512F1ADF.90906-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-02-28 18:51 ` Stephen Warren
2013-02-28 12:09 ` J, KEERTHY
2013-02-28 19:07 ` Stephen Warren
2013-03-01 2:24 ` J, KEERTHY
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=1361332815-2348-1-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=liam.r.girdwood@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--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).