From: Sheng-Liang Pan <sheng-liang.pan@quanta.corp-partner.google.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: mka@chromium.org, dianders@chromium.org,
Sheng-Liang Pan <sheng-liang.pan@quanta.corp-partner.google.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: [PATCH 0/2] Add a new board device tree named 'evoker' for herobrine variant.
Date: Thu, 1 Sep 2022 17:12:51 +0800 [thread overview]
Message-ID: <20220901091253.93333-1-sheng-liang.pan@quanta.corp-partner.google.com> (raw)
This patch add the initial dts file for new board 'evoker'.
Changes in v2:
- document sc7280 and evoker board
Sheng-Liang Pan (2):
arm64: dts: qcom: sc7280: Add device tree for herobrine evoker
dt-bindings: arm: qcom: document sc7280 and evoker board
.../devicetree/bindings/arm/qcom.yaml | 5 +
arch/arm64/boot/dts/qcom/Makefile | 1 +
.../dts/qcom/sc7280-herobrine-evoker-r0.dts | 333 ++++++++++++++++++
3 files changed, 339 insertions(+)
create mode 100644 arch/arm64/boot/dts/qcom/sc7280-herobrine-evoker-r0.dts
--
2.34.1
next reply other threads:[~2022-09-01 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 9:12 Sheng-Liang Pan [this message]
2022-09-01 9:12 ` [PATCH 1/2] arm64: dts: qcom: sc7280: Add device tree for herobrine evoker Sheng-Liang Pan
2022-09-01 10:01 ` Krzysztof Kozlowski
2022-09-01 15:06 ` Doug Anderson
2022-09-01 9:12 ` [PATCH 2/2] dt-bindings: arm: qcom: document sc7280 and evoker board Sheng-Liang Pan
2022-09-01 10:03 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2022-09-02 7:42 [PATCH 0/2] Add a new board device tree named 'evoker' for herobrine variant Sheng-Liang Pan
2022-09-01 6:13 Sheng-Liang Pan
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=20220901091253.93333-1-sheng-liang.pan@quanta.corp-partner.google.com \
--to=sheng-liang.pan@quanta.corp-partner.google.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.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=mka@chromium.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.