From: Kukjin Kim <kgene.kim@samsung.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Jonghwan Choi <jhbird.choi@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Kukjin Kim <kgene.kim@samsung.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Jonghwan Choi <jhbird.choi@gmail.com>
Subject: Re: [PATCH v3] cpufreq: exynos: Fix the compile error
Date: Sat, 17 May 2014 08:26:53 +0900 [thread overview]
Message-ID: <53769EBD.2000201@samsung.com> (raw)
In-Reply-To: <CAKohponFCpNThX1m9n+_96vN=WqN5zqA-+GWMLMLO_z-3p5okA@mail.gmail.com>
On 05/16/14 20:07, Viresh Kumar wrote:
> On 16 May 2014 15:48, Jonghwan Choi<jhbird.choi@samsung.com> wrote:
>> Commit 7da83a80 ("ARM: EXYNOS: Migrate Exynos specific macros from plat to mach") which lands in samsung tree causes build breakage
>> for cpufreq-exynos like following:
>>
>> drivers/cpufreq/exynos-cpufreq.c: In function 'exynos_cpufreq_probe':
>> drivers/cpufreq/exynos-cpufreq.c:166:2: error: implicit declaration of function 'soc_is_exynos4210'
>> [-Werror=implicit-function-declaration]
>> drivers/cpufreq/exynos-cpufreq.c:168:2: error: implicit declaration of function 'soc_is_exynos4212'
>> [-Werror=implicit-function-declaration]
>> drivers/cpufreq/exynos-cpufreq.c:168:2: error: implicit declaration of function 'soc_is_exynos4412'
>> [-Werror=implicit-function-declaration]
>> drivers/cpufreq/exynos-cpufreq.c:170:2: error: implicit declaration of function 'soc_is_exynos5250'
>> [-Werror=implicit-function-declaration]
>> cc1: some warnings being treated as errors
>> make[2]: *** [drivers/cpufreq/exynos-cpufreq.o] Error 1
>> make[2]: *** Waiting for unfinished jobs....
>> drivers/cpufreq/exynos4x12-cpufreq.c: In function 'exynos4x12_set_clkdiv':
>> drivers/cpufreq/exynos4x12-cpufreq.c:118:2: error: implicit declaration of function 'soc_is_exynos4212'
>> [-Werror=implicit-function-declaration]
>> cc1: some warnings being treated as errors
>> make[2]: *** [drivers/cpufreq/exynos4x12-cpufreq.o] Error 1
>> make[1]: *** [drivers/cpufreq] Error 2
>
> Blank line here..
>
>> This fixes above error with getting SoC information via of_machine_is_compatible() instead of soc_is_exynosXXXX().
>>
>> Signed-off-by: Jonghwan Choi<jhbird.choi@samsung.com>
>> ---
>> drivers/cpufreq/exynos-cpufreq.c | 20 +++++++++++++++++---
>> drivers/cpufreq/exynos-cpufreq.h | 8 ++++++++
>> drivers/cpufreq/exynos4x12-cpufreq.c | 11 ++++-------
>> 3 files changed, 29 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c
>> index f99cfe2..9aecffef 100644
>> --- a/drivers/cpufreq/exynos-cpufreq.c
>> +++ b/drivers/cpufreq/exynos-cpufreq.c
>> @@ -17,6 +17,7 @@
>> #include<linux/regulator/consumer.h>
>> #include<linux/cpufreq.h>
>> #include<linux/platform_device.h>
>> +#include<linux/of.h>
>>
>> #include<plat/cpu.h>
>>
>> @@ -163,11 +164,24 @@ static int exynos_cpufreq_probe(struct platform_device *pdev)
>> if (!exynos_info)
>> return -ENOMEM;
>>
>> - if (soc_is_exynos4210())
>> + if (of_machine_is_compatible("samsung,exynos4210")) {
>> + exynos_info->type = EXYNOS_SOC_4210;
>> + } else if (of_machine_is_compatible("samsung,exynos4212")) {
>> + exynos_info->type = EXYNOS_SOC_4212;
>> + } else if (of_machine_is_compatible("samsung,exynos4412")) {
>> + exynos_info->type = EXYNOS_SOC_4212;
>
> 4412 ?
>
Yes, I will fix when I apply.
>> + } else if (of_machine_is_compatible("samsung,exynos5250")) {
>> + exynos_info->type = EXYNOS_SOC_5250;
>> + } else {
>> + pr_err("%s: Unknown SoC type\n", __func__);
>> + return -ENODEV;
>> + }
>> +
>> + if (exynos_info->type == EXYNOS_SOC_4210)
>> ret = exynos4210_cpufreq_init(exynos_info);
>> - else if (soc_is_exynos4212() || soc_is_exynos4412())
>> + else if (exynos_info->type == EXYNOS_SOC_4212 || exynos_info->type == EXYNOS_SOC_4412)
>> ret = exynos4x12_cpufreq_init(exynos_info);
>> - else if (soc_is_exynos5250())
>> + else if (exynos_info->type == EXYNOS_SOC_5250)
>> ret = exynos5250_cpufreq_init(exynos_info);
>> else
>> return 0;
>
> Do this in the first if/else only..
Probably, you mean following in above?
>> - if (soc_is_exynos4210())
I've applied this with fixing typo you mentioned just now, if any
concerns, please kindly let me know.
Thanks,
Kukjin
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] cpufreq: exynos: Fix the compile error
Date: Sat, 17 May 2014 08:26:53 +0900 [thread overview]
Message-ID: <53769EBD.2000201@samsung.com> (raw)
In-Reply-To: <CAKohponFCpNThX1m9n+_96vN=WqN5zqA-+GWMLMLO_z-3p5okA@mail.gmail.com>
On 05/16/14 20:07, Viresh Kumar wrote:
> On 16 May 2014 15:48, Jonghwan Choi<jhbird.choi@samsung.com> wrote:
>> Commit 7da83a80 ("ARM: EXYNOS: Migrate Exynos specific macros from plat to mach") which lands in samsung tree causes build breakage
>> for cpufreq-exynos like following:
>>
>> drivers/cpufreq/exynos-cpufreq.c: In function 'exynos_cpufreq_probe':
>> drivers/cpufreq/exynos-cpufreq.c:166:2: error: implicit declaration of function 'soc_is_exynos4210'
>> [-Werror=implicit-function-declaration]
>> drivers/cpufreq/exynos-cpufreq.c:168:2: error: implicit declaration of function 'soc_is_exynos4212'
>> [-Werror=implicit-function-declaration]
>> drivers/cpufreq/exynos-cpufreq.c:168:2: error: implicit declaration of function 'soc_is_exynos4412'
>> [-Werror=implicit-function-declaration]
>> drivers/cpufreq/exynos-cpufreq.c:170:2: error: implicit declaration of function 'soc_is_exynos5250'
>> [-Werror=implicit-function-declaration]
>> cc1: some warnings being treated as errors
>> make[2]: *** [drivers/cpufreq/exynos-cpufreq.o] Error 1
>> make[2]: *** Waiting for unfinished jobs....
>> drivers/cpufreq/exynos4x12-cpufreq.c: In function 'exynos4x12_set_clkdiv':
>> drivers/cpufreq/exynos4x12-cpufreq.c:118:2: error: implicit declaration of function 'soc_is_exynos4212'
>> [-Werror=implicit-function-declaration]
>> cc1: some warnings being treated as errors
>> make[2]: *** [drivers/cpufreq/exynos4x12-cpufreq.o] Error 1
>> make[1]: *** [drivers/cpufreq] Error 2
>
> Blank line here..
>
>> This fixes above error with getting SoC information via of_machine_is_compatible() instead of soc_is_exynosXXXX().
>>
>> Signed-off-by: Jonghwan Choi<jhbird.choi@samsung.com>
>> ---
>> drivers/cpufreq/exynos-cpufreq.c | 20 +++++++++++++++++---
>> drivers/cpufreq/exynos-cpufreq.h | 8 ++++++++
>> drivers/cpufreq/exynos4x12-cpufreq.c | 11 ++++-------
>> 3 files changed, 29 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c
>> index f99cfe2..9aecffef 100644
>> --- a/drivers/cpufreq/exynos-cpufreq.c
>> +++ b/drivers/cpufreq/exynos-cpufreq.c
>> @@ -17,6 +17,7 @@
>> #include<linux/regulator/consumer.h>
>> #include<linux/cpufreq.h>
>> #include<linux/platform_device.h>
>> +#include<linux/of.h>
>>
>> #include<plat/cpu.h>
>>
>> @@ -163,11 +164,24 @@ static int exynos_cpufreq_probe(struct platform_device *pdev)
>> if (!exynos_info)
>> return -ENOMEM;
>>
>> - if (soc_is_exynos4210())
>> + if (of_machine_is_compatible("samsung,exynos4210")) {
>> + exynos_info->type = EXYNOS_SOC_4210;
>> + } else if (of_machine_is_compatible("samsung,exynos4212")) {
>> + exynos_info->type = EXYNOS_SOC_4212;
>> + } else if (of_machine_is_compatible("samsung,exynos4412")) {
>> + exynos_info->type = EXYNOS_SOC_4212;
>
> 4412 ?
>
Yes, I will fix when I apply.
>> + } else if (of_machine_is_compatible("samsung,exynos5250")) {
>> + exynos_info->type = EXYNOS_SOC_5250;
>> + } else {
>> + pr_err("%s: Unknown SoC type\n", __func__);
>> + return -ENODEV;
>> + }
>> +
>> + if (exynos_info->type == EXYNOS_SOC_4210)
>> ret = exynos4210_cpufreq_init(exynos_info);
>> - else if (soc_is_exynos4212() || soc_is_exynos4412())
>> + else if (exynos_info->type == EXYNOS_SOC_4212 || exynos_info->type == EXYNOS_SOC_4412)
>> ret = exynos4x12_cpufreq_init(exynos_info);
>> - else if (soc_is_exynos5250())
>> + else if (exynos_info->type == EXYNOS_SOC_5250)
>> ret = exynos5250_cpufreq_init(exynos_info);
>> else
>> return 0;
>
> Do this in the first if/else only..
Probably, you mean following in above?
>> - if (soc_is_exynos4210())
I've applied this with fixing typo you mentioned just now, if any
concerns, please kindly let me know.
Thanks,
Kukjin
next prev parent reply other threads:[~2014-05-16 23:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 10:18 [PATCH v3] cpufreq: exynos: Fix the compile error Jonghwan Choi
2014-05-16 10:18 ` Jonghwan Choi
2014-05-16 10:54 ` Kukjin Kim
2014-05-16 10:54 ` Kukjin Kim
2014-05-16 23:04 ` Rafael J. Wysocki
2014-05-16 23:04 ` Rafael J. Wysocki
2014-05-16 23:24 ` Kukjin Kim
2014-05-16 23:24 ` Kukjin Kim
2014-05-16 23:28 ` Tomasz Figa
2014-05-16 23:28 ` Tomasz Figa
2014-05-19 23:33 ` Rafael J. Wysocki
2014-05-19 23:33 ` Rafael J. Wysocki
2014-05-20 0:29 ` Kukjin Kim
2014-05-20 0:29 ` Kukjin Kim
2014-05-16 11:07 ` Viresh Kumar
2014-05-16 11:07 ` Viresh Kumar
2014-05-16 23:26 ` Kukjin Kim [this message]
2014-05-16 23:26 ` Kukjin Kim
2014-05-16 23:37 ` Tomasz Figa
2014-05-16 23:37 ` Tomasz Figa
2014-05-16 23:44 ` Kukjin Kim
2014-05-16 23:44 ` Kukjin Kim
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=53769EBD.2000201@samsung.com \
--to=kgene.kim@samsung.com \
--cc=cpufreq@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jhbird.choi@gmail.com \
--cc=jhbird.choi@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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.