[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <53F5A587.9030200@collabora.com>
Date: Thu, 21 Aug 2014 09:53:43 +0200
From: Tomeu Vizoso <tomeu.vizoso@...labora.com>
To: Mike Turquette <mturquette@...aro.org>
CC: Stephen Warren <swarren@...dotorg.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Thierry Reding <thierry.reding@...il.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
Rabin Vincent <rabin@....in>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Tomasz Figa <t.figa@...sung.com>,
Peter De Schrijver <pdeschrijver@...dia.com>
Subject: Re: [PATCH v7 3/8] cpufreq: kirkwood: Remove use of the clk provider
API
On 08/21/2014 12:55 AM, Mike Turquette wrote:
> Quoting Tomeu Vizoso (2014-08-18 08:30:29)
>> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@...labora.com>
>> ---
>> drivers/cpufreq/kirkwood-cpufreq.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/cpufreq/kirkwood-cpufreq.c b/drivers/cpufreq/kirkwood-cpufreq.c
>> index 37a4806..f3d087f 100644
>> --- a/drivers/cpufreq/kirkwood-cpufreq.c
>> +++ b/drivers/cpufreq/kirkwood-cpufreq.c
>> @@ -12,7 +12,6 @@
>> #include <linux/kernel.h>
>> #include <linux/module.h>
>> #include <linux/clk.h>
>> -#include <linux/clk-provider.h>
>> #include <linux/cpufreq.h>
>> #include <linux/of_device.h>
>> #include <linux/platform_device.h>
>> @@ -50,7 +49,7 @@ static struct cpufreq_frequency_table kirkwood_freq_table[] = {
>>
>> static unsigned int kirkwood_cpufreq_get_cpu_frequency(unsigned int cpu)
>> {
>> - if (__clk_is_enabled(priv.powersave_clk))
>> + if (clk_is_enabled(priv.powersave_clk))
>> return kirkwood_freq_table[1].frequency;
>> return kirkwood_freq_table[0].frequency;
>> }
>> --
>> 1.9.3
>>
>
> Tomeu,
>
> After taking a second look at clk_is_enabled and the Kirkwood driver, I
> would prefer to not implement clk_is_enabled. The main reason is that it
> is racey, since the clock's status could of course change as soon as as
> that call completes. Furthermore I am worried that drivers might do
> something like:
>
> if (!clk_is_enabled(clk))
> clk_enable(clk);
>
> Which is crap and the driver should just call clk_enable any time it
> needs the clock. To that end I propose to drop "clk: provide public
> clk_is_enabled function" and replace your update to kirkwood-cpufreq.c
> with the following patch. Let me know what you think.
Yep, this looks much better to me. I will replace 2/8 and 3/8 with this
one for v8.
Reviewed-By: Tomeu Vizoso <tomeu.vizoso@...labora.com>
Thanks!
Tomeu
> Regards,
> Mike
>
>
>
> From 713b46fd66abd26a4e4d584a0b8a2a28c0459a60 Mon Sep 17 00:00:00 2001
> From: Mike Turquette <mturquette@...aro.org>
> Date: Mon, 18 Aug 2014 17:30:29 +0200
> Subject: [PATCH] cpufreq: kirkwood: Remove use of the clk provider API
>
> Instead of checking the clock framework to see if the clock is enabled,
> track the cpu frequency within the driver as the powersave_clk is
> enabled and disabled.
>
> Cc: Tomeu Vizoso <tomeu.vizoso@...labora.com>
> Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>
> Cc: Viresh Kumar <viresh.kumar@...aro.org>
> Signed-off-by: Mike Turquette <mturquette@...aro.org>
> ---
> drivers/cpufreq/kirkwood-cpufreq.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/cpufreq/kirkwood-cpufreq.c b/drivers/cpufreq/kirkwood-cpufreq.c
> index 37a4806..88f4641 100644
> --- a/drivers/cpufreq/kirkwood-cpufreq.c
> +++ b/drivers/cpufreq/kirkwood-cpufreq.c
> @@ -12,7 +12,6 @@
> #include <linux/kernel.h>
> #include <linux/module.h>
> #include <linux/clk.h>
> -#include <linux/clk-provider.h>
> #include <linux/cpufreq.h>
> #include <linux/of_device.h>
> #include <linux/platform_device.h>
> @@ -33,6 +32,8 @@ static struct priv
> #define STATE_CPU_FREQ 0x01
> #define STATE_DDR_FREQ 0x02
>
> +static unsigned long cpu_frequency = 0;
> +
> /*
> * Kirkwood can swap the clock to the CPU between two clocks:
> *
> @@ -50,9 +51,7 @@ static struct cpufreq_frequency_table kirkwood_freq_table[] = {
>
> static unsigned int kirkwood_cpufreq_get_cpu_frequency(unsigned int cpu)
> {
> - if (__clk_is_enabled(priv.powersave_clk))
> - return kirkwood_freq_table[1].frequency;
> - return kirkwood_freq_table[0].frequency;
> + return cpu_frequency;
> }
>
> static int kirkwood_cpufreq_target(struct cpufreq_policy *policy,
> @@ -71,9 +70,11 @@ static int kirkwood_cpufreq_target(struct cpufreq_policy *policy,
> switch (state) {
> case STATE_CPU_FREQ:
> clk_disable(priv.powersave_clk);
> + cpu_frequency = kirkwood_freq_table[0].frequency;
> break;
> case STATE_DDR_FREQ:
> clk_enable(priv.powersave_clk);
> + cpu_frequency = kirkwood_freq_table[1].frequency;
> break;
> }
>
> @@ -133,6 +134,7 @@ static int kirkwood_cpufreq_probe(struct platform_device *pdev)
>
> clk_prepare_enable(priv.cpu_clk);
> kirkwood_freq_table[0].frequency = clk_get_rate(priv.cpu_clk) / 1000;
> + cpu_frequency = kirkwood_freq_table[0].frequency;
>
> priv.ddr_clk = of_clk_get_by_name(np, "ddrclk");
> if (IS_ERR(priv.ddr_clk)) {
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists