linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yassine Oudjana <y.oudjana@protonmail.com>
To: Rob Herring <robh+dt@kernel.org>, Ilia Lin <ilia.lin@kernel.org>,
	Niklas Cassel <nks@flawful.org>, Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-pm@vger.kernel.org
Cc: Yassine Oudjana <y.oudjana@protonmail.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] dt-bindings: Convert multiple Qualcomm OPP and CPUFreq bindings to DT schema
Date: Tue, 04 Jan 2022 13:27:36 +0000	[thread overview]
Message-ID: <20220104132618.391799-1-y.oudjana@protonmail.com> (raw)

This series is a compilation of DT schema conversions of multiple Qualcomm
OPP and CPUFreq bindings:
- qcom-cpufreq-nvmem (operating-points-v2-kryo-cpu)
- qcom-opp (operating-points-v2-qcom-level)
- qcom,cpr

Converting each one to DT schema introduces new dt_binding_check and
dtbs_check errors to the others, so it was better to combine them into
a series. Some errors were also caused by a couple of device trees having
OPP tables with names that do not follow opp-v2-base, so these got fixed
in this series as well. Finally, the lack of MSM8996 compatibles in
arm/qcom.yaml caused an error in the opp-v2-kryo-cpu example, so they were
added to the schema as well as to the msm8996-mtp device tree, which only
had qcom,msm8996-mtp as its compatible.

PATCH 4/7 is a new version of a patch[1] that was sent as part of
a different series before, and PATCH 7/7 is a new version of a patch[2]
that was first sent alone.

Changes since v1 (PATCH v2 4/7):
 - Split the schema into an OPP schema and a CPUFreq schema. 

Changes since v1 (PATCH v2 7/7):
 - Remove allOf from compatible.

Yassine Oudjana (7):
  dt-bindings: arm: qcom: Add msm8996 and apq8096 compatibles
  arm64: dts: qcom: msm8996-mtp: Add msm8996 compatible
  dt-bindings: opp: qcom-opp: Convert to DT schema
  dt-bindings: opp: Convert qcom-nvmem-cpufreq to DT schema
  arm64: dts: qcom: msm8996: Rename cluster OPP tables
  arm64: dts: qcom: qcs404: Rename CPU and CPR OPP tables
  dt-bindings: power: avs: qcom,cpr: Convert to DT schema

 .../devicetree/bindings/arm/qcom.yaml         |  16 +-
 .../bindings/cpufreq/qcom-cpufreq-nvmem.yaml  | 166 ++++
 .../bindings/opp/opp-v2-kryo-cpu.yaml         | 257 ++++++
 .../bindings/opp/opp-v2-qcom-level.yaml       |  60 ++
 .../bindings/opp/qcom-nvmem-cpufreq.txt       | 796 ------------------
 .../devicetree/bindings/opp/qcom-opp.txt      |  19 -
 .../bindings/power/avs/qcom,cpr.txt           | 130 ---
 .../bindings/power/avs/qcom,cpr.yaml          | 160 ++++
 MAINTAINERS                                   |   5 +-
 arch/arm64/boot/dts/qcom/msm8996-mtp.dts      |   2 +-
 arch/arm64/boot/dts/qcom/msm8996.dtsi         |   4 +-
 arch/arm64/boot/dts/qcom/qcs404.dtsi          |   4 +-
 12 files changed, 666 insertions(+), 953 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/cpufreq/qcom-cpufreq-nvmem.yaml
 create mode 100644 Documentation/devicetree/bindings/opp/opp-v2-kryo-cpu.yaml
 create mode 100644 Documentation/devicetree/bindings/opp/opp-v2-qcom-level.yaml
 delete mode 100644 Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt
 delete mode 100644 Documentation/devicetree/bindings/opp/qcom-opp.txt
 delete mode 100644 Documentation/devicetree/bindings/power/avs/qcom,cpr.txt
 create mode 100644 Documentation/devicetree/bindings/power/avs/qcom,cpr.yaml

[1] https://lore.kernel.org/linux-arm-msm/20211014083016.137441-6-y.oudjana@protonmail.com/
[2]	https://lore.kernel.org/linux-arm-msm/20211221133937.173618-1-y.oudjana@protonmail.com/
-- 
2.34.1



             reply	other threads:[~2022-01-04 13:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 13:27 Yassine Oudjana [this message]
2022-01-04 13:27 ` [PATCH 1/7] dt-bindings: arm: qcom: Add msm8996 and apq8096 compatibles Yassine Oudjana
2022-01-12  1:10   ` Rob Herring
2022-01-04 13:28 ` [PATCH 2/7] arm64: dts: qcom: msm8996-mtp: Add msm8996 compatible Yassine Oudjana
2022-01-04 13:28 ` [PATCH 3/7] dt-bindings: opp: qcom-opp: Convert to DT schema Yassine Oudjana
2022-01-12  1:11   ` Rob Herring
2022-01-04 13:28 ` [PATCH v2 4/7] dt-bindings: opp: Convert qcom-nvmem-cpufreq " Yassine Oudjana
2022-01-12  1:16   ` Rob Herring
2022-01-04 13:29 ` [PATCH 5/7] arm64: dts: qcom: msm8996: Rename cluster OPP tables Yassine Oudjana
2022-01-04 13:29 ` [PATCH 6/7] arm64: dts: qcom: qcs404: Rename CPU and CPR " Yassine Oudjana
2022-01-04 13:30 ` [PATCH 7/7] dt-bindings: power: avs: qcom,cpr: Convert to DT schema Yassine Oudjana
2022-01-12  1:18   ` Rob Herring
2022-01-31 22:06 ` [PATCH 0/7] dt-bindings: Convert multiple Qualcomm OPP and CPUFreq bindings " Bjorn Andersson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220104132618.391799-1-y.oudjana@protonmail.com \
    --to=y.oudjana@protonmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ilia.lin@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nks@flawful.org \
    --cc=nm@ti.com \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).