[v2,02/14] dt-bindings: cpufreq: Re-organise kryo cpufreq to use it for other nvmem based qcom socs

Message ID 20190725104144.22924-3-niklas.cassel@linaro.org
State New
Headers show
Series
  • Untitled series #22167
Related show

Commit Message

Niklas Cassel July 25, 2019, 10:41 a.m.
From: Sricharan R <sricharan@codeaurora.org>


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>

---
Changes since V1:
-Picked up tags.

 .../opp/{kryo-cpufreq.txt => qcom-nvmem-cpufreq.txt}   | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
 rename Documentation/devicetree/bindings/opp/{kryo-cpufreq.txt => qcom-nvmem-cpufreq.txt} (98%)

-- 
2.21.0

Comments

Viresh Kumar July 26, 2019, 8:04 a.m. | #1
$subject of this and few more binding patches updated to:

"dt-bindings: opp: XXX"

On 25-07-19, 12:41, Niklas Cassel wrote:
> From: Sricharan R <sricharan@codeaurora.org>

> 

> 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>

> ---

> Changes since V1:

> -Picked up tags.


-- 
viresh

Patch

diff --git a/Documentation/devicetree/bindings/opp/kryo-cpufreq.txt b/Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt
similarity index 98%
rename from Documentation/devicetree/bindings/opp/kryo-cpufreq.txt
rename to Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt
index c2127b96805a..198441e80ba8 100644
--- a/Documentation/devicetree/bindings/opp/kryo-cpufreq.txt
+++ b/Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt
@@ -1,13 +1,13 @@ 
-Qualcomm Technologies, Inc. KRYO CPUFreq and OPP bindings
+Qualcomm Technologies, Inc. NVMEM CPUFreq and OPP bindings
 ===================================
 
-In Certain Qualcomm Technologies, Inc. SoCs like apq8096 and msm8996
-that have KRYO processors, the CPU ferequencies subset and voltage value
-of each OPP varies based on the silicon variant in use.
+In Certain Qualcomm Technologies, Inc. SoCs like apq8096 and msm8996,
+the CPU frequencies subset and voltage value of each OPP varies based on
+the silicon variant in use.
 Qualcomm Technologies, Inc. Process Voltage Scaling Tables
 defines the voltage and frequency value based on the msm-id in SMEM
 and speedbin blown in the efuse combination.
-The qcom-cpufreq-kryo driver reads the msm-id and efuse value from the SoC
+The qcom-cpufreq-nvmem driver reads the msm-id and efuse value from the SoC
 to provide the OPP framework with required information (existing HW bitmap).
 This is used to determine the voltage and frequency value for each OPP of
 operating-points-v2 table when it is parsed by the OPP framework.