From: Chen-Yu Tsai <wens@kernel.org>
To: soc@kernel.org
Cc: Chen-Yu Tsai <wens@csie.org>, Jernej Skrabec <jernej@kernel.org>,
Samuel Holland <samuel@sholland.org>,
linux-sunxi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Allwinner SoC device tree changes for 6.11 part 2
Date: Thu, 11 Jul 2024 02:11:59 +0800 [thread overview]
Message-ID: <Zo7O73Afx7lZcBRi@wens.tw> (raw)
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
Hi Arnd,
Here's a late DT commit for 6.11. The driver parts of the H616 crypto
engine series was only merged last week, so I only got to it today.
The whole series has been tested by multiple people including me, so
I don't expect any issues. And it's just enabling a new IP block.
Please pull.
Thanks
ChenYu
The following changes since commit 0ce1d34678e5d214746ee4887f9f7714c39e331f:
riscv: dts: allwinner: Add ClockworkPi and DevTerm devicetrees (2024-06-30 23:06:52 +0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git tags/sunxi-dt-for-6.11-2
for you to fetch changes up to 6ed9a85f1c44d7049cf2d488bfe71252ce467dc2:
arm64: dts: allwinner: h616: add crypto engine node (2024-07-11 00:43:10 +0800)
----------------------------------------------------------------
Allwinner SoC device tree changes for 6.11 part 2
One additional peripheral enabled for the H616.
- H616 crypto engine added
----------------------------------------------------------------
Andre Przywara (1):
arm64: dts: allwinner: h616: add crypto engine node
arch/arm64/boot/dts/allwinner/sun50i-h616.dtsi | 10 ++++++++++
1 file changed, 10 insertions(+)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-07-10 18:12 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=Zo7O73Afx7lZcBRi@wens.tw \
--to=wens@kernel.org \
--cc=jernej@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 NNTP newsgroup(s).