All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jayesh Choudhary <j-choudhary@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <kamlesh@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<j-choudhary@ti.com>
Subject: [PATCH 0/2] Add Crypto Support for J784S4 SoC
Date: Mon, 13 Mar 2023 16:17:19 +0530	[thread overview]
Message-ID: <20230313104721.407071-1-j-choudhary@ti.com> (raw)

This series adds the crypto node for sa2ul for j784s4 platform.

First patch adds the device-id for NAVSS without which the probe
for dma-controller fails due to 'ti,sci-dev-id' read failure.
Second patch adds the crypto node.

This series has functional dependency on j784s4 k3_soc_id[1] and
PSIL-thread support[2] but it does not affect the boot.

[1]:
<https://lore.kernel.org/all/20230313065025.185320-1-j-choudhary@ti.com/>

[2]:
<https://lore.kernel.org/all/20230308201513.116638-1-j-choudhary@ti.com/>

For testing the crypto support, crypto extra tests and self tests were
enabled and tcrypt tests were used to verify SHA-1/256/512, AES and DES3
algorithms.

Testing log:
<https://gist.github.com/Jayesh2000/4fe36337af6f9dc96a055359d5d6f4ca>

Jayesh Choudhary (2):
  arm64: dts: ti: k3-j784s4-main: Add 'ti,sci-dev-id' for main_navss
  arm64: dts: ti: k3-j784s4-main: Enable crypto accelerator

 arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Jayesh Choudhary <j-choudhary@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <kamlesh@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<j-choudhary@ti.com>
Subject: [PATCH 0/2] Add Crypto Support for J784S4 SoC
Date: Mon, 13 Mar 2023 16:17:19 +0530	[thread overview]
Message-ID: <20230313104721.407071-1-j-choudhary@ti.com> (raw)

This series adds the crypto node for sa2ul for j784s4 platform.

First patch adds the device-id for NAVSS without which the probe
for dma-controller fails due to 'ti,sci-dev-id' read failure.
Second patch adds the crypto node.

This series has functional dependency on j784s4 k3_soc_id[1] and
PSIL-thread support[2] but it does not affect the boot.

[1]:
<https://lore.kernel.org/all/20230313065025.185320-1-j-choudhary@ti.com/>

[2]:
<https://lore.kernel.org/all/20230308201513.116638-1-j-choudhary@ti.com/>

For testing the crypto support, crypto extra tests and self tests were
enabled and tcrypt tests were used to verify SHA-1/256/512, AES and DES3
algorithms.

Testing log:
<https://gist.github.com/Jayesh2000/4fe36337af6f9dc96a055359d5d6f4ca>

Jayesh Choudhary (2):
  arm64: dts: ti: k3-j784s4-main: Add 'ti,sci-dev-id' for main_navss
  arm64: dts: ti: k3-j784s4-main: Enable crypto accelerator

 arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

-- 
2.25.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2023-03-13 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 10:47 Jayesh Choudhary [this message]
2023-03-13 10:47 ` [PATCH 0/2] Add Crypto Support for J784S4 SoC Jayesh Choudhary
2023-03-13 10:47 ` [PATCH 1/2] arm64: dts: ti: k3-j784s4-main: Add 'ti,sci-dev-id' for main_navss Jayesh Choudhary
2023-03-13 10:47   ` Jayesh Choudhary
2023-03-13 10:47 ` [PATCH 2/2] arm64: dts: ti: k3-j784s4-main: Enable crypto accelerator Jayesh Choudhary
2023-03-13 10:47   ` Jayesh Choudhary
2023-03-14 11:50 ` [PATCH 0/2] Add Crypto Support for J784S4 SoC Kamlesh Gurudasani
2023-03-14 11:50   ` Kamlesh Gurudasani

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=20230313104721.407071-1-j-choudhary@ti.com \
    --to=j-choudhary@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kamlesh@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@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: 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.