From: Viresh Kumar <viresh.kumar@linaro.org> To: Krzysztof Kozlowski <k.kozlowski@samsung.com> Cc: Rafael Wysocki <rjw@rjwysocki.net>, arnd.bergmann@linaro.org, Kukjin Kim <kgene@kernel.org>, linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, kgene.kim@samsung.com, xf@rock-chips.com, heiko@sntech.de, mmcclint@codeaurora.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/3] cpufreq: exynos: Use generic platdev driver Date: Tue, 29 Mar 2016 09:49:23 +0530 [thread overview] Message-ID: <20160329041923.GB25424@vireshk-i7> (raw) In-Reply-To: <20160329041827.GA25424@vireshk-i7> On 29-03-16, 09:48, Viresh Kumar wrote: > On 29-03-16, 13:10, Krzysztof Kozlowski wrote: > > On 24.03.2016 15:40, Viresh Kumar wrote: > > > The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform > > > device now, reuse that and remove similar code from platform code. > > > > > > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> > > > --- > > > arch/arm/mach-exynos/exynos.c | 25 ------------------------- > > > drivers/cpufreq/cpufreq-dt-platdev.c | 5 +++++ > > > 2 files changed, 5 insertions(+), 25 deletions(-) > > > > Looks fine to me... except that it is a little bit outdated. Please > > rebase on v4.6-rc1 because Bartlomiej added support for cpufreq @Exynos542x. > > Yeah, I know. I already have the updated version. Here it is: From: Viresh Kumar <viresh.kumar@linaro.org> Date: Thu, 24 Mar 2016 12:04:10 +0530 Subject: [PATCH] cpufreq: exynos: Use generic platdev driver The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> --- arch/arm/mach-exynos/exynos.c | 29 ----------------------------- drivers/cpufreq/cpufreq-dt-platdev.c | 9 +++++++++ 2 files changed, 9 insertions(+), 29 deletions(-) diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c index bbf51a46f772..4d3b056fd786 100644 --- a/arch/arm/mach-exynos/exynos.c +++ b/arch/arm/mach-exynos/exynos.c @@ -213,33 +213,6 @@ static void __init exynos_init_irq(void) exynos_map_pmu(); } -static const struct of_device_id exynos_cpufreq_matches[] = { - { .compatible = "samsung,exynos3250", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos4210", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos4212", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos4412", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos5250", .data = "cpufreq-dt" }, -#ifndef CONFIG_BL_SWITCHER - { .compatible = "samsung,exynos5420", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos5800", .data = "cpufreq-dt" }, -#endif - { /* sentinel */ } -}; - -static void __init exynos_cpufreq_init(void) -{ - struct device_node *root = of_find_node_by_path("/"); - const struct of_device_id *match; - - match = of_match_node(exynos_cpufreq_matches, root); - if (!match) { - platform_device_register_simple("exynos-cpufreq", -1, NULL, 0); - return; - } - - platform_device_register_simple(match->data, -1, NULL, 0); -} - static void __init exynos_dt_machine_init(void) { /* @@ -262,8 +235,6 @@ static void __init exynos_dt_machine_init(void) of_machine_is_compatible("samsung,exynos5250")) platform_device_register(&exynos_cpuidle); - exynos_cpufreq_init(); - of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL); } diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c index 18b81724ca0b..f85d1ab5d621 100644 --- a/drivers/cpufreq/cpufreq-dt-platdev.c +++ b/drivers/cpufreq/cpufreq-dt-platdev.c @@ -20,6 +20,15 @@ struct cpufreq_dt_compat { }; static struct cpufreq_dt_compat compat[] = { + { "samsung,exynos3250", NULL, 0 }, + { "samsung,exynos4210", NULL, 0 }, + { "samsung,exynos4212", NULL, 0 }, + { "samsung,exynos4412", NULL, 0 }, + { "samsung,exynos5250", NULL, 0 }, +#ifndef CONFIG_BL_SWITCHER + { "samsung,exynos5420", NULL, 0 }, + { "samsung,exynos5800", NULL, 0 }, +#endif }; static int __init cpufreq_dt_platdev_init(void) -- viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 3/3] cpufreq: exynos: Use generic platdev driver Date: Tue, 29 Mar 2016 09:49:23 +0530 [thread overview] Message-ID: <20160329041923.GB25424@vireshk-i7> (raw) In-Reply-To: <20160329041827.GA25424@vireshk-i7> On 29-03-16, 09:48, Viresh Kumar wrote: > On 29-03-16, 13:10, Krzysztof Kozlowski wrote: > > On 24.03.2016 15:40, Viresh Kumar wrote: > > > The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform > > > device now, reuse that and remove similar code from platform code. > > > > > > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> > > > --- > > > arch/arm/mach-exynos/exynos.c | 25 ------------------------- > > > drivers/cpufreq/cpufreq-dt-platdev.c | 5 +++++ > > > 2 files changed, 5 insertions(+), 25 deletions(-) > > > > Looks fine to me... except that it is a little bit outdated. Please > > rebase on v4.6-rc1 because Bartlomiej added support for cpufreq @Exynos542x. > > Yeah, I know. I already have the updated version. Here it is: From: Viresh Kumar <viresh.kumar@linaro.org> Date: Thu, 24 Mar 2016 12:04:10 +0530 Subject: [PATCH] cpufreq: exynos: Use generic platdev driver The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform device now, reuse that and remove similar code from platform code. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> --- arch/arm/mach-exynos/exynos.c | 29 ----------------------------- drivers/cpufreq/cpufreq-dt-platdev.c | 9 +++++++++ 2 files changed, 9 insertions(+), 29 deletions(-) diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c index bbf51a46f772..4d3b056fd786 100644 --- a/arch/arm/mach-exynos/exynos.c +++ b/arch/arm/mach-exynos/exynos.c @@ -213,33 +213,6 @@ static void __init exynos_init_irq(void) exynos_map_pmu(); } -static const struct of_device_id exynos_cpufreq_matches[] = { - { .compatible = "samsung,exynos3250", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos4210", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos4212", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos4412", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos5250", .data = "cpufreq-dt" }, -#ifndef CONFIG_BL_SWITCHER - { .compatible = "samsung,exynos5420", .data = "cpufreq-dt" }, - { .compatible = "samsung,exynos5800", .data = "cpufreq-dt" }, -#endif - { /* sentinel */ } -}; - -static void __init exynos_cpufreq_init(void) -{ - struct device_node *root = of_find_node_by_path("/"); - const struct of_device_id *match; - - match = of_match_node(exynos_cpufreq_matches, root); - if (!match) { - platform_device_register_simple("exynos-cpufreq", -1, NULL, 0); - return; - } - - platform_device_register_simple(match->data, -1, NULL, 0); -} - static void __init exynos_dt_machine_init(void) { /* @@ -262,8 +235,6 @@ static void __init exynos_dt_machine_init(void) of_machine_is_compatible("samsung,exynos5250")) platform_device_register(&exynos_cpuidle); - exynos_cpufreq_init(); - of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL); } diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c index 18b81724ca0b..f85d1ab5d621 100644 --- a/drivers/cpufreq/cpufreq-dt-platdev.c +++ b/drivers/cpufreq/cpufreq-dt-platdev.c @@ -20,6 +20,15 @@ struct cpufreq_dt_compat { }; static struct cpufreq_dt_compat compat[] = { + { "samsung,exynos3250", NULL, 0 }, + { "samsung,exynos4210", NULL, 0 }, + { "samsung,exynos4212", NULL, 0 }, + { "samsung,exynos4412", NULL, 0 }, + { "samsung,exynos5250", NULL, 0 }, +#ifndef CONFIG_BL_SWITCHER + { "samsung,exynos5420", NULL, 0 }, + { "samsung,exynos5800", NULL, 0 }, +#endif }; static int __init cpufreq_dt_platdev_init(void) -- viresh
next prev parent reply other threads:[~2016-03-29 4:19 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-03-24 6:40 [PATCH 0/3] cpufreq: dt: Create platform device from generic code Viresh Kumar 2016-03-24 6:40 ` [PATCH 1/3] cpufreq: dt: Include types.h from cpufreq-dt.h Viresh Kumar 2016-03-24 6:40 ` [PATCH 2/3] cpufreq: dt: Add generic platform-device creation support Viresh Kumar 2016-03-29 4:03 ` Krzysztof Kozlowski 2016-03-24 6:40 ` [PATCH 3/3] cpufreq: exynos: Use generic platdev driver Viresh Kumar 2016-03-24 6:40 ` Viresh Kumar 2016-03-29 2:35 ` Krzysztof Kozlowski 2016-03-29 2:35 ` Krzysztof Kozlowski 2016-03-29 2:38 ` Viresh Kumar 2016-03-29 2:38 ` Viresh Kumar 2016-03-29 4:10 ` Krzysztof Kozlowski 2016-03-29 4:10 ` Krzysztof Kozlowski 2016-03-29 4:18 ` Viresh Kumar 2016-03-29 4:18 ` Viresh Kumar 2016-03-29 4:19 ` Viresh Kumar [this message] 2016-03-29 4:19 ` Viresh Kumar 2016-03-29 4:39 ` Krzysztof Kozlowski 2016-03-29 4:39 ` Krzysztof Kozlowski 2016-03-24 13:36 ` [PATCH 0/3] cpufreq: dt: Create platform device from generic code Arnd Bergmann 2016-03-24 14:06 ` Viresh Kumar 2016-03-24 14:16 ` Arnd Bergmann 2016-03-25 4:41 ` Viresh Kumar 2016-03-28 15:05 ` Viresh Kumar 2016-03-29 13:22 ` Arnd Bergmann 2016-03-29 14:02 ` 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=20160329041923.GB25424@vireshk-i7 \ --to=viresh.kumar@linaro.org \ --cc=arnd.bergmann@linaro.org \ --cc=heiko@sntech.de \ --cc=k.kozlowski@samsung.com \ --cc=kgene.kim@samsung.com \ --cc=kgene@kernel.org \ --cc=linaro-kernel@lists.linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=mmcclint@codeaurora.org \ --cc=rjw@rjwysocki.net \ --cc=xf@rock-chips.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: linkBe 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.