From: Nishanth Menon <nm@ti.com>
To: linux-omap@vger.kernel.org
Cc: devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Benoît Cousson" <b-cousson@ti.com>,
"Tony Lindgren" <tony@atomide.com>,
"Paul Walmsley" <paul@pwsan.com>,
"Kevin Hilman" <khilman@deeprootsystems.com>,
"Mike Turquette" <mturquette@linaro.org>,
"Nishanth Menon" <nm@ti.com>
Subject: [PATCH V4 4/6] ARM: dts: AM33XX: add clock nodes for CPU
Date: Fri, 12 Apr 2013 17:54:36 -0500 [thread overview]
Message-ID: <1365807278-554-5-git-send-email-nm@ti.com> (raw)
In-Reply-To: <1365807278-554-1-git-send-email-nm@ti.com>
AM33XX based platforms use dpll_mpu clock. Add same to common dtsi
and remove the dummy clock node entry as AM33XX platform supports
only device tree based boot.
Cc: Benoit Cousson <b-cousson@ti.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Paul Walmsley <paul@pwsan.com>
Cc: Tony Lindgren <tony@atomide.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
---
RFC of this patch was discussed in http://marc.info/?t=136370325600009&r=1&w=2
along with the detailed context as to why this is an intermediate step.
previous revisions of cpufreq-cpu0 support do not use this approach.
[Probably belongs to Benoit/Tony/Paul tree?]
arch/arm/boot/dts/am33xx.dtsi | 7 +++++++
arch/arm/mach-omap2/cclock33xx_data.c | 1 -
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index df62830..3aed044 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@@ -42,6 +42,8 @@
275000 1125000
>;
voltage-tolerance = <2>; /* 2 percentage */
+ clocks = <&dpll_mpu>;
+ clock-names = "cpu";
clock-latency = <300000>; /* From omap-cpufreq driver */
};
};
@@ -89,6 +91,11 @@
reg = <0x48200000 0x1000>;
};
+ dpll_mpu: dpll_mpu {
+ #clock-cells = <0>;
+ compatible = "ti,omap-clock";
+ };
+
gpio0: gpio@44e07000 {
compatible = "ti,omap4-gpio";
ti,hwmods = "gpio1";
diff --git a/arch/arm/mach-omap2/cclock33xx_data.c b/arch/arm/mach-omap2/cclock33xx_data.c
index 7f091c8..8be6832 100644
--- a/arch/arm/mach-omap2/cclock33xx_data.c
+++ b/arch/arm/mach-omap2/cclock33xx_data.c
@@ -852,7 +852,6 @@ static struct omap_clk am33xx_clks[] = {
CLK(NULL, "dpll_core_m5_ck", &dpll_core_m5_ck, CK_AM33XX),
CLK(NULL, "dpll_core_m6_ck", &dpll_core_m6_ck, CK_AM33XX),
CLK(NULL, "dpll_mpu_ck", &dpll_mpu_ck, CK_AM33XX),
- CLK("cpu0", NULL, &dpll_mpu_ck, CK_AM33XX),
CLK(NULL, "dpll_mpu_m2_ck", &dpll_mpu_m2_ck, CK_AM33XX),
CLK(NULL, "dpll_ddr_ck", &dpll_ddr_ck, CK_AM33XX),
CLK(NULL, "dpll_ddr_m2_ck", &dpll_ddr_m2_ck, CK_AM33XX),
--
1.7.9.5
next prev parent reply other threads:[~2013-04-12 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 22:54 [PATCH V4 0/6] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Nishanth Menon
[not found] ` <1365807278-554-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2013-04-12 22:54 ` [PATCH V4 1/6] clk: OMAP: introduce device tree binding to kernel clock data Nishanth Menon
2013-04-12 23:31 ` Tony Lindgren
[not found] ` <20130412233142.GE10155-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-04-12 23:39 ` Nishanth Menon
2013-04-13 17:22 ` Tony Lindgren
[not found] ` <20130413172210.GM10155-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2013-04-14 21:19 ` Nishanth Menon
2013-04-24 16:28 ` Mike Turquette
2013-04-25 7:01 ` Rajendra Nayak
2013-04-15 16:22 ` Stephen Warren
2013-04-15 18:43 ` Nishanth Menon
2013-04-12 22:54 ` [PATCH V4 3/6] ARM: dts: OMAP4: add clock nodes for CPU Nishanth Menon
2013-04-12 22:54 ` [PATCH V4 2/6] ARM: dts: OMAP3: " Nishanth Menon
2013-04-12 22:54 ` Nishanth Menon [this message]
2013-04-12 22:54 ` [PATCH V4 5/6] ARM: OMAP2+: AM33XX: add lateinit hook for calling pm late init Nishanth Menon
2013-04-12 22:54 ` [PATCH V4 6/6] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot Nishanth Menon
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=1365807278-554-5-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=paul@pwsan.com \
--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).