On 04/19/2013 08:59 PM, Arnd Bergmann wrote:
Maybe you just didn't have CPUFREQ enabled? I also didn't notice this bug at first because it is turned off in the defconfigs.
I certainly had it enabled. Since I remember I needed to turn it off temporarily after someone has introduced an incorrect change to the clock tree definition and cpufreq was unexpectedly switching parents of one of the root clocks at run time, which was causing malfunction of the camera image processing chain. Anyway this wasn't a clean mainline kernel, as there have been recently lot of stuff pending upstream needed to have complete system with dt support. I assume after 3.10 release the situation is going to be much better.
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. Thanks, Sylwester -- 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
