cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Abraham <thomas.ab@samsung.com>
To: cpufreq@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: linux-samsung-soc@vger.kernel.org, mturquette@linaro.org,
	kgene.kim@samsung.com, t.figa@samsung.com,
	l.majewski@samsung.com, viresh.kumar@linaro.org,
	thomas.ab@samsung.com, heiko@sntech.de, cw00.choi@samsung.com
Subject: [PATCH v6 5/6] ARM: Exynos: switch to using generic cpufreq driver for exynos4210/5250
Date: Tue, 17 Jun 2014 20:55:32 +0530	[thread overview]
Message-ID: <1403018733-4187-7-git-send-email-thomas.ab@samsung.com> (raw)
In-Reply-To: <1403018733-4187-1-git-send-email-thomas.ab@samsung.com>

From: Thomas Abraham <thomas.ab@samsung.com>

Remove the platform device instantiation for Exynos4210/5250 cpufreq
driver and add the platform device for generic cpufreq drivers.

Cc: Kukjin Kim <kgene.kim@samsung.com>
Signed-off-by: Thomas Abraham <thomas.ab@samsung.com>
---
 arch/arm/mach-exynos/exynos.c |   15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
index f38cf7c..cfcfe02 100644
--- a/arch/arm/mach-exynos/exynos.c
+++ b/arch/arm/mach-exynos/exynos.c
@@ -181,7 +181,20 @@ void __init exynos_cpuidle_init(void)
 
 void __init exynos_cpufreq_init(void)
 {
-	platform_device_register_simple("exynos-cpufreq", -1, NULL, 0);
+	char *dev_name;
+
+	if (of_machine_is_compatible("samsung,exynos5440"))
+		return;
+	if (of_machine_is_compatible("samsung,exynos5420"))
+		dev_name = "arm-bL-cpufreq-dt";
+	else
+		if (of_machine_is_compatible("samsung,exynos4412") ||
+			of_machine_is_compatible("samsung,exynos4212"))
+			dev_name = "exynos-cpufreq";
+		else
+			dev_name = "cpufreq-cpu0";
+
+	platform_device_register_simple(dev_name, -1, NULL, 0);
 }
 
 void __iomem *sysram_base_addr;
-- 
1.7.9.5

  parent reply	other threads:[~2014-06-17 15:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 15:25 [PATCH v6 0/6] cpufreq: use generic cpufreq drivers for exynos platforms Thomas Abraham
2014-06-17 15:25 ` Thomas Abraham
2014-06-17 15:25 ` [PATCH v6 1/6] clk: samsung: add infrastructure to register cpu clocks Thomas Abraham
2014-06-23  2:08   ` amit daniel kachhap
2014-06-23  7:56     ` Arjun K V
2014-06-24  1:36   ` amit daniel kachhap
2014-06-17 15:25 ` [PATCH v6 2/6] clk: samsung: register exynos5420 apll/kpll configuration data Thomas Abraham
2014-06-17 15:25 ` [PATCH v6 3/6] clk: exynos: use cpu-clock provider type to represent arm clock Thomas Abraham
2014-06-23  2:14   ` amit daniel kachhap
2014-06-17 15:25 ` [PATCH v6 4/6] ARM: dts: Exynos: add cpu nodes, opp and cpu clock configuration data Thomas Abraham
2014-06-17 15:25 ` Thomas Abraham [this message]
2014-06-17 15:25 ` [PATCH v6 6/6] cpufreq: exynos: remove exynos4210/5250 specific cpufreq driver support Thomas Abraham
2014-06-18  7:51 ` [PATCH v6 0/6] cpufreq: use generic cpufreq drivers for exynos platforms Viresh Kumar
2014-06-19  4:13   ` Thomas Abraham

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=1403018733-4187-7-git-send-email-thomas.ab@samsung.com \
    --to=thomas.ab@samsung.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=heiko@sntech.de \
    --cc=kgene.kim@samsung.com \
    --cc=l.majewski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=t.figa@samsung.com \
    --cc=viresh.kumar@linaro.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