From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: catalin.marinas@arm.com, davem@davemloft.net,
herbert@gondor.apana.org.au, linux@armlinux.org.uk,
mark.rutland@arm.com, mripard@kernel.org, robh+dt@kernel.org,
wens@csie.org, will@kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sunxi@googlegroups.com,
Corentin Labbe <clabbe.montjoie@gmail.com>
Subject: [PATCH v5 04/11] ARM: dts: sun8i: R40: add crypto engine node
Date: Wed, 16 Oct 2019 17:01:24 +0200 [thread overview]
Message-ID: <20191016150131.15430-5-clabbe.montjoie@gmail.com> (raw)
In-Reply-To: <20191016150131.15430-1-clabbe.montjoie@gmail.com>
The Crypto Engine is a hardware cryptographic offloader that supports
many algorithms.
It could be found on most Allwinner SoCs.
This patch enables the Crypto Engine on the Allwinner R40 SoC Device-tree.
Signed-off-by: Corentin Labbe <clabbe.montjoie@gmail.com>
---
arch/arm/boot/dts/sun8i-r40.dtsi | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-r40.dtsi b/arch/arm/boot/dts/sun8i-r40.dtsi
index c9c2688db66d..421dfbbfd7ee 100644
--- a/arch/arm/boot/dts/sun8i-r40.dtsi
+++ b/arch/arm/boot/dts/sun8i-r40.dtsi
@@ -266,6 +266,15 @@
#phy-cells = <1>;
};
+ crypto: crypto@1c15000 {
+ compatible = "allwinner,sun8i-r40-crypto";
+ reg = <0x01c15000 0x1000>;
+ interrupts = <GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&ccu CLK_BUS_CE>, <&ccu CLK_CE>;
+ clock-names = "bus", "mod";
+ resets = <&ccu RST_BUS_CE>;
+ };
+
ehci1: usb@1c19000 {
compatible = "allwinner,sun8i-r40-ehci", "generic-ehci";
reg = <0x01c19000 0x100>;
--
2.21.0
next prev parent reply other threads:[~2019-10-16 15:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 15:01 [PATCH v5 00/11] crypto: add sun8i-ce driver for Allwinner crypto engine Corentin Labbe
2019-10-16 15:01 ` [PATCH v5 01/11] crypto: Add allwinner subdirectory Corentin Labbe
2019-10-16 15:01 ` [PATCH v5 02/11] crypto: Add Allwinner sun8i-ce Crypto Engine Corentin Labbe
2019-10-16 15:01 ` [PATCH v5 03/11] dt-bindings: crypto: Add DT bindings documentation for " Corentin Labbe
2019-10-16 15:01 ` Corentin Labbe [this message]
2019-10-16 15:01 ` [PATCH v5 05/11] ARM: dts: sun8i: H3: Add Crypto Engine node Corentin Labbe
2019-10-16 15:01 ` [PATCH v5 06/11] ARM64: dts: allwinner: sun50i: Add Crypto Engine node on A64 Corentin Labbe
2019-10-16 15:01 ` [PATCH v5 07/11] ARM64: dts: allwinner: sun50i: Add crypto engine node on H5 Corentin Labbe
2019-10-16 15:01 ` [PATCH v5 08/11] ARM64: dts: allwinner: sun50i: Add Crypto Engine node on H6 Corentin Labbe
2019-10-16 15:01 ` [PATCH v5 09/11] sunxi_defconfig: add new Allwinner crypto options Corentin Labbe
2019-10-16 15:01 ` [PATCH v5 10/11] arm64: defconfig: " Corentin Labbe
2019-10-16 15:01 ` [PATCH v5 11/11] crypto: sun4i-ss: Move to Allwinner directory Corentin Labbe
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=20191016150131.15430-5-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.org \
--cc=will@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).