From: Rob Herring <robh@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Liang Chen <cl@rock-chips.com>,
devicetree@vger.kernel.org
Subject: Re: [RFC PATCH 4/4] arm64: dts: rockchip: add basic dts for Pine64 Quartz64-A
Date: Thu, 15 Jul 2021 10:21:31 -0600 [thread overview]
Message-ID: <20210715162131.GA1184545@robh.at.kernel.org> (raw)
In-Reply-To: <20210710151034.32857-5-pgwipeout@gmail.com>
On Sat, 10 Jul 2021 11:10:34 -0400, Peter Geis wrote:
> Add a basic dts for the Pine64 Quartz64 Model A Single Board Computer.
> This board outputs on uart2 for debug.
>
> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
> ---
> .../devicetree/bindings/arm/rockchip.yaml | 5 +
> arch/arm64/boot/dts/rockchip/Makefile | 1 +
> .../boot/dts/rockchip/rk3566-quartz64-a.dts | 321 ++++++++++++++++++
> 3 files changed, 327 insertions(+)
> create mode 100644 arch/arm64/boot/dts/rockchip/rk3566-quartz64-a.dts
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-07-15 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 15:10 [RFC PATCH 0/4] split rk3568 and rk3566 device trees Peter Geis
2021-07-10 15:10 ` [RFC PATCH 1/4] arm64: dts: rockchip: move rk3568 dtsi to rk356x dtsi Peter Geis
2021-07-10 15:10 ` [RFC PATCH 2/4] arm64: dts: rockchip: split rk3568 device tree Peter Geis
2021-07-10 15:10 ` [RFC PATCH 3/4] arm64: dts: rockchip: add rk3566 dtsi Peter Geis
2021-07-10 15:10 ` [RFC PATCH 4/4] arm64: dts: rockchip: add basic dts for Pine64 Quartz64-A Peter Geis
2021-07-15 16:21 ` Rob Herring [this message]
2021-07-20 16:19 ` Peter Geis
2021-07-28 17:25 ` Rob Herring
2021-07-23 12:02 ` [RFC PATCH 0/4] split rk3568 and rk3566 device trees Heiko Stuebner
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=20210715162131.GA1184545@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.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;
as well as URLs for NNTP newsgroup(s).