From: Keerthy <j-keerthy@ti.com>
To: tony@atomide.com
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, lee.jones@linaro.org,
broonie@kernel.org, robh+dt@kernel.org, j-keerthy@ti.com
Subject: [PATCH 1/4] ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles
Date: Mon, 4 Jul 2016 15:25:10 +0530 [thread overview]
Message-ID: <1467626113-15705-2-git-send-email-j-keerthy@ti.com> (raw)
In-Reply-To: <1467626113-15705-1-git-send-email-j-keerthy@ti.com>
With the device tree parsing using the regulator framework
there is a no longer a need for separate compatibles for
individual regulator nodes. Hence removing them all.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
arch/arm/boot/dts/am437x-gp-evm.dts | 6 ------
1 file changed, 6 deletions(-)
diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts b/arch/arm/boot/dts/am437x-gp-evm.dts
index 1cecc09..cafa974 100644
--- a/arch/arm/boot/dts/am437x-gp-evm.dts
+++ b/arch/arm/boot/dts/am437x-gp-evm.dts
@@ -513,7 +513,6 @@
#interrupt-cells = <2>;
dcdc1: regulator-dcdc1 {
- compatible = "ti,tps65218-dcdc1";
regulator-name = "vdd_core";
regulator-min-microvolt = <912000>;
regulator-max-microvolt = <1144000>;
@@ -522,7 +521,6 @@
};
dcdc2: regulator-dcdc2 {
- compatible = "ti,tps65218-dcdc2";
regulator-name = "vdd_mpu";
regulator-min-microvolt = <912000>;
regulator-max-microvolt = <1378000>;
@@ -531,7 +529,6 @@
};
dcdc3: regulator-dcdc3 {
- compatible = "ti,tps65218-dcdc3";
regulator-name = "vdcdc3";
regulator-min-microvolt = <1500000>;
regulator-max-microvolt = <1500000>;
@@ -546,7 +543,6 @@
};
dcdc5: regulator-dcdc5 {
- compatible = "ti,tps65218-dcdc5";
regulator-name = "v1_0bat";
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <1000000>;
@@ -558,7 +554,6 @@
};
dcdc6: regulator-dcdc6 {
- compatible = "ti,tps65218-dcdc6";
regulator-name = "v1_8bat";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
@@ -570,7 +565,6 @@
};
ldo1: regulator-ldo1 {
- compatible = "ti,tps65218-ldo1";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
regulator-boot-on;
--
1.9.1
next prev parent reply other threads:[~2016-07-04 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 9:55 [PATCH 0/4] ARM: dts: TPS65218: Clean ups Keerthy
2016-07-04 9:55 ` Keerthy [this message]
2016-07-04 9:55 ` [PATCH 2/4] ARM: dts: AM437X-SK-EVM: Remove redundant regulator compatibles Keerthy
2016-07-04 9:55 ` [PATCH 3/4] ARM: dts: AM437X-CM-T43: " Keerthy
2016-07-04 9:55 ` [PATCH 4/4] ARM: dts: AM43X-EPOS-EVM: " Keerthy
[not found] ` <1467626113-15705-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-08-26 14:51 ` [PATCH 0/4] ARM: dts: TPS65218: Clean ups Tony Lindgren
[not found] ` <20160826145059.ar37v7rbtcrah5yu-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-08-26 16:11 ` Keerthy
[not found] ` <6b1ba3c8-dcb5-4d9d-d231-734735d88eb9-l0cyMroinI0@public.gmane.org>
2016-08-30 9:53 ` Lee Jones
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=1467626113-15705-2-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-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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).