From: Daniel Parks <danielrparks@ti.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: <linux-crypto@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [RFC PATCH 0/6] Add SA2UL Public Key Accelerator driver
Date: Mon, 8 Aug 2022 14:12:49 -0500 [thread overview]
Message-ID: <cover.1659985696.git.danielrparks@ti.com> (raw)
The PKA is a subdevice of the SA2UL that provides hardware acceleration
for asymmetric cryptography algorithms. RSA and Diffie-Hellman are
enabled in this patch series.
Tested using these configurations:
- CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n
- CONFIG_CRYPTO_MANAGER_EXTRA_TESTS=y
These patches are RFC for now because we're waiting for legal to clear
us to release the firmware.
The dts patches depend on [1] and [2], respectively, to apply without
fuzz.
[1]: https://www.spinics.net/lists/devicetree/msg523234.html
[2]: https://www.spinics.net/lists/devicetree/msg523233.html
Daniel Parks (6):
dt-bindings: crypto: ti,sa2ul: add pka subdevice
dt-bindings: crypto: add binding for eip29t2 public key accelerator
(PKA)
arm64: dts: ti: k3-am64-main: add SA2UL public key accelerator
subdevice
arm64: dts: ti: k3-j721e-main: add SA2UL public key accelerator
subdevice
crypto: sa2ul: turn on PKA engine
crypto: sa2ul_pka: Add SA2UL PKA driver
.../inside-secure,safexcel-eip29t2.yaml | 49 ++
.../devicetree/bindings/crypto/ti,sa2ul.yaml | 6 +
arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 8 +
arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 7 +
drivers/crypto/Kconfig | 2 +
drivers/crypto/Makefile | 1 +
drivers/crypto/sa2ul.c | 2 +-
drivers/crypto/sa2ul_pka/Kconfig | 26 +
drivers/crypto/sa2ul_pka/Makefile | 3 +
drivers/crypto/sa2ul_pka/sa2ul_pka.h | 135 +++++
drivers/crypto/sa2ul_pka/sa2ul_pka_base.c | 564 ++++++++++++++++++
drivers/crypto/sa2ul_pka/sa2ul_pka_dh.c | 150 +++++
drivers/crypto/sa2ul_pka/sa2ul_pka_op.c | 205 +++++++
drivers/crypto/sa2ul_pka/sa2ul_pka_op.h | 28 +
drivers/crypto/sa2ul_pka/sa2ul_pka_rsa.c | 193 ++++++
drivers/crypto/sa2ul_pka/sa2ul_pka_sg.c | 316 ++++++++++
16 files changed, 1694 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/crypto/inside-secure,safexcel-eip29t2.yaml
create mode 100644 drivers/crypto/sa2ul_pka/Kconfig
create mode 100644 drivers/crypto/sa2ul_pka/Makefile
create mode 100644 drivers/crypto/sa2ul_pka/sa2ul_pka.h
create mode 100644 drivers/crypto/sa2ul_pka/sa2ul_pka_base.c
create mode 100644 drivers/crypto/sa2ul_pka/sa2ul_pka_dh.c
create mode 100644 drivers/crypto/sa2ul_pka/sa2ul_pka_op.c
create mode 100644 drivers/crypto/sa2ul_pka/sa2ul_pka_op.h
create mode 100644 drivers/crypto/sa2ul_pka/sa2ul_pka_rsa.c
create mode 100644 drivers/crypto/sa2ul_pka/sa2ul_pka_sg.c
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-08-08 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 19:12 Daniel Parks [this message]
2022-08-08 19:12 ` [RFC PATCH 1/6] dt-bindings: crypto: ti,sa2ul: add pka subdevice Daniel Parks
2022-08-09 5:44 ` Krzysztof Kozlowski
2022-08-09 23:22 ` Rob Herring
2022-08-08 19:12 ` [RFC PATCH 2/6] dt-bindings: crypto: add binding for eip29t2 public key accelerator (PKA) Daniel Parks
2022-08-09 5:47 ` Krzysztof Kozlowski
2022-08-09 23:22 ` Rob Herring
2022-08-08 19:12 ` [RFC PATCH 3/6] arm64: dts: ti: k3-am64-main: add SA2UL public key accelerator subdevice Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 4/6] arm64: dts: ti: k3-j721e-main: " Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 5/6] crypto: sa2ul: turn on PKA engine Daniel Parks
2022-08-08 19:12 ` [RFC PATCH 6/6] crypto: sa2ul_pka: Add SA2UL PKA driver Daniel Parks
2022-08-08 21:52 ` Randy Dunlap
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=cover.1659985696.git.danielrparks@ti.com \
--to=danielrparks@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.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).