From: Keerthy <j-keerthy@ti.com>
To: broonie@kernel.org, tony@atomide.com, robh+dt@kernel.org,
mark.rutland@arm.com, lee.jones@linaro.org
Cc: nm@ti.com, devicetree@vger.kernel.org, nikita@compulab.co.il,
j-keerthy@ti.com, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/8] Documentation: regulator: tps65218: Update examples
Date: Wed, 11 May 2016 11:18:05 +0530 [thread overview]
Message-ID: <1462945691-904-3-git-send-email-j-keerthy@ti.com> (raw)
In-Reply-To: <1462945691-904-1-git-send-email-j-keerthy@ti.com>
This updates the device tree according to the preferred way of parsing
the nodes using the regulator framework.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
.../devicetree/bindings/regulator/tps65218.txt | 87 ++++++++++++++++++----
1 file changed, 71 insertions(+), 16 deletions(-)
diff --git a/Documentation/devicetree/bindings/regulator/tps65218.txt b/Documentation/devicetree/bindings/regulator/tps65218.txt
index fccc1d2..8d3d919 100644
--- a/Documentation/devicetree/bindings/regulator/tps65218.txt
+++ b/Documentation/devicetree/bindings/regulator/tps65218.txt
@@ -1,23 +1,78 @@
TPS65218 family of regulators
Required properties:
-For tps65218 regulators/LDOs
-- compatible:
- - "ti,tps65218-dcdc1" for DCDC1
- - "ti,tps65218-dcdc2" for DCDC2
- - "ti,tps65218-dcdc3" for DCDC3
- - "ti,tps65218-dcdc4" for DCDC4
- - "ti,tps65218-dcdc5" for DCDC5
- - "ti,tps65218-dcdc6" for DCDC6
- - "ti,tps65218-ldo1" for LDO1
-
-Optional properties:
-- Any optional property defined in bindings/regulator/regulator.txt
+- compatible: "ti,tps65218"
+- reg: I2C slave address
+- list of regulators provided by this controller, must be named
+ after their hardware counterparts: dcdc[1-6] and ldo1
+- This is the list of child nodes that specify the regulator
+ initialization data for defined regulators. Not all regulators for the given
+ device need to be present. The definition for each of these nodes is defined
+ using the standard binding for regulators found at
+ Documentation/devicetree/bindings/regulator/regulator.txt.
+
+ The valid names for regulators are:
+ tps65217: regulator-dcdc1, regulator-dcdc2, regulator-dcdc3, regulator-dcdc4,
+ regulator-dcdc5, regulator-dcdc6, regulator-ldo1, regulator-ls3
+ Each regulator is defined using the standard binding for regulators.
Example:
+tps65218: tps65218@24 {
+ reg = <0x24>;
+ compatible = "ti,tps65218";
+ interrupts = <GIC_SPI 7 IRQ_TYPE_NONE>; /* NMIn */
+ interrupt-controller;
+ #interrupt-cells = <2>;
+
+ dcdc1: regulator-dcdc1 {
+ regulator-name = "vdd_core";
+ regulator-min-microvolt = <912000>;
+ regulator-max-microvolt = <1144000>;
+ regulator-boot-on;
+ regulator-always-on;
+ };
+
+ dcdc2: regulator-dcdc2 {
+ regulator-name = "vdd_mpu";
+ regulator-min-microvolt = <912000>;
+ regulator-max-microvolt = <1378000>;
+ regulator-boot-on;
+ regulator-always-on;
+ };
+
+ dcdc3: regulator-dcdc3 {
+ regulator-name = "vdcdc3";
+ regulator-min-microvolt = <1500000>;
+ regulator-max-microvolt = <1500000>;
+ regulator-boot-on;
+ regulator-always-on;
+ };
+
+ dcdc5: regulator-dcdc5 {
+ regulator-name = "v1_0bat";
+ regulator-min-microvolt = <1000000>;
+ regulator-max-microvolt = <1000000>;
+ regulator-boot-on;
+ regulator-always-on;
+ };
+
+ dcdc6: regulator-dcdc6 {
+ regulator-name = "v1_8bat";
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+ regulator-boot-on;
+ regulator-always-on;
+ };
+
+ ldo1: regulator-ldo1 {
+ regulator-min-microvolt = <1800000>;
+ regulator-max-microvolt = <1800000>;
+ regulator-boot-on;
+ regulator-always-on;
+ };
- xyz: regulator@0 {
- compatible = "ti,tps65218-dcdc1";
- regulator-min-microvolt = <1000000>;
- regulator-max-microvolt = <3000000>;
+ ls3: regulator-ls3 {
+ regulator-min-microvolt = <100000>;
+ regulator-max-microvolt = <1000000>;
};
+};
--
1.9.1
next prev parent reply other threads:[~2016-05-11 5:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 5:48 [PATCH 0/8] regulator: tps65218: Clean ups Keerthy
2016-05-11 5:48 ` [PATCH 1/8] mfd: tps65218: Remove redundant read wrapper Keerthy
2016-05-11 5:48 ` Keerthy [this message]
[not found] ` <1462945691-904-3-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-05-16 14:48 ` [PATCH 2/8] Documentation: regulator: tps65218: Update examples Rob Herring
2016-05-17 3:22 ` Keerthy
2016-05-11 5:48 ` [PATCH 3/8] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate Keerthy
2016-06-03 11:08 ` Keerthy
2016-06-06 9:00 ` Lee Jones
2016-06-08 15:50 ` Lee Jones
2016-06-08 16:09 ` Keerthy
2016-05-11 5:48 ` [PATCH 4/8] regulator: tps65218: Remove all the compatibles Keerthy
2016-05-11 10:21 ` Mark Brown
2016-05-11 5:48 ` [PATCH 5/8] ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles Keerthy
[not found] ` <1462945691-904-6-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-05-12 17:08 ` Tony Lindgren
2016-05-11 5:48 ` [PATCH 6/8] ARM: dts: AM437X-SK-EVM: " Keerthy
2016-05-11 5:48 ` [PATCH 7/8] ARM: dts: AM437X-CM-T43: " Keerthy
2016-05-11 5:48 ` [PATCH 8/8] ARM: dts: AM43X-EPOS-EVM: " 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=1462945691-904-3-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nikita@compulab.co.il \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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).