[PATCH v2 1/4] cpufreq: pxa: use generic platdev driver for device-tree
From: viresh.kumar@linaro.org (Viresh Kumar)
Date: 2016-10-18 11:38:58
Also in:
linux-devicetree, linux-pm, lkml
On 15-10-16, 21:57, Robert Jarzmik wrote:
quoted hunk ↗ jump to hunk
For device-tree based pxa25x and pxa27x platforms, cpufreq-dt driver is doing the job as well as pxa2xx-cpufreq, so add these platforms to the compatibility list. This won't work for legacy non device-tree platforms where pxa2xx-cpufreq is still required. Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr> --- drivers/cpufreq/cpufreq-dt-platdev.c | 2 ++ 1 file changed, 2 insertions(+)diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c index 0bb44d5b5df4..356825b5c9b8 100644 --- a/drivers/cpufreq/cpufreq-dt-platdev.c +++ b/drivers/cpufreq/cpufreq-dt-platdev.c@@ -32,6 +32,8 @@ static const struct of_device_id machines[] __initconst = { { .compatible = "fsl,imx7d", }, { .compatible = "marvell,berlin", }, + { .compatible = "marvell,pxa250", }, + { .compatible = "marvell,pxa270", }, { .compatible = "samsung,exynos3250", }, { .compatible = "samsung,exynos4210", },
Isn't there a race between cpufreq-dt and the platform driver to register first ? Also, it seems that atleast the next two patches are required before applying this? You need to fix the order if that is the case. -- viresh