linux.git/Documentation/devicetree/bindings/opp, branch v5.9

dt-bindings: opp: Introduce opp-peak-kBps and opp-avg-kBps bindings

2020-05-13T06:16:11+00:00

Interconnects often quantify their performance points in terms of
bandwidth. So, add opp-peak-kBps (required) and opp-avg-kBps (optional) to
allow specifying Bandwidth OPP tables in DT.

opp-peak-kBps is a required property that replaces opp-hz for Bandwidth OPP
tables.

opp-avg-kBps is an optional property that can be used in Bandwidth OPP
tables.

Signed-off-by: Saravana Kannan 
Signed-off-by: Georgi Djakov 
Reviewed-by: Sibi Sankar 
Reviewed-by: Rob Herring 
Signed-off-by: Viresh Kumar

cpufreq: qcom: Add support for krait based socs

2020-03-20T04:29:57+00:00

In Certain QCOM SoCs like ipq8064, apq8064, msm8960, msm8974
that has KRAIT processors the voltage/current value of each OPP
varies based on the silicon variant in use.

The required OPP related data is determined based on
the efuse value. This is similar to the existing code for
kryo cores. So adding support for krait cores here.

Signed-off-by: Sricharan R 
Signed-off-by: Ansuel Smith 
Signed-off-by: Viresh Kumar

dt-bindings: opp: Convert Allwinner H6 OPP to a schema

2019-12-24T21:17:52+00:00

The Allwinner H6 SoCs use binning in order to provide binning to
cpufreq which is supported in Linux, with a matching Device Tree binding.

Now that we have the DT validation in place, let's convert the device tree
bindings for that controller over to a YAML schemas.

Signed-off-by: Maxime Ripard 
Signed-off-by: Rob Herring

Merge branches 'pm-opp', 'pm-qos', 'acpi-pm', 'pm-domains' and 'pm-tools'

2019-09-17T07:49:19+00:00

* pm-opp:
  PM / OPP: Correct Documentation about library location
  opp: of: Support multiple suspend OPPs defined in DT
  dt-bindings: opp: Support multiple opp-suspend properties
  opp: core: add regulators enable and disable
  opp: Don't decrement uninitialized list_kref

* pm-qos:
  PM: QoS: Get rid of unused flags

* acpi-pm:
  ACPI: PM: Print debug messages on device power state changes

* pm-domains:
  PM / Domains: Verify PM domain type in dev_pm_genpd_set_performance_state()
  PM / Domains: Simplify genpd_lookup_dev()
  PM / Domains: Align in-parameter names for some genpd functions

* pm-tools:
  pm-graph: make setVal unbuffered again for python2 and python3
  cpupower: update German translation
  tools/power/cpupower: fix 64bit detection when cross-compiling
  cpupower: Add missing newline at end of file
  pm-graph v5.5

Merge branch 'cpufreq/qcom-updates' into cpufreq/arm/linux-next

2019-09-03T02:25:22+00:00

Merge branch 'opp/qcom-updates' into opp/linux-next

2019-09-03T02:24:17+00:00

dt-bindings: opp: Add qcom-opp bindings with properties needed for CPR

2019-09-03T02:23:51+00:00

Add qcom-opp bindings with properties needed for Core Power Reduction
(CPR).

CPR is included in a great variety of Qualcomm SoCs, e.g. msm8916 and
msm8996. CPR was first introduced in msm8974.

Co-developed-by: Jorge Ramirez-Ortiz 
Signed-off-by: Jorge Ramirez-Ortiz 
Signed-off-by: Niklas Cassel 
Reviewed-by: Stephen Boyd 
Reviewed-by: Rob Herring 
Signed-off-by: Viresh Kumar

dt-bindings: opp: qcom-nvmem: Support pstates provided by a power domain

2019-09-03T02:23:19+00:00

Some Qualcomm SoCs have support for Core Power Reduction (CPR).
On these platforms, we need to attach to the power domain provider
providing the performance states, so that the leaky device (the CPU)
can configure the performance states (which represent different
CPU clock frequencies).

Signed-off-by: Niklas Cassel 
Reviewed-by: Rob Herring 
Signed-off-by: Viresh Kumar

dt-bindings: opp: qcom-nvmem: Make speedbin related properties optional

2019-07-26T07:58:59+00:00

Not all Qualcomm platforms need to care about the speedbin efuse,
nor the value blown into the speedbin efuse.
Therefore, make the nvmem-cells and opp-supported-hw properties
optional.

Signed-off-by: Niklas Cassel 
Reviewed-by: Ilia Lin 
Reviewed-by: Rob Herring 
Signed-off-by: Viresh Kumar

dt-bindings: opp: Re-organise kryo cpufreq to use it for other nvmem based qcom socs

2019-07-26T07:58:24+00:00

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 
[niklas.cassel@linaro.org: split dt-binding into a separate patch and
do not rename the compatible string.]
Signed-off-by: Niklas Cassel 
Reviewed-by: Ilia Lin 
Reviewed-by: Rob Herring 
Signed-off-by: Viresh Kumar