Re: [PATCH 0/7] arm64: marvell: add cryptographic engine support for 7k/8k

[Herbert Xu]

On Tue, Apr 11, 2017 at 06:12:25PM +0200, Gregory CLEMENT wrote:
>
> > I have no problems with the crypto bits.
> 
> Does it means that you agree that I apply the arm-soc related patches
> (from 4 to 7) to my mvebu trees?

Yes sure.

Thanks,
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Re: [PATCH 0/7] arm64: marvell: add cryptographic engine support for 7k/8k

[Gregory CLEMENT]

Hi Herbert,
 
 On lun., avril 10 2017, Herbert Xu  wrote:

> On Wed, Mar 29, 2017 at 02:44:25PM +0200, Antoine Tenart wrote:
>> Hi all,
>> 
>> This series adds support for the Inside Secure SafeXcel EIP197
>> cryptographic engine which can be found on Marvell Armada 7k and 8k
>> boards. A new cryptographic engine driver is added, as well as the
>> relevant device tree definition for the Armada 7040 DB and 8040 DB
>> boards.
>> 
>> This driver needs two firmwares to work correctly. These firmware are
>> usually used for more advanced operations than the ones supported (as of
>> now), but we still need them to pass the data to the internal
>> cryptographic engine.
>> 
>> This series was tested in various ways on both the Armada 7040 DB and
>> the Armada 8040 DB: using the crypto framework self tests, using tcrypt
>> and while performing various transfers with iperf on top of IPsec.
>> 
>> This series is based on top of v4.11-rc1, and is available on a branch
>> (which also contains the PPv2 support for 7k/8k, to ease the process of
>> testing IPsec): https://github.com/atenart/linux  v4.11-rc1/7k8k-crypto
>> I can rebase if needed.
>> 
>> Thanks,
>> Antoine
>> 
>> 
>> Antoine Tenart (7):
>>   Documentation/bindings: Document the SafeXel cryptographic engine
>> driver
>>   crypto: inside-secure: add SafeXcel EIP197 crypto engine driver
>>   MAINTAINERS: add a maintainer for the Inside Secure crypto driver
>>   arm64: marvell: dts: add crypto engine description for 7k/8k
>>   arm64: marvell: dts: enable the crypto engine on the Armada 7040 DB
>>   arm64: marvell: dts: enable the crypto engine on the Armada 8040 DB
>>   arm64: defconfig: enable the Safexcel crypto engine as a module
>
> I have no problems with the crypto bits.

Does it means that you agree that I apply the arm-soc related patches
(from 4 to 7) to my mvebu trees?

Thanks,

Gregory

>
> Thanks,
> -- 
> Email: Herbert Xu 
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

Re: [PATCH 0/7] arm64: marvell: add cryptographic engine support for 7k/8k

[Herbert Xu]

On Wed, Mar 29, 2017 at 02:44:25PM +0200, Antoine Tenart wrote:
> Hi all,
> 
> This series adds support for the Inside Secure SafeXcel EIP197
> cryptographic engine which can be found on Marvell Armada 7k and 8k
> boards. A new cryptographic engine driver is added, as well as the
> relevant device tree definition for the Armada 7040 DB and 8040 DB
> boards.
> 
> This driver needs two firmwares to work correctly. These firmware are
> usually used for more advanced operations than the ones supported (as of
> now), but we still need them to pass the data to the internal
> cryptographic engine.
> 
> This series was tested in various ways on both the Armada 7040 DB and
> the Armada 8040 DB: using the crypto framework self tests, using tcrypt
> and while performing various transfers with iperf on top of IPsec.
> 
> This series is based on top of v4.11-rc1, and is available on a branch
> (which also contains the PPv2 support for 7k/8k, to ease the process of
> testing IPsec): https://github.com/atenart/linux  v4.11-rc1/7k8k-crypto
> I can rebase if needed.
> 
> Thanks,
> Antoine
> 
> 
> Antoine Tenart (7):
>   Documentation/bindings: Document the SafeXel cryptographic engine
> driver
>   crypto: inside-secure: add SafeXcel EIP197 crypto engine driver
>   MAINTAINERS: add a maintainer for the Inside Secure crypto driver
>   arm64: marvell: dts: add crypto engine description for 7k/8k
>   arm64: marvell: dts: enable the crypto engine on the Armada 7040 DB
>   arm64: marvell: dts: enable the crypto engine on the Armada 8040 DB
>   arm64: defconfig: enable the Safexcel crypto engine as a module

