From: Pascal van Leeuwen <pascalvanl@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: antoine.tenart@bootlin.com, herbert@gondor.apana.org.au,
davem@davemloft.net,
Pascal van Leeuwen <pvanleeuwen@verimatrix.com>
Subject: [PATCH 0/6] crypto: inside-secure - Add supp. for non-Marvell HW
Date: Fri, 6 Sep 2019 16:31:47 +0200 [thread overview]
Message-ID: <1567780313-1579-1-git-send-email-pvanleeuwen@verimatrix.com> (raw)
This patchset adds support for non-Marvell hardware, probing the HW
configuration directly from the HW itself instead of making assumptions
based on specific Marvell instances and applying appropriate settings.
This should get most EIP97/EIP197 instances out there up and running,
albeit not always with optimal settings yet.
Still to be done:
- support for EIP197 HW with 256 bit internal bus width
- optimize settings for newer versions of the HW
This was tested with both the Macchiatobin board, "similar to Marvell"
HW on the Xilinx VCU118 devboard and a eip197c-iesb HW3.1 on the Xilinx
VCU118 devboard.
Pascal van Leeuwen (6):
crypto: inside-secure - Add EIP97/EIP197 and endianness detection
crypto: inside-secure: Corrected configuration of EIP96_TOKEN_CTRL
crypto: inside-secure - Enable extended algorithms on newer HW
crypto: inside-secure - Base CD fetchcount on actual CD FIFO size
crypto: inside-secure - Base RD fetchcount on actual RD FIFO size
crypto: inside-secure - Probe transform record cache RAM sizes
drivers/crypto/inside-secure/safexcel.c | 459 ++++++++++++++++++++++++--------
drivers/crypto/inside-secure/safexcel.h | 78 ++++--
2 files changed, 418 insertions(+), 119 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-09-06 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 14:31 Pascal van Leeuwen [this message]
2019-09-06 14:31 ` [PATCH 1/6] crypto: inside-secure - Add EIP97/EIP197 and endianness detection Pascal van Leeuwen
2019-09-06 14:31 ` [PATCH 2/6] crypto: inside-secure: Corrected configuration of EIP96_TOKEN_CTRL Pascal van Leeuwen
2019-09-06 14:31 ` [PATCH 3/6] crypto: inside-secure - Enable extended algorithms on newer HW Pascal van Leeuwen
2019-09-06 14:31 ` [PATCH 4/6] crypto: inside-secure - Base CD fetchcount on actual CD FIFO size Pascal van Leeuwen
2019-09-06 14:31 ` [PATCH 5/6] crypto: inside-secure - Base RD fetchcount on actual RD " Pascal van Leeuwen
2019-09-06 14:31 ` [PATCH 6/6] crypto: inside-secure - Probe transform record cache RAM sizes Pascal van Leeuwen
2019-09-13 11:29 ` [PATCH 0/6] crypto: inside-secure - Add supp. for non-Marvell HW Herbert Xu
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=1567780313-1579-1-git-send-email-pvanleeuwen@verimatrix.com \
--to=pascalvanl@gmail.com \
--cc=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=pvanleeuwen@verimatrix.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.