From: Shawn Guo <shawnguo@kernel.org>
To: "Horia Geantă" <horia.geanta@nxp.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Harninder Rai <harninder.rai@nxp.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Bhaskar Upadhaya <Bhaskar.Upadhaya@nxp.com>,
Will Deacon <will.deacon@arm.com>,
Dan Douglass <dan.douglass@nxp.com>,
linux-crypto@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: ls1012a: add crypto node
Date: Fri, 24 Mar 2017 09:56:08 +0800 [thread overview]
Message-ID: <20170324015606.GC30608@dragon> (raw)
In-Reply-To: <20170322122939.22117-1-horia.geanta@nxp.com>
On Wed, Mar 22, 2017 at 02:29:39PM +0200, Horia Geantă wrote:
> LS1012A has a SEC v5.4 security engine.
>
> Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/fsl-ls1012a-frdm.dts | 9 +++
> arch/arm64/boot/dts/freescale/fsl-ls1012a-qds.dts | 9 +++
> arch/arm64/boot/dts/freescale/fsl-ls1012a-rdb.dts | 9 +++
> arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 91 +++++++++++++++++++++-
> 4 files changed, 117 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1012a-frdm.dts b/arch/arm64/boot/dts/freescale/fsl-ls1012a-frdm.dts
> index a619f6496a4c..bab9e68947e4 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1012a-frdm.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1012a-frdm.dts
> @@ -49,6 +49,15 @@
> model = "LS1012A Freedom Board";
> compatible = "fsl,ls1012a-frdm", "fsl,ls1012a";
>
> + aliases {
> + crypto = &crypto;
> + rtic_a = &rtic_a;
> + rtic_b = &rtic_b;
> + rtic_c = &rtic_c;
> + rtic_d = &rtic_d;
> + sec_mon = &sec_mon;
> + };
> +
> sys_mclk: clock-mclk {
> compatible = "fixed-clock";
> #clock-cells = <0>;
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1012a-qds.dts b/arch/arm64/boot/dts/freescale/fsl-ls1012a-qds.dts
> index 14a67f1709e7..5c4e84c7f20d 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1012a-qds.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1012a-qds.dts
> @@ -49,6 +49,15 @@
> model = "LS1012A QDS Board";
> compatible = "fsl,ls1012a-qds", "fsl,ls1012a";
>
> + aliases {
> + crypto = &crypto;
> + rtic_a = &rtic_a;
> + rtic_b = &rtic_b;
> + rtic_c = &rtic_c;
> + rtic_d = &rtic_d;
> + sec_mon = &sec_mon;
> + };
> +
> sys_mclk: clock-mclk {
> compatible = "fixed-clock";
> #clock-cells = <0>;
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1012a-rdb.dts b/arch/arm64/boot/dts/freescale/fsl-ls1012a-rdb.dts
> index 62c5c7123a15..ff9dd16aa65a 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1012a-rdb.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1012a-rdb.dts
> @@ -48,6 +48,15 @@
> / {
> model = "LS1012A RDB Board";
> compatible = "fsl,ls1012a-rdb", "fsl,ls1012a";
> +
> + aliases {
> + crypto = &crypto;
> + rtic_a = &rtic_a;
> + rtic_b = &rtic_b;
> + rtic_c = &rtic_c;
> + rtic_d = &rtic_d;
> + sec_mon = &sec_mon;
> + };
What are these aliases used for? Are they board specific? If not, we
should probably have them in fsl-ls1012a.dtsi, since you are adding
them for all three fsl-ls1012a based boards.
> };
>
> &duart0 {
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi
> index cffebb4b3df1..68f3012ae07e 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi
> @@ -42,7 +42,7 @@
> * OTHER DEALINGS IN THE SOFTWARE.
> */
>
> -#include <dt-bindings/interrupt-controller/irq.h>
> +#include <dt-bindings/interrupt-controller/arm-gic.h>
>
> / {
> compatible = "fsl,ls1012a";
> @@ -113,6 +113,95 @@
> big-endian;
> };
>
> + crypto: crypto@1700000 {
> + compatible = "fsl,sec-v5.4", "fsl,sec-v5.0",
> + "fsl,sec-v4.0";
> + fsl,sec-era = <8>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0 0x00 0x1700000 0x100000>;
> + reg = <0x00 0x1700000 0x0 0x100000>;
> + interrupts = <GIC_SPI 75 IRQ_TYPE_LEVEL_HIGH>;
> +
> + sec_jr0: jr@10000 {
> + compatible = "fsl,sec-v5.4-job-ring",
> + "fsl,sec-v5.0-job-ring",
> + "fsl,sec-v4.0-job-ring";
> + reg = <0x10000 0x10000>;
> + interrupts = <GIC_SPI 71 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + sec_jr1: jr@20000 {
> + compatible = "fsl,sec-v5.4-job-ring",
> + "fsl,sec-v5.0-job-ring",
> + "fsl,sec-v4.0-job-ring";
> + reg = <0x20000 0x10000>;
> + interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + sec_jr2: jr@30000 {
> + compatible = "fsl,sec-v5.4-job-ring",
> + "fsl,sec-v5.0-job-ring",
> + "fsl,sec-v4.0-job-ring";
> + reg = <0x30000 0x10000>;
> + interrupts = <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + sec_jr3: jr@40000 {
> + compatible = "fsl,sec-v5.4-job-ring",
> + "fsl,sec-v5.0-job-ring",
> + "fsl,sec-v4.0-job-ring";
> + reg = <0x40000 0x10000>;
> + interrupts = <GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + rtic@60000 {
> + compatible = "fsl,sec-v5.4-rtic",
> + "fsl,sec-v5.0-rtic",
> + "fsl,sec-v4.0-rtic";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + reg = <0x60000 0x100 0x60e00 0x18>;
> + ranges = <0x0 0x60100 0x500>;
> +
> + rtic_a: rtic-a@0 {
> + compatible = "fsl,sec-v5.4-rtic-memory",
> + "fsl,sec-v5.0-rtic-memory",
> + "fsl,sec-v4.0-rtic-memory";
> + reg = <0x00 0x20 0x100 0x100>;
> + };
> +
> + rtic_b: rtic-b@20 {
> + compatible = "fsl,sec-v5.4-rtic-memory",
> + "fsl,sec-v5.0-rtic-memory",
> + "fsl,sec-v4.0-rtic-memory";
> + reg = <0x20 0x20 0x200 0x100>;
> + };
> +
> + rtic_c: rtic-c@40 {
> + compatible = "fsl,sec-v5.4-rtic-memory",
> + "fsl,sec-v5.0-rtic-memory",
> + "fsl,sec-v4.0-rtic-memory";
> + reg = <0x40 0x20 0x300 0x100>;
> + };
> +
> + rtic_d: rtic-d@60 {
> + compatible = "fsl,sec-v5.4-rtic-memory",
> + "fsl,sec-v5.0-rtic-memory",
> + "fsl,sec-v4.0-rtic-memory";
> + reg = <0x60 0x20 0x400 0x100>;
> + };
> + };
> + };
> +
> + sec_mon: sec_mon@1e90000 {
Hyphen is more preferred to be used in node name than underscore.
Shawn
> + compatible = "fsl,sec-v5.4-mon", "fsl,sec-v5.0-mon",
> + "fsl,sec-v4.0-mon";
> + reg = <0x0 0x1e90000 0x0 0x10000>;
> + interrupts = <GIC_SPI 78 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 79 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> dcfg: dcfg@1ee0000 {
> compatible = "fsl,ls1012a-dcfg",
> "syscon";
> --
> 2.12.0.264.gd6db3f216544
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-03-24 1:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 12:29 [PATCH] arm64: dts: ls1012a: add crypto node Horia Geantă
2017-03-24 1:56 ` Shawn Guo [this message]
2017-03-24 7:17 ` Horia Geantă
2017-03-24 7:34 ` Shawn Guo
2017-03-24 8:29 ` Horia Geantă
[not found] ` <DB4PR04MB0847E3EE8F7FAC11DD85FAA8983E0-tLF+feb1Bz4/w1fYxD+T089NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-03-24 14:03 ` Shawn Guo
2017-03-28 7:19 ` Horia Geantă
2017-03-28 10:41 ` Shawn Guo
2017-03-28 11:46 ` [PATCH v2] " Horia Geantă
2017-03-29 3:04 ` Shawn Guo
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=20170324015606.GC30608@dragon \
--to=shawnguo@kernel.org \
--cc=Bhaskar.Upadhaya@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=dan.douglass@nxp.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=harninder.rai@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).