From: Jernej Skrabec <jernej@kernel.org>
To: arm@kernel.org, soc@kernel.org
Cc: wens@csie.org, samuel@sholland.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Subject: [GIT PULL] Allwinner device tree changes for 6.10, part 2
Date: Sat, 27 Apr 2024 15:30:06 +0200 [thread overview]
Message-ID: <20240427133006.GA146501@jernej-laptop> (raw)
Hi!
Here are some last minute DT changes. They apply on top of
sunxi-dt-for-6.10-1.
Best regards,
Jernej
The following changes since commit fd46e5e136a83f61c1746d5a08686c0c4f4c0706:
arm64: dts: allwinner: h616: Add NMI device node (2024-04-26 17:50:16 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git tags/sunxi-dt-for-6.10-2
for you to fetch changes up to 0d185df6c9ff841be2460d2f4610de22f326d5dc:
arm64: dts: allwinner: h700: Add RG35XX-H DTS (2024-04-27 15:21:00 +0200)
----------------------------------------------------------------
- new boards: RG35XX 2024, RG35XX-Plus, RG35XX-H
----------------------------------------------------------------
Ryan Walklin (4):
dt-bindings: arm: sunxi: document Anbernic RG35XX handheld gaming device variants
arm64: dts: allwinner: h700: Add RG35XX 2024 DTS
arm64: dts: allwinner: h700: Add RG35XX-Plus DTS
arm64: dts: allwinner: h700: Add RG35XX-H DTS
Documentation/devicetree/bindings/arm/sunxi.yaml | 15 +
arch/arm64/boot/dts/allwinner/Makefile | 3 +
.../allwinner/sun50i-h700-anbernic-rg35xx-2024.dts | 327 +++++++++++++++++++++
.../allwinner/sun50i-h700-anbernic-rg35xx-h.dts | 36 +++
.../allwinner/sun50i-h700-anbernic-rg35xx-plus.dts | 53 ++++
5 files changed, 434 insertions(+)
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-2024.dts
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-h.dts
create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-plus.dts
reply other threads:[~2024-04-27 13:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240427133006.GA146501@jernej-laptop \
--to=jernej@kernel.org \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=soc@kernel.org \
--cc=wens@csie.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 read-only IMAP folder(s) and NNTP newsgroup(s).