From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
krzk+dt@kernel.org
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
robh@kernel.org, conor+dt@kernel.org, andrew@lunn.ch,
sebastian.hesselbarth@gmail.com, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com, atenart@kernel.org,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v2 3/4] arm64: dts: marvell: Add SoC specific compatibles to SafeXcel crypto
Date: Thu, 22 Jan 2026 10:28:01 +0100 [thread overview]
Message-ID: <87ikcukndq.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <20260112145558.54644-4-angelogioacchino.delregno@collabora.com>
AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
writes:
> Following the changes in the binding for the SafeXcel crypto
> engine, add SoC specific compatibles to the existing nodes in
> Armada 37xx and CP11x.
>
Applied on mvebu/dt64
Thanks,
Gregory
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> arch/arm64/boot/dts/marvell/armada-37xx.dtsi | 3 ++-
> arch/arm64/boot/dts/marvell/armada-cp11x.dtsi | 3 ++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/marvell/armada-37xx.dtsi b/arch/arm64/boot/dts/marvell/armada-37xx.dtsi
> index c612317043ea..87f9367aec12 100644
> --- a/arch/arm64/boot/dts/marvell/armada-37xx.dtsi
> +++ b/arch/arm64/boot/dts/marvell/armada-37xx.dtsi
> @@ -427,7 +427,8 @@ xor11 {
> };
>
> crypto: crypto@90000 {
> - compatible = "inside-secure,safexcel-eip97ies";
> + compatible = "marvell,armada-3700-crypto",
> + "inside-secure,safexcel-eip97ies";
> reg = <0x90000 0x20000>;
> interrupts = <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>,
> <GIC_SPI 21 IRQ_TYPE_LEVEL_HIGH>,
> diff --git a/arch/arm64/boot/dts/marvell/armada-cp11x.dtsi b/arch/arm64/boot/dts/marvell/armada-cp11x.dtsi
> index d9d409eac259..39599171d51b 100644
> --- a/arch/arm64/boot/dts/marvell/armada-cp11x.dtsi
> +++ b/arch/arm64/boot/dts/marvell/armada-cp11x.dtsi
> @@ -512,7 +512,8 @@ CP11X_LABEL(sdhci0): mmc@780000 {
> };
>
> CP11X_LABEL(crypto): crypto@800000 {
> - compatible = "inside-secure,safexcel-eip197b";
> + compatible = "marvell,armada-cp110-crypto",
> + "inside-secure,safexcel-eip197b";
> reg = <0x800000 0x200000>;
> interrupts = <88 IRQ_TYPE_LEVEL_HIGH>,
> <89 IRQ_TYPE_LEVEL_HIGH>,
> --
> 2.52.0
>
--
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-22 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 14:55 [PATCH v2 0/4] Fixes for EIP97/EIP197 binding and devicetrees AngeloGioacchino Del Regno
2026-01-12 14:55 ` [PATCH v2 1/4] dt-bindings: crypto: inside-secure,safexcel: Add SoC compatibles AngeloGioacchino Del Regno
2026-01-13 22:36 ` Rob Herring (Arm)
2026-01-12 14:55 ` [PATCH v2 2/4] dt-bindings: crypto: inside-secure,safexcel: Mandate only ring IRQs AngeloGioacchino Del Regno
2026-01-13 22:37 ` Rob Herring (Arm)
2026-01-12 14:55 ` [PATCH v2 3/4] arm64: dts: marvell: Add SoC specific compatibles to SafeXcel crypto AngeloGioacchino Del Regno
2026-01-22 9:28 ` Gregory CLEMENT [this message]
2026-01-12 14:55 ` [PATCH v2 4/4] arm64: dts: mediatek: mt7986a: Change compatible for " AngeloGioacchino Del Regno
2026-01-14 8:32 ` (subset) [PATCH v2 0/4] Fixes for EIP97/EIP197 binding and devicetrees AngeloGioacchino Del Regno
2026-01-21 18:43 ` Rob Herring
2026-01-31 2:51 ` Herbert Xu
2026-01-31 2:52 ` Herbert Xu
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=87ikcukndq.fsf@BLaptop.bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=atenart@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/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