From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 4/9] cpufreq: omap: Use generic platdev driver
Date: Fri, 22 Apr 2016 16:58:42 +0530 [thread overview]
Message-ID: <a9cadb022a3be97ec43983d524a6ab0378829441.1461324267.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1461324267.git.viresh.kumar@linaro.org>
The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform
device now, reuse that and remove similar code from platform code.
Cc: Tony Lindgren <tony@atomide.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Acked-by: Arnd Bergmann <arnd@arndb.de>
---
arch/arm/mach-omap2/pm.c | 7 ++-----
drivers/cpufreq/cpufreq-dt-platdev.c | 5 +++++
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c
index 58920bc8807b..2f7b11da7d5d 100644
--- a/arch/arm/mach-omap2/pm.c
+++ b/arch/arm/mach-omap2/pm.c
@@ -277,13 +277,10 @@ static void __init omap4_init_voltages(void)
static inline void omap_init_cpufreq(void)
{
- struct platform_device_info devinfo = { };
+ struct platform_device_info devinfo = { .name = "omap-cpufreq" };
if (!of_have_populated_dt())
- devinfo.name = "omap-cpufreq";
- else
- devinfo.name = "cpufreq-dt";
- platform_device_register_full(&devinfo);
+ platform_device_register_full(&devinfo);
}
static int __init omap2_common_pm_init(void)
diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
index 3843314389c7..4e525f6ec59f 100644
--- a/drivers/cpufreq/cpufreq-dt-platdev.c
+++ b/drivers/cpufreq/cpufreq-dt-platdev.c
@@ -28,6 +28,11 @@ static const struct of_device_id machines[] __initconst = {
{ .compatible = "samsung,exynos5420", },
{ .compatible = "samsung,exynos5800", },
#endif
+
+ { .compatible = "ti,omap2", },
+ { .compatible = "ti,omap3", },
+ { .compatible = "ti,omap4", },
+ { .compatible = "ti,omap5", },
};
static int __init cpufreq_dt_platdev_init(void)
--
2.7.1.410.g6faf27b
next prev parent reply other threads:[~2016-04-22 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1461324267.git.viresh.kumar@linaro.org>
2016-04-22 11:28 ` [PATCH V2 2/9] cpufreq: berlin: Use generic platdev driver Viresh Kumar
2016-04-22 11:28 ` [PATCH V2 3/9] cpufreq: imx: " Viresh Kumar
2016-04-22 11:28 ` Viresh Kumar [this message]
2016-04-22 11:28 ` [PATCH V2 5/9] cpufreq: rockchip: " Viresh Kumar
2016-04-22 13:58 ` Heiko Stübner
2016-04-22 11:28 ` [PATCH V2 6/9] cpufreq: shmobile: " Viresh Kumar
2016-04-22 11:28 ` [PATCH V2 7/9] cpufreq: sunxi: " Viresh Kumar
2016-04-22 11:28 ` [PATCH V2 8/9] cpufreq: zynq: " 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=a9cadb022a3be97ec43983d524a6ab0378829441.1461324267.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).