[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4abf0d97-d2b8-46ab-3c05-4a11510ac3fe@linaro.org>
Date: Mon, 16 Apr 2018 11:45:37 +0200
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Sudeep Holla <sudeep.holla@....com>, edubezval@...il.com,
kevin.wangtao@...aro.org, leo.yan@...aro.org,
vincent.guittot@...aro.org, linux-kernel@...r.kernel.org,
javi.merino@...nel.org, rui.zhang@...el.com,
daniel.thompson@...aro.org, linux-pm@...r.kernel.org,
Amit Daniel Kachhap <amit.kachhap@...il.com>
Subject: Re: [PATCH v3 6/7] thermal/drivers/cpu_cooling: Introduce the cpu
idle cooling driver
On 16/04/2018 11:37, Viresh Kumar wrote:
> On 16-04-18, 09:44, Daniel Lezcano wrote:
>> Because we rely on the number to identify the cluster and flag it
>> 'processed'. The number itself is not important.
>
> It is, because you are creating multiple groups (like cpufreq
> policies) right now based on cluster id. Which will be zero for all
> the CPUs. So in a big little system we will have two cpufreq cooling
> devices and one cpuidle cooling device.
Can you elaborate a bit ? I'm not sure to get the point.
BTW, Am I asked to change my code to stick to something which is not
merged ?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
Powered by blists - more mailing lists