On Mon, May 5, 2014 at 7:03 PM, Nishanth Menon <nm@xxxxxx> wrote: > CPUFreq usage of OPP should be independent of the ordering of type of > data storage inside OPP layer. The current operations can equally be > performed by generic operations. > > [RFC]: https://patchwork.kernel.org/patch/4100811/ > > Series based on: v3.15-rc1 > > Nishanth Menon (2): > PM / OPP: Remove cpufreq wrapper dependency on internal data > organization > PM / OPP: Move cpufreq specific OPP functions out of generic OPP > library > > Documentation/cpu-freq/core.txt | 29 +++++++++++ > Documentation/power/opp.txt | 40 ++------------ > drivers/base/power/opp.c | 91 -------------------------------- > drivers/cpufreq/Makefile | 2 + > drivers/cpufreq/cpufreq_opp.c | 110 +++++++++++++++++++++++++++++++++++++++ > include/linux/cpufreq.h | 21 ++++++++ > include/linux/pm_opp.h | 20 ------- > 7 files changed, 167 insertions(+), 146 deletions(-) > create mode 100644 drivers/cpufreq/cpufreq_opp.c Works fine on Exynos. Tested-by: Thomas Abraham <thomas.ab@xxxxxxxxxxx> > > -- > 1.7.9.5 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-pm" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- 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
