On Friday 19 April 2013, Sylwester Nawrocki wrote: > > It could also be working by chance on EXYNOS4, since the register > > definitions were not actually removed from the regs-clk.h header > > for those. > > That's most likely what happened. Ok. I think I see the bigger picture now. The EXYNOS5 cpufreq driver was actually just merged now, so I assume that by the time Thomas did the clock changes, the register definitions for EXYNOS5 were actually unused and he subsequently removed them from the kernel. Since the driver now depends on them, I think the only way forward for 3.10 is to revert the change that removed the definitions and put them back in place. We really should use the clock API from all the exynos cpufreq drivers, but it's too late for that change now in 3.10 and we will have to do it for 3.11 then. This are not looking so good for exynos multiplatform support in 3.10 now, but if we get it in, that will mean we have to disable cpufreq when building multiplatform, but it can remain for the classic single-platform configurations. Arnd -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
