From: Tero Kristo <t-kristo@ti.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>
Cc: <j-keerthy@ti.com>
Subject: [PATCHv5 0/7] crypto: sa2ul driver support
Date: Wed, 1 Jul 2020 11:05:46 +0300 [thread overview]
Message-ID: <20200701080553.22604-1-t-kristo@ti.com> (raw)
Hi,
This latest incarnation of the series has patch #3 re-written for the
hash init/update/final sequencing only. As the HW accelerator can't
properly handle split up hashes, nor can its state be exported out, we
use software fallback now for all cases of hashing, except for digest.
Applies on top of 5.8-rc1, testing done:
- Crypto manager self tests (pass)
- Crypto manager extra self tests (pass)
- Openssl testing via cryptodev (pass)
- Ipsec testing over UDP tunnel (pass)
- tcrypt.ko testing for hashing/cipher (pass)
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next reply other threads:[~2020-07-01 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 8:05 Tero Kristo [this message]
2020-07-01 8:05 ` [PATCHv5 1/7] dt-bindings: crypto: Add TI SA2UL crypto accelerator documentation Tero Kristo
2020-07-01 8:05 ` [PATCHv5 2/7] crypto: sa2ul: Add crypto driver Tero Kristo
2020-07-09 8:03 ` Herbert Xu
2020-07-09 8:06 ` Herbert Xu
2020-07-13 8:40 ` Tero Kristo
2020-07-01 8:05 ` [PATCHv5 3/7] crypto: sa2ul: add sha1/sha256/sha512 support Tero Kristo
2020-07-01 8:05 ` [PATCHv5 4/7] crypto: sa2ul: Add AEAD algorithm support Tero Kristo
2020-07-01 8:05 ` [PATCHv5 5/7] crypto: sa2ul: add device links to child devices Tero Kristo
2020-07-01 8:05 ` [PATCHv5 6/7] arm64: dts: ti: k3-am6: Add crypto accelarator node Tero Kristo
2020-07-01 8:05 ` [PATCHv5 7/7] arm64: dts: ti: k3-j721e-main: Add crypto accelerator node Tero Kristo
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=20200701080553.22604-1-t-kristo@ti.com \
--to=t-kristo@ti.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=j-keerthy@ti.com \
--cc=linux-crypto@vger.kernel.org \
/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).