From: Antoine Tenart <antoine.tenart@bootlin.com>
To: Pascal van Leeuwen <pascalvanl@gmail.com>
Cc: linux-crypto@vger.kernel.org, antoine.tenart@bootlin.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
Pascal van Leeuwen <pvanleeuwen@verimatrix.com>
Subject: Re: [PATCHv3 1/4] crypto: inside-secure - make driver selectable for non-Marvell hardware
Date: Mon, 5 Aug 2019 10:04:12 +0200 [thread overview]
Message-ID: <20190805080412.GF14470@kwain> (raw)
In-Reply-To: <1564586959-9963-2-git-send-email-pvanleeuwen@verimatrix.com>
Hi Pascal,
On Wed, Jul 31, 2019 at 05:29:16PM +0200, Pascal van Leeuwen wrote:
> While being a generic EIP97/EIP197 driver, the driver was only selectable
> for Marvell Armada hardware. This fix makes the driver selectable for any
> Device Tree supporting kernel configuration, allowing it to be used for
> other compatible hardware by just adding the correct device tree entry.
>
> It also allows the driver to be selected for PCI(E) supporting kernel con-
> figurations, to be able to use it with PCIE based FPGA development boards
> for pre-silicon driver development by both Inside Secure and its IP custo-
> mers.
>
> Signed-off-by: Pascal van Leeuwen <pvanleeuwen@verimatrix.com>
Acked-by: Antoine Tenart <antoine.tenart@bootlin.com>
Thanks!
Antoine
> ---
> drivers/crypto/Kconfig | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
> index 67af688..0d9f67d 100644
> --- a/drivers/crypto/Kconfig
> +++ b/drivers/crypto/Kconfig
> @@ -716,8 +716,7 @@ source "drivers/crypto/stm32/Kconfig"
>
> config CRYPTO_DEV_SAFEXCEL
> tristate "Inside Secure's SafeXcel cryptographic engine driver"
> - depends on OF
> - depends on (ARM64 && ARCH_MVEBU) || (COMPILE_TEST && 64BIT)
> + depends on OF || PCI || COMPILE_TEST
> select CRYPTO_AES
> select CRYPTO_AUTHENC
> select CRYPTO_BLKCIPHER
> @@ -729,10 +728,11 @@ config CRYPTO_DEV_SAFEXCEL
> select CRYPTO_SHA256
> select CRYPTO_SHA512
> help
> - This driver interfaces with the SafeXcel EIP-197 cryptographic engine
> - designed by Inside Secure. Select this if you want to use CBC/ECB
> - chain mode, AES cipher mode and SHA1/SHA224/SHA256/SHA512 hash
> - algorithms.
> + This driver interfaces with the SafeXcel EIP-97 and EIP-197 cryptographic
> + engines designed by Inside Secure. It currently accelerates DES, 3DES and
> + AES block ciphers in ECB and CBC mode, as well as SHA1, SHA224, SHA256,
> + SHA384 and SHA512 hash algorithms for both basic hash and HMAC.
> + Additionally, it accelerates combined AES-CBC/HMAC-SHA AEAD operations.
>
> config CRYPTO_DEV_ARTPEC6
> tristate "Support for Axis ARTPEC-6/7 hardware crypto acceleration."
> --
> 1.8.3.1
--
Antoine Ténart, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-05 8:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 15:29 [PATCHv3 0/4] crypto: inside-secure - broaden driver scope Pascal van Leeuwen
2019-07-31 15:29 ` [PATCHv3 1/4] crypto: inside-secure - make driver selectable for non-Marvell hardware Pascal van Leeuwen
2019-08-05 8:04 ` Antoine Tenart [this message]
2019-07-31 15:29 ` [PATCHv3 2/4] crypto: inside-secure - Remove redundant algo to engine mapping code Pascal van Leeuwen
2019-08-05 7:51 ` Antoine Tenart
2019-07-31 15:29 ` [PATCHv3 3/4] crypto: inside-secure - add support for PCI based FPGA development board Pascal van Leeuwen
2019-08-05 8:36 ` Antoine Tenart
2019-08-05 8:47 ` Pascal Van Leeuwen
2019-08-05 9:09 ` Antoine Tenart
2019-08-05 9:49 ` Pascal Van Leeuwen
2019-07-31 15:29 ` [PATCHv3 4/4] crypto: inside-secure - add support for using the EIP197 without vendor firmware Pascal van Leeuwen
2019-08-05 9:07 ` Antoine Tenart
2019-08-05 9:48 ` Pascal Van Leeuwen
2019-08-05 9:54 ` Antoine Tenart
2019-08-05 10:12 ` Pascal Van Leeuwen
2019-08-05 12:43 ` Antoine Tenart
2019-08-05 13:02 ` Pascal Van Leeuwen
2019-08-05 13:12 ` Antoine Tenart
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=20190805080412.GF14470@kwain \
--to=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=pascalvanl@gmail.com \
--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 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).