From: James Tai <james.tai@realtek.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: <mark.rutland@arm.com>, <devicetree@vger.kernel.org>,
<linux-realtek-soc@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/2] Initial RTD1319 SoC and Realtek PymParticle EVB support
Date: Thu, 5 Dec 2019 16:25:53 +0800 [thread overview]
Message-ID: <20191205082555.22633-1-james.tai@realtek.com> (raw)
Hi Andreas,
This series adds Device Trees for the Realtek RTD1319 SoC and Realtek's
PymParticle EVB.
Cc: devicetree@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Andreas Färber <afaerber@suse.de>
James Tai (2):
dt-bindings: arm: realtek: Document RTD1319 and Realtek PymParticle
EVB
arm64: dts: realtek: Add RTD1319 SoC and Realtek PymParticle EVB
.../devicetree/bindings/arm/realtek.yaml | 6 +
arch/arm64/boot/dts/realtek/Makefile | 2 +
.../boot/dts/realtek/rtd1319-pymparticle.dts | 43 ++++++
arch/arm64/boot/dts/realtek/rtd1319.dtsi | 12 ++
arch/arm64/boot/dts/realtek/rtd13xx.dtsi | 137 ++++++++++++++++++
5 files changed, 200 insertions(+)
create mode 100644 arch/arm64/boot/dts/realtek/rtd1319-pymparticle.dts
create mode 100644 arch/arm64/boot/dts/realtek/rtd1319.dtsi
create mode 100644 arch/arm64/boot/dts/realtek/rtd13xx.dtsi
--
2.24.0
next reply other threads:[~2019-12-05 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 8:25 James Tai [this message]
2019-12-05 8:25 ` [PATCH 1/2] dt-bindings: arm: realtek: Document RTD1319 and Realtek PymParticle EVB James Tai
2019-12-05 8:33 ` Andreas Färber
2019-12-18 23:28 ` Rob Herring
2019-12-05 8:25 ` [PATCH 2/2] arm64: dts: realtek: Add RTD1319 SoC " James Tai
2019-12-05 10:58 ` Andreas Färber
2019-12-05 12:10 ` Robin Murphy
2019-12-27 7:17 ` James Tai
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=20191205082555.22633-1-james.tai@realtek.com \
--to=james.tai@realtek.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=mark.rutland@arm.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
all inboxes | Powered by JetHome®