All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	Mike Turquette <mturquette@linaro.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	Thomas Abraham <thomas.ab@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCHv3 3/4] ARM: exynos: Add exynos3250 compatible to use generic cpufreq driver
Date: Mon, 29 Sep 2014 19:08:04 +0900	[thread overview]
Message-ID: <54292F84.4060906@samsung.com> (raw)
In-Reply-To: <CAKohpokXNEYZBqsKyJDMUCZA7BY_E0=G5eVmTx_cBKvAyoSi9w@mail.gmail.com>

On 09/29/2014 06:58 PM, Viresh Kumar wrote:
> On 25 September 2014 00:05, Chanwoo Choi <cw00.choi@samsung.com> wrote:
>> This patch add exynos3250 compatible string to exynos_cpufreq_matches
>> for supporting generic cpufreq driver on Exynos3250.
>>
>> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
>> Cc: Kukjin Kim <kgene.kim@samsung.com>
>> Cc: Tomasz Figa <tomasz.figa@gmail.com>
>> Cc: Thomas Abraham <thomas.ab@samsung.com>
>> ---
>>  arch/arm/mach-exynos/exynos.c | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
>> index 8923d37..1318d69 100644
>> --- a/arch/arm/mach-exynos/exynos.c
>> +++ b/arch/arm/mach-exynos/exynos.c
>> @@ -285,6 +285,7 @@ static const struct of_device_id exynos_cpufreq_matches[] = {
>>         { .compatible = "samsung,exynos5420", .data = "arm-bL-cpufreq-dt" },
>>         { .compatible = "samsung,exynos5250", .data = "cpufreq-cpu0" },
>>         { .compatible = "samsung,exynos4210", .data = "cpufreq-cpu0" },
>> +       { .compatible = "samsung,exynos3250", .data = "cpufreq-cpu0" },
> 
> cpufreq-cpu0 is renamed to cpufreq-dt now.

As you comment, I checked it on following patch. I'll change it.
https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/cpufreq-dt.c?h=linux-next&id=978027e170fbf428ccb1dedcdaa8f1eb7ced97f4

Thanks,
Chanwoo Choi

WARNING: multiple messages have this Message-ID (diff)
From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 3/4] ARM: exynos: Add exynos3250 compatible to use generic cpufreq driver
Date: Mon, 29 Sep 2014 19:08:04 +0900	[thread overview]
Message-ID: <54292F84.4060906@samsung.com> (raw)
In-Reply-To: <CAKohpokXNEYZBqsKyJDMUCZA7BY_E0=G5eVmTx_cBKvAyoSi9w@mail.gmail.com>

On 09/29/2014 06:58 PM, Viresh Kumar wrote:
> On 25 September 2014 00:05, Chanwoo Choi <cw00.choi@samsung.com> wrote:
>> This patch add exynos3250 compatible string to exynos_cpufreq_matches
>> for supporting generic cpufreq driver on Exynos3250.
>>
>> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
>> Cc: Kukjin Kim <kgene.kim@samsung.com>
>> Cc: Tomasz Figa <tomasz.figa@gmail.com>
>> Cc: Thomas Abraham <thomas.ab@samsung.com>
>> ---
>>  arch/arm/mach-exynos/exynos.c | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
>> index 8923d37..1318d69 100644
>> --- a/arch/arm/mach-exynos/exynos.c
>> +++ b/arch/arm/mach-exynos/exynos.c
>> @@ -285,6 +285,7 @@ static const struct of_device_id exynos_cpufreq_matches[] = {
>>         { .compatible = "samsung,exynos5420", .data = "arm-bL-cpufreq-dt" },
>>         { .compatible = "samsung,exynos5250", .data = "cpufreq-cpu0" },
>>         { .compatible = "samsung,exynos4210", .data = "cpufreq-cpu0" },
>> +       { .compatible = "samsung,exynos3250", .data = "cpufreq-cpu0" },
> 
> cpufreq-cpu0 is renamed to cpufreq-dt now.

As you comment, I checked it on following patch. I'll change it.
https://git.kernel.org/cgit/linux/kernel/git/rafael/linux-pm.git/commit/drivers/cpufreq/cpufreq-dt.c?h=linux-next&id=978027e170fbf428ccb1dedcdaa8f1eb7ced97f4

Thanks,
Chanwoo Choi

  reply	other threads:[~2014-09-29 10:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  7:05 [PATCHv3 0/4] cpufreq: Use cpufreq-cpu0 driver for Exynos3250 Chanwoo Choi
2014-09-25  7:05 ` Chanwoo Choi
2014-09-25  7:05 ` [PATCHv3 1/4] clk: samsung: exynos3250: Add cpu clock configuration data and instaniate cpu clock Chanwoo Choi
2014-09-25  7:05   ` Chanwoo Choi
2014-09-25  7:05 ` [PATCHv3 2/4] clk: samsung: exynos3250: Update clock flags related to CPU to use cpu-clock type Chanwoo Choi
2014-09-25  7:05   ` Chanwoo Choi
2014-09-25  7:05 ` [PATCHv3 3/4] ARM: exynos: Add exynos3250 compatible to use generic cpufreq driver Chanwoo Choi
2014-09-25  7:05   ` Chanwoo Choi
2014-09-29  9:58   ` Viresh Kumar
2014-09-29  9:58     ` Viresh Kumar
2014-09-29 10:08     ` Chanwoo Choi [this message]
2014-09-29 10:08       ` Chanwoo Choi
2014-09-25  7:05 ` [PATCHv3 4/4] ARM: dts: Add CPU OPP and regulator supply property for Exynos3250 Chanwoo Choi
2014-09-25  7:05   ` Chanwoo Choi

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=54292F84.4060906@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=thomas.ab@samsung.com \
    --cc=tomasz.figa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.