From: Richard Acayan <mailingradian@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Vinod Koul <vkoul@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Chanho Park <chanho61.park@samsung.com>,
Thierry Reding <treding@nvidia.com>,
Stephan Gerhold <stephan.gerhold@kernkonzept.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Robert Marko <robimarko@gmail.com>,
Das Srinagesh <quic_gurus@quicinc.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht, phone-devel@vger.kernel.org
Subject: [PATCH 2/4] dt-bindings: arm: qcom: add sdm670 and pixel 3a compatible
Date: Tue, 1 Nov 2022 19:57:20 -0400 [thread overview]
Message-ID: <20221101235722.53955-3-mailingradian@gmail.com> (raw)
In-Reply-To: <20221101235722.53955-1-mailingradian@gmail.com>
The Snapdragon 670 and Pixel 3a initial device trees are about to be
added. Add the compatible strings for the board.
Signed-off-by: Richard Acayan <mailingradian@gmail.com>
---
Documentation/devicetree/bindings/arm/qcom.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index 207e28260206..f9eddc22d4a4 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -51,6 +51,7 @@ description: |
sdm632
sdm636
sdm660
+ sdm670
sdm845
sdx55
sdx65
@@ -654,6 +655,11 @@ properties:
- xiaomi,lavender
- const: qcom,sdm660
+ - items:
+ - enum:
+ - google,sargo
+ - const: qcom,sdm670
+
- items:
- enum:
- qcom,sdx55-mtp
--
2.38.1
next prev parent reply other threads:[~2022-11-01 23:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 23:57 [PATCH 0/4] Initial SDM670 and Pixel 3a support Richard Acayan
2022-11-01 23:57 ` [PATCH 1/4] dt-bindings: arm: cpus: add qcom kryo 360 compatible Richard Acayan
2022-11-02 17:36 ` Rob Herring
2022-11-01 23:57 ` Richard Acayan [this message]
2022-11-02 17:37 ` [PATCH 2/4] dt-bindings: arm: qcom: add sdm670 and pixel 3a compatible Rob Herring
2022-11-01 23:57 ` [PATCH 3/4] dt-bindings: firmware: scm: add sdm670 compatible Richard Acayan
2022-11-02 17:37 ` Rob Herring
2022-11-02 17:51 ` Guru Das Srinagesh
2022-11-01 23:57 ` [PATCH 4/4] arm64: dts: qcom: add sdm670 and pixel 3a device trees Richard Acayan
2022-11-02 2:19 ` Richard Acayan
2022-11-02 20:26 ` Konrad Dybcio
2022-11-02 20:30 ` Krzysztof Kozlowski
2022-11-02 20:44 ` Konrad Dybcio
2022-11-03 0:53 ` Richard Acayan
2022-11-03 1:19 ` Richard Acayan
2022-11-03 20:34 ` 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=20221101235722.53955-3-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=chanho61.park@samsung.com \
--cc=devicetree@vger.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=lpieralisi@kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=quic_gurus@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
--cc=robin.murphy@arm.com \
--cc=stephan.gerhold@kernkonzept.com \
--cc=treding@nvidia.com \
--cc=vkoul@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).