From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@linaro.org>
Subject: [PATCH 3/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Add QCM2290
Date: Wed, 08 Mar 2023 02:27:00 +0100 [thread overview]
Message-ID: <20230308-topic-cpufreq_bindings-v1-3-3368473ec52d@linaro.org> (raw)
In-Reply-To: <20230308-topic-cpufreq_bindings-v1-0-3368473ec52d@linaro.org>
Document the OSM CPUFREQ_HW present on QCM2290, featuring just one
lonely frequency domain.
Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
---
.../bindings/cpufreq/cpufreq-qcom-hw.yaml | 24 ++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml
index 6f97e2effaca..dc4e497b15ac 100644
--- a/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml
+++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-qcom-hw.yaml
@@ -21,6 +21,7 @@ properties:
- description: v1 of CPUFREQ HW
items:
- enum:
+ - qcom,qcm2290-cpufreq-hw
- qcom,sc7180-cpufreq-hw
- qcom,sdm845-cpufreq-hw
- qcom,sm6115-cpufreq-hw
@@ -92,6 +93,29 @@ required:
additionalProperties: false
allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ enum:
+ - qcom,qcm2290-cpufreq-hw
+ then:
+ properties:
+ reg:
+ minItems: 1
+ maxItems: 1
+
+ reg-names:
+ minItems: 1
+ maxItems: 1
+
+ interrupts:
+ minItems: 1
+ maxItems: 1
+
+ interrupt-names:
+ minItems: 1
+
- if:
properties:
compatible:
--
2.39.2
next prev parent reply other threads:[~2023-03-08 1:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 1:26 [PATCH 0/8] qcom-cpufreq-hw binding improvements Konrad Dybcio
2023-03-08 1:26 ` [PATCH 1/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Allow just 1 frequency domain Konrad Dybcio
2023-03-16 22:36 ` Rob Herring
2023-03-08 1:26 ` [PATCH 2/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Sanitize data per compatible Konrad Dybcio
2023-03-16 22:39 ` Rob Herring
2023-03-08 1:27 ` Konrad Dybcio [this message]
2023-03-16 22:39 ` [PATCH 3/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Add QCM2290 Rob Herring
2023-03-08 1:27 ` [PATCH 4/8] arm64: dts: qcom: sc7180: Add SoC-specific compatible to cpufreq_hw Konrad Dybcio
2023-03-08 1:27 ` [PATCH 5/8] arm64: dts: qcom: sdm845: " Konrad Dybcio
2023-03-08 1:27 ` [PATCH 6/8] arm64: dts: qcom: sm6115: " Konrad Dybcio
2023-03-08 1:27 ` [PATCH 7/8] arm64: dts: qcom: sm6350: " Konrad Dybcio
2023-03-08 10:35 ` Luca Weiss
2023-03-08 1:27 ` [PATCH 8/8] arm64: dts: qcom: sm8150: " Konrad Dybcio
2023-03-22 14:45 ` (subset) [PATCH 0/8] qcom-cpufreq-hw binding improvements Bjorn Andersson
2023-03-30 3:59 ` Viresh Kumar
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=20230308-topic-cpufreq_bindings-v1-3-3368473ec52d@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mani@kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@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