devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Vaibhav Gupta <vaibhavgupta40@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Kishon Vijay Abraham <kishon@ti.com>,
	Sekhar Nori <nsekhar@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>,
	Praneeth Bajjuri <praneeth@ti.com>,
	Gowtham Tammana <g-tammana@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am64-main: Enable crypto accelerator
Date: Tue, 18 May 2021 07:01:33 -0500	[thread overview]
Message-ID: <20210518120133.73qmsd6uu6dwtjfu@backshift> (raw)
In-Reply-To: <20210518062630.144154-1-vaibhavgupta40@gmail.com>

On 11:56-20210518, Vaibhav Gupta wrote:
> From: Vaibhav Gupta <v_gupta@ti.com>
> 
> Add the node for SA2UL including the random number generator.
> 
> [v_gupta@ti.com: Add address ranges entry in cbass_main]
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> Signed-off-by: Vaibhav Gupta <v_gupta@ti.com>


I see that you have missed the series Suman posted in [1]. It has a few
cleanups of interest.

> ---
>  arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 25 ++++++++++++++++++++++++
>  arch/arm64/boot/dts/ti/k3-am64.dtsi      |  1 +
>  2 files changed, 26 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
> index 25b702303637..adbc3c0673f3 100644
> --- a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
> @@ -160,6 +160,31 @@ k3_reset: reset-controller {
>  		};
>  	};
>  
> +	main_crypto: crypto@40900000 {
> +		compatible = "ti,am64-sa2ul";
> +		reg = <0x0 0x40900000 0x0 0x1200>;
> +		power-domains = <&k3_pds 133 TI_SCI_PD_EXCLUSIVE>;
> +		clocks = <&k3_clks 133 0>, <&k3_clks 133 1>, <&k3_clks 133 2>;
> +		clock-names = "pka_in_clk" , "x1_clk" , "x2_clk";
> +		#address-cells = <2>;
> +		#size-cells = <2>;
> +		ranges = <0x0 0x040900000 0x00 0x040900000 0x0 0x30000>;
> +
> +		status = "okay";
drop this..
> +
> +		dmas = <&main_pktdma 0xc001 15>, <&main_pktdma 0x4002 15>,
> +				<&main_pktdma 0x4003 15>;
> +		dma-names = "tx", "rx1", "rx2";
> +
> +		eip76d_rng: rng@40910000 {
> +			compatible = "inside-secure,safexcel-eip76";
> +			reg = <0x0 0x40910000 0x0 0x80>;
> +			interrupts = <GIC_SPI 168 IRQ_TYPE_LEVEL_HIGH>;
> +			clocks = <&k3_clks 133 2>;
> +			clock-names = "x2_clk";
> +		};
> +	};
> +
>  	main_pmx0: pinctrl@f4000 {
>  		compatible = "pinctrl-single";
>  		reg = <0x00 0xf4000 0x00 0x2d0>;
> diff --git a/arch/arm64/boot/dts/ti/k3-am64.dtsi b/arch/arm64/boot/dts/ti/k3-am64.dtsi
> index 0ae8c844c482..e2bea44a16c5 100644
> --- a/arch/arm64/boot/dts/ti/k3-am64.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am64.dtsi
> @@ -85,6 +85,7 @@ cbass_main: bus@f4000 {
>  			 <0x00 0x78000000 0x00 0x78000000 0x00 0x00800000>, /* Main R5FSS */
>  			 <0x06 0x00000000 0x06 0x00000000 0x01 0x00000000>, /* PCIe DAT1 */
>  			 <0x05 0x00000000 0x05 0x00000000 0x01 0x00000000>, /* FSS0 DAT3 */
> +			 <0x00 0x40900000 0x00 0x40900000 0x00 0x00030000>, /* SA2UL */
>  
>  			 /* MCU Domain Range */
>  			 <0x00 0x04000000 0x00 0x04000000 0x00 0x01ff1400>;


I think you might have missed the discussion here:[1]
a) Could I suggest you co-ordinate with Suman as to which series should
   I consider? Suman's looks a lot complete..
b) Considering the potential for TF-A booting Linux without u-boot on HS
   devices, may I suggest making sure that the dts board files for evm have the
   nodes disabled by default?

[1] https://lore.kernel.org/linux-arm-kernel/20210514221148.m42zldo6lfxn5l4m@underfed/

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

      reply	other threads:[~2021-05-18 12:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  6:26 [PATCH v2] arm64: dts: ti: k3-am64-main: Enable crypto accelerator Vaibhav Gupta
2021-05-18 12:01 ` Nishanth Menon [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=20210518120133.73qmsd6uu6dwtjfu@backshift \
    --to=nm@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=g-tammana@ti.com \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=nsekhar@ti.com \
    --cc=praneeth@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vaibhavgupta40@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;
as well as URLs for NNTP newsgroup(s).