From: Kathiravan T <quic_kathirav@quicinc.com>
To: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Kathiravan T <quic_kathirav@quicinc.com>
Subject: [PATCH 1/2] arm: qcom: document MI01.6 board based on IPQ5332 family
Date: Thu, 23 Mar 2023 10:19:28 +0530 [thread overview]
Message-ID: <20230323044929.8694-2-quic_kathirav@quicinc.com> (raw)
In-Reply-To: <20230323044929.8694-1-quic_kathirav@quicinc.com>
Document the MI01.6 (Reference Design Platform 468) board based on IPQ5332
family of SoCs.
Signed-off-by: Kathiravan T <quic_kathirav@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 05badce5fedc..a2dacce49197 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -84,6 +84,7 @@ description: |
adp
ap-al02-c7
ap-mi01.2
+ ap-mi01.6
cdp
cp01-c1
dragonboard
@@ -327,6 +328,7 @@ properties:
- items:
- enum:
- qcom,ipq5332-ap-mi01.2
+ - qcom,ipq5332-ap-mi01.6
- const: qcom,ipq5332
- items:
--
2.17.1
next prev parent reply other threads:[~2023-03-23 4:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 4:49 [PATCH 0/2] Add initial support for RDP468 of IPQ5332 family Kathiravan T
2023-03-23 4:49 ` Kathiravan T [this message]
2023-03-23 6:43 ` [PATCH 1/2] arm: qcom: document MI01.6 board based on " Krzysztof Kozlowski
2023-03-23 4:49 ` [PATCH 2/2] arm64: dts: qcom: ipq5332: add support for the RDP468 variant Kathiravan T
2023-03-23 6:44 ` Krzysztof Kozlowski
2023-03-23 10:40 ` kernel test robot
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=20230323044929.8694-2-quic_kathirav@quicinc.com \
--to=quic_kathirav@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.