This is second attempt to initialize CPU's OPPs from CPU core code. First one was here: https://lkml.org/lkml/2014/5/19/57
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. This patchset is all about that. The idea was initially discussed here: https://lkml.org/lkml/2014/5/17/123 V1->V2: - Addition of two new patches: 1/2 & 2/2 - Created separate routine of_init_cpu_opp_table() which wouldn't add any overhead for the platforms which don't have OPP or OF enabled. - Added a print for success case as well - Added Acks from Shawn - Got rid of extra indentation level by returning early from register_cpu(). Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org> Cc: Amit Daniel Kachhap <amit.dan...@samsung.com> Cc: Kukjin Kim <kgene....@samsung.com> Cc: Shawn Guo <shawn....@linaro.org> Viresh Kumar (7): opp: remove -ENOSYS from dummy implementation of of_init_opp_table() opp: handle of_node_{get|put}() inside of_init_opp_table() 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 | 30 ++++++++++++++++++++++++++---- drivers/base/power/opp.c | 4 ++++ 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 +------------------- include/linux/pm_opp.h | 2 +- 9 files changed, 47 insertions(+), 87 deletions(-) -- 2.0.0.rc2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
