All drivers expecting CPU's OPPs from device tree initialize OPP table using of_init_opp_table() and there is nothing driver specific in that. They all do it in the same way adding to code redundancy.
It would be better if we can get rid of code redundancy by initializing CPU OPPs from core code for all CPUs that have a "operating-points" property defined in their node. First patch initializes OPPs as soon as CPU device is registered in register_cpu(). Following patches get rid of these calls from individual drivers which are currently initializing OPPs. The idea was initially discussed here: https://lkml.org/lkml/2014/5/17/123 Cc: Greg Kroah-Hartman <[email protected]> Cc: Amit Daniel Kachhap <[email protected]> Cc: Kukjin Kim <[email protected]> Cc: Shawn Guo <[email protected]> Cc: Sudeep Holla <[email protected]> Viresh Kumar (5): driver/core: cpu: initialize opp table cpufreq: arm_big_little: don't initialize opp table cpufreq: imx6q: don't initialize opp table cpufreq: cpufreq-cpu0: don't initialize opp table cpufreq: exynos5440: don't initialize opp table arch/arm/mach-imx/mach-imx6q.c | 36 ++++++++---------------------------- drivers/base/cpu.c | 14 ++++++++++++-- drivers/cpufreq/arm_big_little.c | 12 +++++++----- drivers/cpufreq/arm_big_little_dt.c | 18 ------------------ drivers/cpufreq/cpufreq-cpu0.c | 6 ------ drivers/cpufreq/exynos5440-cpufreq.c | 6 ------ drivers/cpufreq/imx6q-cpufreq.c | 20 +------------------- 7 files changed, 28 insertions(+), 84 deletions(-) -- 2.0.0.rc2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
