The DMA controller currently takes configuration information from
information passed though dma_channel_request(), but it shouldn't.
Using the API, the DMA channel should only be configured during
a dma_slave_config() call.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-crypto@
Clearly this driver hasn't been tested, or even enabled in a while.
drivers/crypto/ux500/cryp/cryp_core.c:1771:3:
error: request for member ‘pm’ in something not a structure or union
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-crypto@vger.kernel.org
Signed-off-by: L
If we fail to prepare the ux500-cryp clock before enabling it the
platform will fail to boot. Here we insure this happens.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-crypto@vger.kernel.org
Signed-off-by: Lee Jones
---
drivers/crypto/ux500/cryp/cryp_core.c |6 +++---
1
If we fail to prepare the ux500-hash clock before enabling it the
platform will fail to boot. Here we insure this happens.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-crypto@vger.kernel.org
Signed-off-by: Lee Jones
---
drivers/crypto/ux500/hash/hash_core.c |8
The Cryp driver is currently silent and the Hash driver prints the
name of its probe function unnecessarily. Let's just put a nice
descriptive one-liner there instead.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-crypto@vger.kernel.org
Signed-off-by: Lee Jones
---
drivers/c
The DMA controller currently takes configuration information from
information passed though dma_channel_request(), but it shouldn't.
Using the API, the DMA channel should only be configured during
a dma_slave_config() call.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-crypto@
On Thu, Mar 14, 2013 at 10:48 AM, Chanho Min wrote:
> +#ifdef __BIG_ENDIAN
> +#define LZ4_NBCOMMONBYTES(val) (__builtin_clzll(val) >> 3)
> +#else
> +#define LZ4_NBCOMMONBYTES(val) (__builtin_ctzll(val) >> 3)
> +#endif
>
> #else /* 32-bit */
> #define STEPSIZE 4
> @@ -83,6 +130,14 @@ typedef str