[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANuQgHHMQ_SpO7jvbL7KDP0frK2_QFo8wvPwLrpsUFwPUQMt_g@mail.gmail.com>
Date: Thu, 24 Apr 2014 13:17:07 +0530
From: Chander Kashyap <chander.kashyap@...aro.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Cc: "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-samsung-soc@...r.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"kgene.kim@...sung.com" <kgene.kim@...sung.com>,
Chander Kashyap <k.chander@...sung.com>
Subject: Re: [Patch v2 2/4] driver: cpuidle: cpuidle-big-little: init driver
for Exynos5420
On 23 April 2014 22:02, Lorenzo Pieralisi <lorenzo.pieralisi@....com> wrote:
> On Wed, Apr 23, 2014 at 10:25:52AM +0100, Chander Kashyap wrote:
>> Add "samsung,exynos5420" compatible string to initialize generic
>> big-little cpuidle driver for Exynos5420.
>>
>> Signed-off-by: Chander Kashyap <chander.kashyap@...aro.org>
>> Signed-off-by: Chander Kashyap <k.chander@...sung.com>
>> Acked-by: Daniel Lezcano <daniel.lezcano@...aro.org>
>> ---
>> drivers/cpuidle/cpuidle-big_little.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/cpuidle/cpuidle-big_little.c b/drivers/cpuidle/cpuidle-big_little.c
>> index b45fc62..d0fac53 100644
>> --- a/drivers/cpuidle/cpuidle-big_little.c
>> +++ b/drivers/cpuidle/cpuidle-big_little.c
>> @@ -170,7 +170,8 @@ static int __init bl_idle_init(void)
>> /*
>> * Initialize the driver just for a compliant set of machines
>> */
>> - if (!of_machine_is_compatible("arm,vexpress,v2p-ca15_a7"))
>> + if (!of_machine_is_compatible("arm,vexpress,v2p-ca15_a7") &&
>> + (!of_machine_is_compatible("samsung,exynos5420")))
>> return -ENODEV;
>
> We should handle the string matching differently, we can't keep adding
> comparisons.
yes, that's true.
>
> Daniel raised the point already: what about the idle tables (data and
> number of states ?). TC2 has just a cluster state, and specific
> latencies, which are highly unlikely to be correct for this platform.
>
As of now only support for one state i.e. core power down.
As latencies are concerned, need to fine tune.
Thanks again for the review.
> Lorenzo
>
--
with warm regards,
Chander Kashyap
--
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