From: Suman Anna <s-anna@ti.com> To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org> Cc: Gowtham Tammana <g-tammana@ti.com>, Praneeth Bajjuri <praneeth@ti.com>, Vaibhav Gupta <v_gupta@ti.com>, <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, Suman Anna <s-anna@ti.com> Subject: [PATCH 1/3] arm64: dts: ti: k3-j7200-mcu: Add the mcu sa2ul crypto node Date: Fri, 14 May 2021 16:07:22 -0500 [thread overview] Message-ID: <20210514210725.32720-2-s-anna@ti.com> (raw) In-Reply-To: <20210514210725.32720-1-s-anna@ti.com> From: Peter Ujfalusi <peter.ujfalusi@ti.com> Add sa2ul crypto accelarator node. In comparision to j721e, The sa2ul crypto device on j7200 has moved to mcu domain and is available for linux usage as a shared device. Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com> [praneeth@ti.com: picked recommendation from author to k3-j7200-mcu-wakeup.dtsi and verified functionality] Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Gowtham Tammana <g-tammana@ti.com> [s-anna@ti.com: minor formatting cleanups] Signed-off-by: Suman Anna <s-anna@ti.com> --- .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi index 5e74e43822c3..f24bd4af62c8 100644 --- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi +++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi @@ -380,4 +380,24 @@ mcu_r5fss0_core1: r5f@41400000 { ti,loczrama = <1>; }; }; + + mcu_crypto: crypto@40900000 { + compatible = "ti,j721e-sa2ul"; + reg = <0x00 0x40900000 0x00 0x1200>; + power-domains = <&k3_pds 265 TI_SCI_PD_SHARED>; + #address-cells = <2>; + #size-cells = <2>; + ranges = <0x00 0x40900000 0x00 0x40900000 0x00 0x30000>; + dmas = <&mcu_udmap 0xf501>, <&mcu_udmap 0x7502>, + <&mcu_udmap 0x7503>; + dma-names = "tx", "rx1", "rx2"; + dma-coherent; + + rng: rng@40910000 { + compatible = "inside-secure,safexcel-eip76"; + reg = <0x00 0x40910000 0x00 0x7d>; + interrupts = <GIC_SPI 945 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&k3_clks 265 1>; + }; + }; }; -- 2.30.1
WARNING: multiple messages have this Message-ID (diff)
From: Suman Anna <s-anna@ti.com> To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org> Cc: devicetree@vger.kernel.org, Gowtham Tammana <g-tammana@ti.com>, Praneeth Bajjuri <praneeth@ti.com>, Vaibhav Gupta <v_gupta@ti.com>, linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/3] arm64: dts: ti: k3-j7200-mcu: Add the mcu sa2ul crypto node Date: Fri, 14 May 2021 16:07:22 -0500 [thread overview] Message-ID: <20210514210725.32720-2-s-anna@ti.com> (raw) In-Reply-To: <20210514210725.32720-1-s-anna@ti.com> From: Peter Ujfalusi <peter.ujfalusi@ti.com> Add sa2ul crypto accelarator node. In comparision to j721e, The sa2ul crypto device on j7200 has moved to mcu domain and is available for linux usage as a shared device. Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com> [praneeth@ti.com: picked recommendation from author to k3-j7200-mcu-wakeup.dtsi and verified functionality] Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Gowtham Tammana <g-tammana@ti.com> [s-anna@ti.com: minor formatting cleanups] Signed-off-by: Suman Anna <s-anna@ti.com> --- .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi index 5e74e43822c3..f24bd4af62c8 100644 --- a/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi +++ b/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi @@ -380,4 +380,24 @@ mcu_r5fss0_core1: r5f@41400000 { ti,loczrama = <1>; }; }; + + mcu_crypto: crypto@40900000 { + compatible = "ti,j721e-sa2ul"; + reg = <0x00 0x40900000 0x00 0x1200>; + power-domains = <&k3_pds 265 TI_SCI_PD_SHARED>; + #address-cells = <2>; + #size-cells = <2>; + ranges = <0x00 0x40900000 0x00 0x40900000 0x00 0x30000>; + dmas = <&mcu_udmap 0xf501>, <&mcu_udmap 0x7502>, + <&mcu_udmap 0x7503>; + dma-names = "tx", "rx1", "rx2"; + dma-coherent; + + rng: rng@40910000 { + compatible = "inside-secure,safexcel-eip76"; + reg = <0x00 0x40910000 0x00 0x7d>; + interrupts = <GIC_SPI 945 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&k3_clks 265 1>; + }; + }; }; -- 2.30.1 _______________________________________________ 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:[~2021-05-14 21:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-14 21:07 [PATCH 0/3] Add crypto nodes for J7200 and AM64x Suman Anna 2021-05-14 21:07 ` Suman Anna 2021-05-14 21:07 ` Suman Anna [this message] 2021-05-14 21:07 ` [PATCH 1/3] arm64: dts: ti: k3-j7200-mcu: Add the mcu sa2ul crypto node Suman Anna 2021-05-14 21:07 ` [PATCH 2/3] arm64: dts: ti: k3-am64: Add SA2UL address space to Main CBASS ranges Suman Anna 2021-05-14 21:07 ` Suman Anna 2021-05-14 21:07 ` [PATCH 3/3] arm64: dts: ti: k3-am64-main: Enable crypto accelerator Suman Anna 2021-05-14 21:07 ` Suman Anna 2021-05-14 22:11 ` [PATCH 0/3] Add crypto nodes for J7200 and AM64x Nishanth Menon 2021-05-14 22:11 ` Nishanth Menon
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=20210514210725.32720-2-s-anna@ti.com \ --to=s-anna@ti.com \ --cc=devicetree@vger.kernel.org \ --cc=g-tammana@ti.com \ --cc=kristo@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=nm@ti.com \ --cc=praneeth@ti.com \ --cc=v_gupta@ti.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: linkBe 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.