From: Nishanth Menon <nm@ti.com>
To: "Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: [PATCH V7 3/8] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot
Date: Wed, 16 Oct 2013 10:39:03 -0500 [thread overview]
Message-ID: <1381937948-27057-4-git-send-email-nm@ti.com> (raw)
In-Reply-To: <1381937948-27057-1-git-send-email-nm@ti.com>
With OMAP3+ and AM33xx supported SoC having defined CPU device tree
entries with operating-points and clock nodes defined, we can now use
the SoC generic cpufreq-cpu0 driver by registering appropriate device.
Cc: Benoit Cousson <bcousson@baylibre.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>
---
arch/arm/mach-omap2/pm.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c
index e742118..360b2da 100644
--- a/arch/arm/mach-omap2/pm.c
+++ b/arch/arm/mach-omap2/pm.c
@@ -266,7 +266,12 @@ static void __init omap4_init_voltages(void)
static inline void omap_init_cpufreq(void)
{
- struct platform_device_info devinfo = { .name = "omap-cpufreq", };
+ struct platform_device_info devinfo = { };
+
+ if (!of_have_populated_dt())
+ devinfo.name = "omap-cpufreq";
+ else
+ devinfo.name = "cpufreq-cpu0";
platform_device_register_full(&devinfo);
}
@@ -300,10 +305,11 @@ int __init omap2_common_pm_late_init(void)
/* Smartreflex device init */
omap_devinit_smartreflex();
- /* cpufreq dummy device instantiation */
- omap_init_cpufreq();
}
+ /* cpufreq dummy device instantiation */
+ omap_init_cpufreq();
+
#ifdef CONFIG_SUSPEND
suspend_set_ops(&omap_pm_ops);
#endif
--
1.7.9.5
next prev parent reply other threads:[~2013-10-16 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 15:39 [PATCH V7 0/8] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Nishanth Menon
2013-10-16 15:39 ` [PATCH V7 1/8] ARM: OMAP3+: do not register non-dt OPP tables " Nishanth Menon
2013-10-16 15:39 ` [PATCH V7 2/8] ARM: OMAP2+: add missing lateinit hook for calling pm late init Nishanth Menon
2013-10-16 15:39 ` Nishanth Menon [this message]
2013-10-22 15:11 ` [PATCH V7 3/8] ARM: OMAP3+: use cpu0-cpufreq driver in device tree supported boot Tony Lindgren
2013-10-16 15:39 ` [PATCH V7 4/8] ARM: dts: omap5-uevm: add smps123 supply for CPU Nishanth Menon
2013-10-16 15:39 ` [PATCH V7 5/8] ARM: dts: dra7-evm: " Nishanth Menon
[not found] ` <1381937948-27057-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2013-10-16 15:39 ` [PATCH V7 6/8] ARM: dts: OMAP5: Add CPU OPP table Nishanth Menon
2013-10-16 15:39 ` [PATCH V7 7/8] ARM: dts: DRA7: " Nishanth Menon
2013-10-16 15:39 ` [PATCH V7 8/8] ARM: dts: OMAP3: add clock nodes for CPU Nishanth Menon
2013-10-22 15:49 ` [PATCH V7 0/8] ARM: OMAP3+: support cpufreq-cpu0 for device tree boot Benoit Cousson
2013-12-23 9:54 ` Viresh Kumar
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=1381937948-27057-4-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.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=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).