From: Christian Hewitt <christianshewitt@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kevin Hilman <khilman@baylibre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>
Subject: [PATCH v3 0/2] arm64: dts: meson: add support for WeTek Core 2
Date: Sun, 19 Jul 2020 02:14:19 +0000 [thread overview]
Message-ID: <20200719021421.7959-1-christianshewitt@gmail.com> (raw)
From: chewitt <christianshewitt@gmail.com>
This series adds support for the WeTek Core 2 which is a commercial box
device based on the Amlogic Q200 reference design.
v3 changes - fix BT node (enable-gpios > shutdown-gpios)
v2 changes - simplify ethernet disable
Christian Hewitt (2):
dt-bindings: arm: amlogic: add support for the WeTek Core 2
arm64: dts: meson: add support for the WeTek Core 2
.../devicetree/bindings/arm/amlogic.yaml | 1 +
arch/arm64/boot/dts/amlogic/Makefile | 1 +
.../dts/amlogic/meson-gxm-wetek-core2.dts | 87 +++++++++++++++++++
3 files changed, 89 insertions(+)
create mode 100644 arch/arm64/boot/dts/amlogic/meson-gxm-wetek-core2.dts
--
2.17.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2020-07-19 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 2:14 Christian Hewitt [this message]
2020-07-19 2:14 ` [PATCH v3 1/2] dt-bindings: arm: amlogic: add support for the WeTek Core 2 Christian Hewitt
2020-07-19 2:14 ` [PATCH v3 2/2] arm64: dts: meson: " Christian Hewitt
2020-07-21 8:05 ` Neil Armstrong
2020-07-21 21:14 ` [PATCH v3 0/2] arm64: dts: meson: add support for " Kevin Hilman
2020-07-21 21:21 ` patchwork-bot+linux-amlogic
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=20200719021421.7959-1-christianshewitt@gmail.com \
--to=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).