From: Pascal Van Leeuwen <pvanleeuwen@verimatrix.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Pascal van Leeuwen <pascalvanl@gmail.com>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"antoine.tenart@bootlin.com" <antoine.tenart@bootlin.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: RE: [PATCHv4 0/4] crypto: inside-secure - broaden driver scope
Date: Mon, 19 Aug 2019 14:52:51 +0000 [thread overview]
Message-ID: <MN2PR20MB29737672222C6C258658F83FCAA80@MN2PR20MB2973.namprd20.prod.outlook.com> (raw)
In-Reply-To: <20190815115125.GA28602@gondor.apana.org.au>
> -----Original Message-----
> From: linux-crypto-owner@vger.kernel.org <linux-crypto-owner@vger.kernel.org> On Behalf Of
> Herbert Xu
> Sent: Thursday, August 15, 2019 1:51 PM
> To: Pascal van Leeuwen <pascalvanl@gmail.com>
> Cc: linux-crypto@vger.kernel.org; antoine.tenart@bootlin.com; davem@davemloft.net; Pascal
> Van Leeuwen <pvanleeuwen@verimatrix.com>
> Subject: Re: [PATCHv4 0/4] crypto: inside-secure - broaden driver scope
>
> On Tue, Aug 06, 2019 at 09:46:22AM +0200, Pascal van Leeuwen wrote:
> > This is a first baby step towards making the inside-secure crypto driver
> > more broadly useful. The current driver only works for Marvell Armada HW
> > and requires proprietary firmware, only available under NDA from Marvell,
> > to be installed. This patch set allows the driver to be used with other
> > hardware and removes the dependence on that proprietary firmware.
> >
> > changes since v1:
> > - changed dev_info's into dev_dbg to reduce normal verbosity
> > - terminate all message strings with \n
> > - use priv->version field strictly to enumerate device context
> > - fixed some code & comment style issues
> > - removed EIP97/197 references from messages
> > - use #if(IS_ENABLED(CONFIG_PCI)) to remove all PCI related code
> > - use #if(IS_ENABLED(CONFIG_OF)) to remove all device tree related code
> > - do not inline the minifw but read it from /lib/firmware instead
> >
> > changes since v2:
> > - split off removal of alg to engine mapping code into separate patch
> > - replaced some constants with nice defines
> > - added missing \n to some error messages
> > - removed some redundant parenthesis
> > - aligned some #if's properly
> > - added some comments to clarify code
> > - report error on FW load for unknown HW instead of loading EIP197B FW
> > - use readl_relaxed() instead of readl() + cpu_relax() in polling loop
> > - merged patch "fix null ptr dereference on rmmod for macchiatobin" here
> > - merged patch "removed unused struct entry"
> >
> > changes since v3:
> > - reverted comment style from generic back to network
> > - changed prefix "crypto_is_" to "safexcel_" for consistency
> >
> > Pascal van Leeuwen (4):
> > crypto: inside-secure - make driver selectable for non-Marvell
> > hardware
> > crypto: inside-secure - Remove redundant algo to engine mapping code
> > crypto: inside-secure - add support for PCI based FPGA development
> > board
> > crypto: inside-secure - add support for using the EIP197 without
> > vendor firmware
> >
> > drivers/crypto/Kconfig | 12 +-
> > drivers/crypto/inside-secure/safexcel.c | 744 +++++++++++++++++--------
> > drivers/crypto/inside-secure/safexcel.h | 43 +-
> > drivers/crypto/inside-secure/safexcel_cipher.c | 11 -
> > drivers/crypto/inside-secure/safexcel_hash.c | 12 -
> > drivers/crypto/inside-secure/safexcel_ring.c | 3 +-
> > 6 files changed, 573 insertions(+), 252 deletions(-)
>
> This patch series fails to apply on the current cryptodev tree.
>
> Please rebase.
>
Ugh ... yeah. Looks like some very minor changes have been made to the cryptodev
tree since I prepared those that are causing me a major headache now.
Will rebase and send a v3 shortly.
> Thanks,
> --
> Email: Herbert Xu <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Regards,
Pascal van Leeuwen
Silicon IP Architect, Multi-Protocol Engines @ Verimatrix
www.insidesecure.com
prev parent reply other threads:[~2019-08-19 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 7:46 [PATCHv4 0/4] crypto: inside-secure - broaden driver scope Pascal van Leeuwen
2019-08-06 7:46 ` [PATCHv4 1/4] crypto: inside-secure - make driver selectable for non-Marvell hardware Pascal van Leeuwen
2019-08-06 7:46 ` [PATCHv4 2/4] crypto: inside-secure - Remove redundant algo to engine mapping code Pascal van Leeuwen
2019-08-06 7:46 ` [PATCHv4 3/4] crypto: inside-secure - add support for PCI based FPGA development board Pascal van Leeuwen
2019-08-06 9:19 ` Antoine Tenart
2019-08-06 7:46 ` [PATCHv4 4/4] crypto: inside-secure - add support for using the EIP197 without vendor firmware Pascal van Leeuwen
2019-08-15 11:51 ` [PATCHv4 0/4] crypto: inside-secure - broaden driver scope Herbert Xu
2019-08-19 14:52 ` Pascal Van Leeuwen [this message]
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=MN2PR20MB29737672222C6C258658F83FCAA80@MN2PR20MB2973.namprd20.prod.outlook.com \
--to=pvanleeuwen@verimatrix.com \
--cc=antoine.tenart@bootlin.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=pascalvanl@gmail.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).