From: Kevin Hilman <khilman@baylibre.com>
To: soc@kernel.org, arm@kernel.org
Cc: linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: dts: amlogic: updates for v5.13 (round 2)
Date: Fri, 09 Apr 2021 11:14:12 -0700 [thread overview]
Message-ID: <7htuofgwaz.fsf@baylibre.com> (raw)
Arnd, Olof,
A 2nd round of DT changes for Amlogic SoC families.
I'm now aware of the new DT warnings added in the first round and will
work to get those cleaned up next.
Kevin
The following changes since commit 727d93ed3ba67307a82c3ac5ebc7e335265e8b9e:
arm64: dts: meson: add initial device-tree for MeCool KIII Pro (2021-04-05 15:35:39 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git tags/amlogic-dt64-2
for you to fetch changes up to 412c8fa8c3748cc0500b4c86a47dd28254f015f1:
arm64: dts: meson: add GPIO line names to ODROID N2/N2+ (2021-04-07 09:18:41 -0700)
----------------------------------------------------------------
arm64: dts: amlogic: updates for v5.13 (round 2)
- updates/cleanups for Hardkernel Odroid N2/N2+
----------------------------------------------------------------
Christian Hewitt (1):
arm64: dts: meson: remove extra tab from ODROID N2/N2+ ext_mdio node
Hyeonki Hong (2):
arm64: dts: meson: add saradc node to ODROID N2/N2+
arm64: dts: meson: add GPIO line names to ODROID N2/N2+
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dtsi | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 51 insertions(+), 1 deletion(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-04-09 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 18:14 Kevin Hilman [this message]
2021-04-09 19:54 ` [GIT PULL] arm64: dts: amlogic: updates for v5.13 (round 2) Arnd Bergmann
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=7htuofgwaz.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=arm@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@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).