[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKohpomv8fXqVEBWkmJTHKrkdVUbZCodV_D_pu3hjRqH0wUEeg@mail.gmail.com>
Date: Wed, 3 Dec 2014 12:00:58 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Eduardo Valentin <edubezval@...il.com>
Cc: Linux PM <linux-pm@...r.kernel.org>,
Lukasz Majewski <l.majewski@...sung.com>,
LKML <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Grant Likely <grant.likely@...aro.org>,
Kukjin Kim <kgene.kim@...sung.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
Naveen Krishna Chatradhi <ch.naveen@...sung.com>,
Rob Herring <robh+dt@...nel.org>,
Zhang Rui <rui.zhang@...el.com>
Subject: Re: [PATCHv3 1/1] thermal: cpu_cooling: check for the readiness of
cpufreq layer
On 28 November 2014 at 20:23, Eduardo Valentin <edubezval@...il.com> wrote:
> diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c
> index 1ab0018..88d2775 100644
> --- a/drivers/thermal/cpu_cooling.c
> +++ b/drivers/thermal/cpu_cooling.c
> @@ -440,6 +440,9 @@ __cpufreq_cooling_register(struct device_node *np,
> int ret = 0, i;
> struct cpufreq_policy policy;
>
> + if (!cpufreq_frequency_get_table(0))
Please add a pr_debug() here, that will be quite useful while debugging.
Also, you can't simply pass 0 to get_table() above. We might be
registering the cooling device for some other cluster as well..
This is what I have done in my patch earlier.
cpufreq_frequency_get_table(cpumask_first(clip_cpus));
And this will work for all cases.
--
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