Re: [PATCH] crypto: ccp - Fix XTS-AES support on a version 5 CCP

On 08/18/2017 11:19 AM, Gary R Hook wrote: On 07/17/2017 04:48 PM, Lendacky, Thomas wrote: On 7/17/2017 3:08 PM, Gary R Hook wrote: Version 5 CCPs have differing requirements for XTS-AES: key components are stored in a 512-bit vector. The context must be little-endian justified. AES-256 is

Re: [PATCH 2/6] crypto: jz4780-rng: Make ingenic CGU driver use syscon

Hi PrasannaKumar, On Thursday, 17 August 2017 11:25:16 PDT PrasannaKumar Muralidharan wrote: > Ingenic PRNG registers are a part of the same hardware block as clock > and power stuff. It is handled by CGU driver. Ingenic M200 SoC has power > related registers that are after the PRNG registers. So

Re: [PATCH] crypto: ccp - Fix XTS-AES-128 support on v5 CCPs

On Tue, Jul 25, 2017 at 02:12:11PM -0500, Gary R Hook wrote: > Version 5 CCPs have some new requirements for XTS-AES: the type field > must be specified, and the key requires 512 bits, with each part > occupying 256 bits and padded with zeroes. > > cc: # 4.9.x+ > >

Re: [PATCH] crypto: ccp - Fix XTS-AES-128 support on v5 CCPs

On Fri, Aug 18, 2017 at 11:41:04AM -0500, Gary R Hook wrote: > >On Tue, Jul 25, 2017 at 02:12:11PM -0500, Gary R Hook wrote: > >> Version 5 CCPs have some new requirements for XTS-AES: the type field > >> must be specified, and the key requires 512 bits, with each part > >> occupying 256 bits and

Re: [PATCH 2/3] crypto: engine - find request type with cra_type

On Mon, Aug 14, 2017 at 03:17:24PM +0200, Corentin Labbe wrote: > The current method for finding request type is based on crypto_tfm_alg_type. > > But in case of skcipher, it is the same than ablkcipher. > Using cra_type for this work permits to make the distinction between the two. > >

[PATCH v3 2/3] dt-bindings: Document STM32 CRYP bindings

Document device tree bindings for the STM32 CRYP. Signed-off-by: Fabien Dessenne Acked-by: Rob Herring --- .../devicetree/bindings/crypto/st,stm32-cryp.txt | 19 +++ 1 file changed, 19 insertions(+) create mode 100644

[PATCH v3 3/3] crypto: stm32 - Support for STM32 CRYP crypto module

This module registers block and AEAD cipher algorithms that make use of the STMicroelectronics STM32 crypto "CRYP1" hardware. The following algorithms are supported: - aes: ecb, cbc, ctr, gcm, ccm - des: ecb, cbc - tdes: ecb, cbc Signed-off-by: Fabien Dessenne ---

[PATCH v3 0/3] STM32 CRYP crypto driver

This set of patches adds a new crypto driver for STMicroelectronics stm32 HW. This drivers uses the crypto API and provides with HW-enabled AEAD and block cipher algorithms. It makes use of the crypto engine which is upgraded in order to support AEAD requests. This driver was successfully tested

[PATCH v3 1/3] crypto: engine - permit to enqueue aead_request

The current crypto engine allows ablkcipher_request and ahash_request to be enqueued. Extend this to aead_request. Signed-off-by: Fabien Dessenne --- crypto/crypto_engine.c | 101 include/crypto/engine.h | 16 2

Re: [PATCH 2/3] crypto: engine - find request type with cra_type

On Fri, Aug 18, 2017 at 04:28:37PM +0800, Herbert Xu wrote: > On Mon, Aug 14, 2017 at 03:17:24PM +0200, Corentin Labbe wrote: > > The current method for finding request type is based on crypto_tfm_alg_type. > > > > But in case of skcipher, it is the same than ablkcipher. > > Using cra_type for

Re: [PATCH 3/6] crypto: jz4780-rng: Add Ingenic JZ4780 hardware PRNG driver

Hi Stephan, On 18 August 2017 at 00:22, Stephan Mueller wrote: > Am Donnerstag, 17. August 2017, 20:25:17 CEST schrieb PrasannaKumar > Muralidharan: > > Hi PrasannaKumar, > >> + >> +static int jz4780_rng_generate(struct crypto_rng *tfm, >> +const

[PATCH 1/1] crypto: stm32/hash - Remove uninitialized symbol

Remove err symbol as this is not used in the thread context and the variable is not initialized. Signed-off-by: Lionel Debieve --- drivers/crypto/stm32/stm32-hash.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/crypto/stm32/stm32-hash.c

[PATCH v4 1/1] crypto: engine - Permit to enqueue skcipher request

The crypto engine could actually only enqueue hash and ablkcipher request. This patch permit it to enqueue skcipher requests by adding all necessary functions. Signed-off-by: Corentin Labbe --- crypto/crypto_engine.c | 120

[PATCH v4 0/1] crypto: engine - Permit to enqueue skcipher request

Hello The crypto engine could actually only enqueue hash and ablkcipher request. This patch serie permit it to enqueue skcipher requests by adding all necessary functions. Changes since v3 - Use cra_type only for distinguish ablkcipher from skcipher Changes since v2 - added two patch for

Re: [PATCH v3 3/4] btrfs: Add zstd support

On Wed, Jul 26, 2017 at 12:19:29AM +0100, Giovanni Cabiddu wrote: > Hi Nick, > > On Thu, Jul 20, 2017 at 10:27:42PM +0100, Nick Terrell wrote: > > Add zstd compression and decompression support to BtrFS. zstd at its > > fastest level compresses almost as well as zlib, while offering much > >

Re: [PATCH] crypto: ccp - Fix XTS-AES support on a version 5 CCP

On 07/17/2017 04:48 PM, Lendacky, Thomas wrote: On 7/17/2017 3:08 PM, Gary R Hook wrote: Version 5 CCPs have differing requirements for XTS-AES: key components are stored in a 512-bit vector. The context must be little-endian justified. AES-256 is supported now, so propagate the cipher size to