lkml.org 
[lkml]   [2018]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v4 13/14] dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu
    +Sricharan,

    On 30-03-18, 00:26, Ilia Lin wrote:
    > 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.
    > 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
    > to provide the OPP framework with required information.
    > 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.
    >
    > This change adds documentation.
    >
    > Change-Id: I1953f652a48249fb516d175f0e965a9510cd4209
    > Signed-off-by: Ilia Lin <ilialin@codeaurora.org>
    > ---
    > .../devicetree/bindings/cpufreq/kryo-cpufreq.txt | 693 +++++++++++++++++++++
    > 1 file changed, 693 insertions(+)
    > create mode 100644 Documentation/devicetree/bindings/cpufreq/kryo-cpufreq.txt
    >
    > diff --git a/Documentation/devicetree/bindings/cpufreq/kryo-cpufreq.txt b/Documentation/devicetree/bindings/cpufreq/kryo-cpufreq.txt

    This should really go in opp directory.

    > new file mode 100644
    > index 0000000..20cef9d
    > --- /dev/null
    > +++ b/Documentation/devicetree/bindings/cpufreq/kryo-cpufreq.txt
    > @@ -0,0 +1,693 @@
    > +Qualcomm Technologies, Inc. KRYO 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.
    > +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
    > +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.
    > +
    > +Required properties:
    > +--------------------
    > +In 'cpus' nodes:
    > +- operating-points-v2: Phandle to the operating-points-v2 table to use.
    > +
    > +In 'operating-points-v2' table:
    > +- compatible: Should be
    > + - 'operating-points-v2-kryo-cpu' for apq8096 and msm8996.
    > +- nvmem-cells: A phandle pointing to a nvmem-cells node representing the
    > + efuse registers that has information about the
    > + speedbin that is used to select the right frequency/voltage
    > + value pair.
    > + Please refer the for nvmem-cells
    > + bindings Documentation/devicetree/bindings/nvmem/nvmem.txt
    > + and also examples below.

    Sricharan is also working on adding these, just make sure you guys do the same
    thing..

    --
    viresh

    \
     
     \ /
      Last update: 2018-04-02 11:31    [W:5.686 / U:1.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site