From: Rajendra Nayak <rnayak@codeaurora.org>
To: agross@kernel.org, bjorn.andersson@linaro.org, robh+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, skakit@codeaurora.org,
konrad.dybcio@somainline.org, swboyd@chromium.org,
dianders@chromium.org, mka@chromium.org,
Rajendra Nayak <rnayak@codeaurora.org>
Subject: [PATCH v2 1/2] dt-bindings: arm: qcom: Document qcom,sc7280-idp2 board
Date: Wed, 4 Aug 2021 18:33:18 +0530 [thread overview]
Message-ID: <1628082199-17002-2-git-send-email-rnayak@codeaurora.org> (raw)
In-Reply-To: <1628082199-17002-1-git-send-email-rnayak@codeaurora.org>
Document the qcom,sc7280-idp2 board based off sc7280 SoC,
The board is also known as piglin in the Chrome OS builds,
so document the google,piglin compatible as well.
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
---
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 7163e5f..8c07690 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -187,6 +187,8 @@ properties:
- items:
- enum:
- qcom,sc7280-idp
+ - qcom,sc7280-idp2
+ - google,piglin
- google,senor
- const: qcom,sc7280
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2021-08-04 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 13:03 [PATCH v2 0/2] Add DT files for sc7280 IDP2 board Rajendra Nayak
2021-08-04 13:03 ` Rajendra Nayak [this message]
2021-08-04 16:28 ` [PATCH v2 1/2] dt-bindings: arm: qcom: Document qcom,sc7280-idp2 board Stephen Boyd
2021-08-04 13:03 ` [PATCH v2 2/2] arm64: dts: qcom: sc7280-idp: Add device tree files for IDP2 Rajendra Nayak
2021-08-04 19:47 ` Konrad Dybcio
2021-08-05 3:27 ` Rajendra Nayak
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=1628082199-17002-2-git-send-email-rnayak@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.org \
--cc=skakit@codeaurora.org \
--cc=swboyd@chromium.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.