summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorChristian Marangi <ansuelsmth@gmail.com>2023-02-08 18:39:12 +0300
committerViresh Kumar <viresh.kumar@linaro.org>2023-02-14 08:21:58 +0300
commit389de9c5a677c0d950528ee7d1871366ad2a6fd8 (patch)
treee26d4a33bb62da27d56c2a821a9957fd00478ffc /tools/perf/scripts/python/exported-sql-viewer.py
parent26e27f4e382f126d80e230df2a76d5f1c5a1ac42 (diff)
downloadlinux-389de9c5a677c0d950528ee7d1871366ad2a6fd8.tar.xz
dt-bindings: cpufreq: qcom-cpufreq-nvmem: make cpr bindings optional
The qcom-cpufreq-nvmem driver supports 2 kind of devices: - pre-cpr that doesn't have power-domains and base everything on nvmem cells and multiple named microvolt bindings. Doesn't need required-opp binding in the opp nodes as they are only used for genpd based devices. - cpr-based that require power-domain in the cpu nodes and use various source to decide the correct voltage and freq Require required-opp binding since they need to be linked to the related opp-level. When the schema was introduced, it was wrongly set to always require these binding but this is not the case for pre-cpr devices. Make the power-domain and the required-opp optional and set them required only for qcs404 based devices. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions