From: Hariharan K <quic_harihk@quicinc.com>
To: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <quic_srichara@quicinc.com>, <quic_sjaganat@quicinc.com>,
<quic_kathirav@quicinc.com>, <quic_arajkuma@quicinc.com>,
<quic_anusha@quicinc.com>
Subject: [PATCH 1/2] dt-bindings: arm: qcom: document MI04.1 board based on IPQ5332 family
Date: Tue, 6 Jun 2023 15:27:31 +0530 [thread overview]
Message-ID: <20230606095732.12884-2-quic_harihk@quicinc.com> (raw)
In-Reply-To: <20230606095732.12884-1-quic_harihk@quicinc.com>
Document the MI04.1 (Reference Design Platform 446) board based on IPQ5332
family of SoCs.
Signed-off-by: Hariharan K <quic_harihk@quicinc.com>
---
Documentation/devicetree/bindings/arm/qcom.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index 8302d1ee280d..165a815337f7 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -93,6 +93,7 @@ description: |
ap-mi01.2
ap-mi01.3
ap-mi01.6
+ ap-mi04.1
cdp
cp01-c1
dragonboard
@@ -340,6 +341,7 @@ properties:
- qcom,ipq5332-ap-mi01.2
- qcom,ipq5332-ap-mi01.3
- qcom,ipq5332-ap-mi01.6
+ - qcom,ipq5332-ap-mi04.1
- const: qcom,ipq5332
- items:
--
2.17.1
next prev parent reply other threads:[~2023-06-06 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 9:57 [PATCH 0/2] Add initial support for RDP446 of IPQ5332 family Hariharan K
2023-06-06 9:57 ` Hariharan K [this message]
2023-06-06 11:28 ` [PATCH 1/2] dt-bindings: arm: qcom: document MI04.1 board based on " Krzysztof Kozlowski
2023-06-13 23:04 ` Bjorn Andersson
2023-06-14 10:40 ` Hariharan K
2023-06-06 9:57 ` [PATCH 2/2] arm64: dts: qcom: ipq5332: add support for the RDP446 variant Hariharan K
2023-06-14 10:43 ` Konrad Dybcio
2023-06-14 10:59 ` Hariharan K
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=20230606095732.12884-2-quic_harihk@quicinc.com \
--to=quic_harihk@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_anusha@quicinc.com \
--cc=quic_arajkuma@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=robh+dt@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