From: Jayesh Choudhary <j-choudhary@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <devicetree@vger.kernel.org>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <j-choudhary@ti.com>
Subject: [PATCH v2 0/2] Enable SA2UL support on AM64X
Date: Mon, 11 Jul 2022 14:27:41 +0530 [thread overview]
Message-ID: <20220711085743.10128-1-j-choudhary@ti.com> (raw)
This series enables sa2ul support for TI SoC AM64X.
It is based on another series posted by Suman Anna:
<https://lore.kernel.org/linux-arm-kernel/20210514210725.32720-1-s-anna@ti.com/>
rng node has been disabled due to its indirect access from OP-TEE.
Since the sa2ul hardware is being used by OP-TEE as well,
it should be requested using shared TI-SCI flag. So the flag
has been changed from TI-SCI-EXCLUSIVE to TI-SCI-SHARED.
I have tried crypto tests on my local setup, and tcrypt and
self-tests are passing.
Changes from v1:
- disable rng node instead of dropping it
Peter Ujfalusi (1):
arm64: dts: ti: k3-am64-main: Enable crypto accelerator
Suman Anna (1):
arm64: dts: ti: k3-am64: Add SA2UL address space to Main CBASS ranges
arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 20 ++++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am64.dtsi | 1 +
2 files changed, 21 insertions(+)
--
2.17.1
next reply other threads:[~2022-07-11 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 8:57 Jayesh Choudhary [this message]
2022-07-11 8:57 ` [PATCH v2 1/2] arm64: dts: ti: k3-am64: Add SA2UL address space to Main CBASS ranges Jayesh Choudhary
2022-08-30 13:54 ` Kamlesh Gurudasani
2022-07-11 8:57 ` [PATCH v2 2/2] arm64: dts: ti: k3-am64-main: Enable crypto accelerator Jayesh Choudhary
2022-08-30 14:07 ` Kamlesh Gurudasani
2022-09-01 14:23 ` [PATCH v2 0/2] Enable SA2UL support on AM64X Vignesh Raghavendra
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=20220711085743.10128-1-j-choudhary@ti.com \
--to=j-choudhary@ti.com \
--cc=devicetree@vger.kernel.org \
--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 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).