From: Parikshit Pareek <quic_ppareek@quicinc.com>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Andrew Halaney <ahalaney@redhat.com>,
"Shazad Hussain" <quic_shazhuss@quicinc.com>,
Brian Masney <bmasney@redhat.com>,
"Johan Hovold" <johan@kernel.org>,
Parikshit Pareek <quic_ppareek@quicinc.com>
Subject: [PATCH v6 1/2] dt-bindings: arm: qcom: Document additional sa8540p device
Date: Thu, 20 Oct 2022 13:00:35 +0530 [thread overview]
Message-ID: <20221020073036.16656-2-quic_ppareek@quicinc.com> (raw)
In-Reply-To: <20221020073036.16656-1-quic_ppareek@quicinc.com>
Add the qdrive3 ride device to the valid device compatibles found on the
sa8540p platform.
Signed-off-by: Parikshit Pareek <quic_ppareek@quicinc.com>
---
Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index 207e28260206..f12b1ff19337 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -687,6 +687,7 @@ properties:
- items:
- enum:
- qcom,sa8295p-adp
+ - qcom,sa8540p-ride
- const: qcom,sa8540p
- items:
--
2.17.1
next prev parent reply other threads:[~2022-10-20 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 7:30 [PATCH v6 0/2] arm64: dts: qcom: add dts for sa8540p-ride board Parikshit Pareek
2022-10-20 7:30 ` Parikshit Pareek [this message]
2022-10-20 13:46 ` [PATCH v6 1/2] dt-bindings: arm: qcom: Document additional sa8540p device Krzysztof Kozlowski
2022-10-20 16:33 ` Brian Masney
2022-10-20 7:30 ` [PATCH v6 2/2] arm64: dts: qcom: add SA8540P ride(Qdrive-3) Parikshit Pareek
2022-10-20 11:49 ` konrad.dybcio
2022-10-28 7:50 ` Parikshit Pareek
2022-10-28 8:28 ` Brian Masney
2022-10-20 16:39 ` Brian Masney
2022-11-02 7:35 ` Shazad Hussain
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=20221020073036.16656-2-quic_ppareek@quicinc.com \
--to=quic_ppareek@quicinc.com \
--cc=agross@kernel.org \
--cc=ahalaney@redhat.com \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_shazhuss@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