From: Keerthy <j-keerthy@ti.com>
To: lee.jones@linaro.org, broonie@kernel.org, tony@atomide.com
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, j-keerthy@ti.com
Subject: [PATCH v2 6/8] ARM: dts: AM437X-SK-EVM: Remove redundant regulator compatibles
Date: Mon, 27 Jun 2016 16:31:43 +0530 [thread overview]
Message-ID: <1467025305-13464-7-git-send-email-j-keerthy@ti.com> (raw)
In-Reply-To: <1467025305-13464-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-sk-evm.dts | 5 -----
1 file changed, 5 deletions(-)
diff --git a/arch/arm/boot/dts/am437x-sk-evm.dts b/arch/arm/boot/dts/am437x-sk-evm.dts
index d82dd6e..1b404fd 100644
--- a/arch/arm/boot/dts/am437x-sk-evm.dts
+++ b/arch/arm/boot/dts/am437x-sk-evm.dts
@@ -428,7 +428,6 @@
#interrupt-cells = <2>;
dcdc1: regulator-dcdc1 {
- compatible = "ti,tps65218-dcdc1";
/* VDD_CORE limits min of OPP50 and max of OPP100 */
regulator-name = "vdd_core";
regulator-min-microvolt = <912000>;
@@ -438,7 +437,6 @@
};
dcdc2: regulator-dcdc2 {
- compatible = "ti,tps65218-dcdc2";
/* VDD_MPU limits min of OPP50 and max of OPP_NITRO */
regulator-name = "vdd_mpu";
regulator-min-microvolt = <912000>;
@@ -448,7 +446,6 @@
};
dcdc3: regulator-dcdc3 {
- compatible = "ti,tps65218-dcdc3";
regulator-name = "vdds_ddr";
regulator-min-microvolt = <1500000>;
regulator-max-microvolt = <1500000>;
@@ -457,7 +454,6 @@
};
dcdc4: regulator-dcdc4 {
- compatible = "ti,tps65218-dcdc4";
regulator-name = "v3_3d";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
@@ -466,7 +462,6 @@
};
ldo1: regulator-ldo1 {
- compatible = "ti,tps65218-ldo1";
regulator-name = "v1_8d";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
--
1.9.1
next prev parent reply other threads:[~2016-06-27 11:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 11:01 [PATCH v2 0/8] mfd/regulator: tps65218: Clean ups Keerthy
2016-06-27 11:01 ` [PATCH v2 1/8] mfd: tps65218: Remove redundant read wrapper Keerthy
[not found] ` <1467025305-13464-2-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-06-27 11:51 ` kbuild test robot
2016-06-27 12:20 ` kbuild test robot
2016-06-27 12:23 ` Lee Jones
2016-06-27 14:30 ` Keerthy
2016-06-27 11:01 ` [PATCH v2 2/8] Documentation: regulator: tps65218: Update examples Keerthy
2016-06-27 11:01 ` [PATCH v2 3/8] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate Keerthy
[not found] ` <1467025305-13464-4-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-06-27 12:23 ` Lee Jones
2016-06-27 11:01 ` [PATCH v2 4/8] regulator: tps65218: Remove all the compatibles Keerthy
2016-06-27 11:01 ` [PATCH v2 5/8] ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles Keerthy
2016-06-27 11:01 ` Keerthy [this message]
2016-06-27 11:01 ` [PATCH v2 7/8] ARM: dts: AM437X-CM-T43: " Keerthy
2016-06-27 11:01 ` [PATCH v2 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=1467025305-13464-7-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=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).