cpufreq: qcom: Re-organise kryo cpufreq to use it for other nvmem based qcom socs
authorSricharan R <sricharan@codeaurora.org>
Thu, 25 Jul 2019 10:41:31 +0000 (12:41 +0200)
committerViresh Kumar <viresh.kumar@linaro.org>
Tue, 3 Sep 2019 02:25:00 +0000 (07:55 +0530)
commit7d12709544b8b3fb9727a34a664b8380e1e3493a
tree49958927ca1f9f7502d0166fffb8265bbe78697b
parent475a21e0eade5227488d97aebeaa882b16f38ca1
cpufreq: qcom: Re-organise kryo cpufreq to use it for other nvmem based qcom socs

The kryo cpufreq driver reads the nvmem cell and uses that data to
populate the opps. There are other qcom cpufreq socs like krait which
does similar thing. Except for the interpretation of the read data,
rest of the driver is same for both the cases. So pull the common things
out for reuse.

Signed-off-by: Sricharan R <sricharan@codeaurora.org>
[niklas.cassel@linaro.org: split dt-binding into a separate patch and
do not rename the compatible string. Update MAINTAINERS file.]
Signed-off-by: Niklas Cassel <niklas.cassel@linaro.org>
Reviewed-by: Ilia Lin <ilia.lin@kernel.org>
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
MAINTAINERS
drivers/cpufreq/Kconfig.arm
drivers/cpufreq/Makefile
drivers/cpufreq/qcom-cpufreq-kryo.c [deleted file]
drivers/cpufreq/qcom-cpufreq-nvmem.c [new file with mode: 0644]