From: Christian Marangi <ansuelsmth@gmail.com>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Christian Marangi <ansuelsmth@gmail.com>
Subject: [PATCH] dt-bindings: arm: qcom: add ipq8064 board variants
Date: Thu, 20 Nov 2025 14:54:32 +0100 [thread overview]
Message-ID: <20251120135435.12824-1-ansuelsmth@gmail.com> (raw)
Document QCOM ipq8064 board variants ipq8062, ipq8065, ipq8066,
ipq8068, ipq8069 now matched by the QCOM cpufreq nvmem driver if
socinfo can't derive the variant from SMEM.
Suggested-by: Rob Herring <robh@kernel.org>
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
---
.../devicetree/bindings/arm/qcom.yaml | 20 +++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index 18b5ed044f9f..0eb1619fede8 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -299,12 +299,32 @@ properties:
- qcom,ipq5424-rdp466
- const: qcom,ipq5424
+ - items:
+ - const: qcom,ipq8062
+ - const: qcom,ipq8064
+
- items:
- enum:
- mikrotik,rb3011
- qcom,ipq8064-ap148
- const: qcom,ipq8064
+ - items:
+ - const: qcom,ipq8065
+ - const: qcom,ipq8064
+
+ - items:
+ - const: qcom,ipq8066
+ - const: qcom,ipq8064
+
+ - items:
+ - const: qcom,ipq8068
+ - const: qcom,ipq8064
+
+ - items:
+ - const: qcom,ipq8069
+ - const: qcom,ipq8064
+
- items:
- enum:
- qcom,ipq8074-hk01
--
2.51.0
next reply other threads:[~2025-11-20 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 13:54 Christian Marangi [this message]
2025-11-20 15:25 ` [PATCH] dt-bindings: arm: qcom: add ipq8064 board variants Konrad Dybcio
2025-11-20 15:31 ` Christian Marangi
2025-11-20 17:41 ` Rob Herring
2025-11-20 22:49 ` Christian Marangi
2025-11-21 9:19 ` Konrad Dybcio
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=20251120135435.12824-1-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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).