From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] arm64: dts: marvell: cp110: enable the crypto engine at the SoC level
Date: Thu, 15 Jun 2017 18:25:57 +0200 [thread overview]
Message-ID: <87eful6wve.fsf@free-electrons.com> (raw)
In-Reply-To: <20170615121004.32257-1-antoine.tenart@free-electrons.com> (Antoine Tenart's message of "Thu, 15 Jun 2017 14:10:02 +0200")
Hi Antoine,
On jeu., juin 15 2017, Antoine Tenart <antoine.tenart@free-electrons.com> wrote:
> Enable the cryptographic engine at the SoC level on the master cp110.
> This engine is always present and do not depends on any pinmux
> configuration.
>
> Signed-off-by: Antoine Tenart <antoine.tenart@free-electrons.com>
Applied on mvebu/dt64
Thanks,
Gregory
> ---
> arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi b/arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi
> index c4294403276b..54cc3fc7b6a4 100644
> --- a/arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi
> +++ b/arch/arm64/boot/dts/marvell/armada-cp110-master.dtsi
> @@ -245,7 +245,6 @@
> "ring2", "ring3", "eip";
> clocks = <&cpm_syscon0 1 26>;
> dma-mask = <0xff 0xffffffff>;
> - status = "disabled";
> };
> };
>
> --
> 2.9.4
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2017-06-15 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 12:10 [PATCH v2 1/3] arm64: dts: marvell: cp110: enable the crypto engine at the SoC level Antoine Tenart
2017-06-15 12:10 ` [PATCH v2 2/3] arm64: dts: marvell: remove cpm crypto nodes from dts files Antoine Tenart
2017-06-15 16:27 ` Gregory CLEMENT
2017-06-15 12:10 ` [PATCH v2 3/3] arm64: dts: marvell: add a comment on the cp110 slave node status Antoine Tenart
2017-06-15 16:27 ` Gregory CLEMENT
2017-06-15 16:25 ` Gregory CLEMENT [this message]
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=87eful6wve.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.