[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5587958.90ud9NuKXm@wuerfel>
Date: Wed, 14 May 2014 15:04:51 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: Chander Kashyap <chander.kashyap@...aro.org>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org,
Chander Kashyap <k.chander@...sung.com>,
lorenzo.pieralisi@....com, daniel.lezcano@...aro.org,
rjw@...ysocki.net, kgene.kim@...sung.com
Subject: Re: [PATCH v5 4/6] driver: cpuidle: cpuidle-big-little: init driver for Exynos5420
On Wednesday 14 May 2014 13:33:55 Chander Kashyap wrote:
>
> diff --git a/drivers/cpuidle/cpuidle-big_little.c b/drivers/cpuidle/cpuidle-big_little.c
> index 4cd02bd..344d79fa 100644
> --- a/drivers/cpuidle/cpuidle-big_little.c
> +++ b/drivers/cpuidle/cpuidle-big_little.c
> @@ -165,6 +165,7 @@ static int __init bl_idle_driver_init(struct cpuidle_driver *drv, int cpu_id)
>
> static const struct of_device_id compatible_machine_match[] = {
> { .compatible = "arm,vexpress,v2p-ca15_a7" },
> + { .compatible = "samsung,exynos5420" },
> {},
> };
Does the cpuidle-big_little driver actually care about the platform?
If not, it would be good to add a generic string here as well, for
future platforms to match.
It still makes sense to list both the generic string and the platform
specific one though, in case we have to work around subtle differences.
Arnd
--
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