]> asedeno.scripts.mit.edu Git - linux.git/commit
dt-bindings: opp: Re-organise kryo cpufreq to use it for other nvmem based qcom socs
authorSricharan R <sricharan@codeaurora.org>
Thu, 25 Jul 2019 10:41:30 +0000 (12:41 +0200)
committerViresh Kumar <viresh.kumar@linaro.org>
Fri, 26 Jul 2019 07:58:24 +0000 (13:28 +0530)
commit8cfda0df3a3020454848f55ed23a781169770c99
tree00a6d73a888940c87e219e6b5d266834f24b772d
parent71419d84c216cee8da3b19fb843b4242f112cde4
dt-bindings: opp: 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.]
Signed-off-by: Niklas Cassel <niklas.cassel@linaro.org>
Reviewed-by: Ilia Lin <ilia.lin@kernel.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt [moved from Documentation/devicetree/bindings/opp/kryo-cpufreq.txt with 98% similarity]