From: Shawn Guo <shawnguo@kernel.org>
To: Chris Healy <cphealy@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Stefan Agner <stefan@agner.ch>, Rob Herring <robh+dt@kernel.org>,
linux ARM <linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrey Smirnov <andrew.smirnov@gmail.com>
Subject: Re: [PATCH] ARM: dts: vfxxx: Add node for CAAM
Date: Mon, 13 Jul 2020 14:33:24 +0800 [thread overview]
Message-ID: <20200713063323.GE12113@dragon> (raw)
In-Reply-To: <CAFXsbZoeTyRp7bwjBUcXT5H2GhrTmNeeoQSFcgiS9aNRFw6V_g@mail.gmail.com>
On Sat, Jul 04, 2020 at 06:40:43PM -0700, Chris Healy wrote:
> Add node for CAAM device in NXP Vybrid SoC.
>
> Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
> Signed-off-by: Chris Healy <cphealy@gmail.com>
> ---
> arch/arm/boot/dts/vfxxx.dtsi | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/arch/arm/boot/dts/vfxxx.dtsi b/arch/arm/boot/dts/vfxxx.dtsi
> index 2d547e7b21ad..0fe03aa0367f 100644
> --- a/arch/arm/boot/dts/vfxxx.dtsi
> +++ b/arch/arm/boot/dts/vfxxx.dtsi
> @@ -729,6 +729,28 @@
> dma-names = "rx","tx";
> status = "disabled";
> };
> +
> + crypto: crypto@400f0000 {
> + compatible = "fsl,sec-v4.0";
Please use tab for indentation.
Shawn
> + #address-cells = <1>;
> + #size-cells = <1>;
> + reg = <0x400f0000 0x9000>;
> + ranges = <0 0x400f0000 0x9000>;
> + clocks = <&clks VF610_CLK_CAAM>;
> + clock-names = "ipg";
> +
> + sec_jr0: jr0@1000 {
> + compatible = "fsl,sec-v4.0-job-ring";
> + reg = <0x1000 0x1000>;
> + interrupts = <102 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + sec_jr1: jr1@2000 {
> + compatible = "fsl,sec-v4.0-job-ring";
> + reg = <0x2000 0x1000>;
> + interrupts = <102 IRQ_TYPE_LEVEL_HIGH>;
> + };
> + };
> };
> };
> };
> --
> 2.21.3
prev parent reply other threads:[~2020-07-13 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 1:40 [PATCH] ARM: dts: vfxxx: Add node for CAAM Chris Healy
2020-07-13 6:33 ` Shawn Guo [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=20200713063323.GE12113@dragon \
--to=shawnguo@kernel.org \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=stefan@agner.ch \
/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).