I have no problems with the crypto bits.

Thanks,
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

[PATCH 0/7] arm64: marvell: add cryptographic engine support for 7k/8k

[Antoine Tenart]

Hi all,

This series adds support for the Inside Secure SafeXcel EIP197
cryptographic engine which can be found on Marvell Armada 7k and 8k
boards. A new cryptographic engine driver is added, as well as the
relevant device tree definition for the Armada 7040 DB and 8040 DB
boards.

This driver needs two firmwares to work correctly. These firmware are
usually used for more advanced operations than the ones supported (as of
now), but we still need them to pass the data to the internal
cryptographic engine.

This series was tested in various ways on both the Armada 7040 DB and
the Armada 8040 DB: using the crypto framework self tests, using tcrypt
and while performing various transfers with iperf on top of IPsec.

This series is based on top of v4.11-rc1, and is available on a branch
(which also contains the PPv2 support for 7k/8k, to ease the process of
testing IPsec): https://github.com/atenart/linux  v4.11-rc1/7k8k-crypto
I can rebase if needed.

Thanks,
Antoine


Antoine Tenart (7):
  Documentation/bindings: Document the SafeXel cryptographic engine
driver
  crypto: inside-secure: add SafeXcel EIP197 crypto engine driver
  MAINTAINERS: add a maintainer for the Inside Secure crypto driver
  arm64: marvell: dts: add crypto engine description for 7k/8k
  arm64: marvell: dts: enable the crypto engine on the Armada 7040 DB
  arm64: marvell: dts: enable the crypto engine on the Armada 8040 DB
  arm64: defconfig: enable the Safexcel crypto engine as a module

 .../bindings/crypto/inside-secure-safexcel.txt |   27 +
 MAINTAINERS|6 +
 arch/arm64/boot/dts/marvell/armada-7040-db.dts |4 +
 arch/arm64/boot/dts/marvell/armada-8040-db.dts |4 +
 .../boot/dts/marvell/armada-cp110-master.dtsi  |   15 +
 .../arm64/boot/dts/marvell/armada-cp110-slave.dtsi |   15 +
 arch/arm64/configs/defconfig   |1 +
 drivers/crypto/Kconfig |   17 +
 drivers/crypto/Makefile|1 +
 drivers/crypto/inside-secure/Makefile  |2 +
 drivers/crypto/inside-secure/safexcel.c|  939 ++
 drivers/crypto/inside-secure/safexcel.h|  581 +++
 drivers/crypto/inside-secure/safexcel_cipher.c |  544 ++
 drivers/crypto/inside-secure/safexcel_hash.c   | 1045 
 drivers/crypto/inside-secure/safexcel_ring.c   |  173 
 15 files changed, 3374 insertions(+)
 create mode 100644 
Documentation/devicetree/bindings/crypto/inside-secure-safexcel.txt
 create mode 100644 drivers/crypto/inside-secure/Makefile
 create mode 100644 drivers/crypto/inside-secure/safexcel.c
 create mode 100644 drivers/crypto/inside-secure/safexcel.h
 create mode 100644 drivers/crypto/inside-secure/safexcel_cipher.c
 create mode 100644 drivers/crypto/inside-secure/safexcel_hash.c
 create mode 100644 drivers/crypto/inside-secure/safexcel_ring.c

-- 
2.11.0