On Sat, Jul 26, 2014 at 04:01:26PM +0200, Corentin LABBE wrote:
>
> Even if it is undocumented, the hardware seems to support it.
> Since crypto_ahash_ctx is for a tfm, does ahash_request_ctx is the good place
> to store data ?
> (after a call to crypto_ahash_set_reqsize in cra_init)
Yes any
On Sat, Jul 26, 2014 at 04:01:26PM +0200, Corentin LABBE wrote:
Even if it is undocumented, the hardware seems to support it.
Since crypto_ahash_ctx is for a tfm, does ahash_request_ctx is the good place
to store data ?
(after a call to crypto_ahash_set_reqsize in cra_init)
Yes any hash
Le 24/07/2014 15:38, Herbert Xu a écrit :
> On Thu, Jul 24, 2014 at 01:04:55PM +0200, Corentin LABBE wrote:
>> Le 24/07/2014 08:00, Herbert Xu a écrit :
>>> On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
+/* sunxi_hash_init: initialize request context
+ * Activate
Le 24/07/2014 15:38, Herbert Xu a écrit :
On Thu, Jul 24, 2014 at 01:04:55PM +0200, Corentin LABBE wrote:
Le 24/07/2014 08:00, Herbert Xu a écrit :
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
+/* sunxi_hash_init: initialize request context
+ * Activate the SS, and
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
> Add support for the Security System included in Allwinner SoC A20.
> The Security System is a hardware cryptographic accelerator that support
> AES/MD5/SHA1/DES/3DES/PRNG algorithms.
>
> Signed-off-by: LABBE Corentin
> ---
>
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
Add support for the Security System included in Allwinner SoC A20.
The Security System is a hardware cryptographic accelerator that support
AES/MD5/SHA1/DES/3DES/PRNG algorithms.
Signed-off-by: LABBE Corentin
On Thu, Jul 24, 2014 at 01:04:55PM +0200, Corentin LABBE wrote:
> Le 24/07/2014 08:00, Herbert Xu a écrit :
> > On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
> >>
> >> +/* sunxi_hash_init: initialize request context
> >> + * Activate the SS, and configure it for MD5 or SHA1
> >>
Le 24/07/2014 08:00, Herbert Xu a écrit :
> On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
>>
>> +/* sunxi_hash_init: initialize request context
>> + * Activate the SS, and configure it for MD5 or SHA1
>> + */
>> +int sunxi_hash_init(struct ahash_request *areq)
>> +{
>> +const
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
>
> +/* sunxi_hash_init: initialize request context
> + * Activate the SS, and configure it for MD5 or SHA1
> + */
> +int sunxi_hash_init(struct ahash_request *areq)
> +{
> + const char *hash_type;
> + struct crypto_ahash *tfm
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
+/* sunxi_hash_init: initialize request context
+ * Activate the SS, and configure it for MD5 or SHA1
+ */
+int sunxi_hash_init(struct ahash_request *areq)
+{
+ const char *hash_type;
+ struct crypto_ahash *tfm =
Le 24/07/2014 08:00, Herbert Xu a écrit :
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
+/* sunxi_hash_init: initialize request context
+ * Activate the SS, and configure it for MD5 or SHA1
+ */
+int sunxi_hash_init(struct ahash_request *areq)
+{
+const char
On Thu, Jul 24, 2014 at 01:04:55PM +0200, Corentin LABBE wrote:
Le 24/07/2014 08:00, Herbert Xu a écrit :
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
+/* sunxi_hash_init: initialize request context
+ * Activate the SS, and configure it for MD5 or SHA1
+ */
+int
On Wed, Jul 23, 2014 at 03:48:57PM +0200, Maxime Ripard wrote:
>
> The exact opposite has been asked for during v1's review...
Indeed but unfortunately it was bogus advice. The async interface
brings with it a lot of complexity which should be avoided unless
you actually need it.
Even if you
Hi,
On Wed, Jul 23, 2014 at 09:16:20PM +0800, Herbert Xu wrote:
> On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
> > Add support for the Security System included in Allwinner SoC A20.
> > The Security System is a hardware cryptographic accelerator that support
> >
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
> Add support for the Security System included in Allwinner SoC A20.
> The Security System is a hardware cryptographic accelerator that support
> AES/MD5/SHA1/DES/3DES/PRNG algorithms.
>
> Signed-off-by: LABBE Corentin
This is
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
Add support for the Security System included in Allwinner SoC A20.
The Security System is a hardware cryptographic accelerator that support
AES/MD5/SHA1/DES/3DES/PRNG algorithms.
Signed-off-by: LABBE Corentin
Hi,
On Wed, Jul 23, 2014 at 09:16:20PM +0800, Herbert Xu wrote:
On Sat, Jul 12, 2014 at 02:59:13PM +0200, LABBE Corentin wrote:
Add support for the Security System included in Allwinner SoC A20.
The Security System is a hardware cryptographic accelerator that support
On Wed, Jul 23, 2014 at 03:48:57PM +0200, Maxime Ripard wrote:
The exact opposite has been asked for during v1's review...
Indeed but unfortunately it was bogus advice. The async interface
brings with it a lot of complexity which should be avoided unless
you actually need it.
Even if you use
Add support for the Security System included in Allwinner SoC A20.
The Security System is a hardware cryptographic accelerator that support
AES/MD5/SHA1/DES/3DES/PRNG algorithms.
Signed-off-by: LABBE Corentin
---
drivers/crypto/Kconfig| 17 ++
drivers/crypto/Makefile
Add support for the Security System included in Allwinner SoC A20.
The Security System is a hardware cryptographic accelerator that support
AES/MD5/SHA1/DES/3DES/PRNG algorithms.
Signed-off-by: LABBE Corentin clabbe.montj...@gmail.com
---
drivers/crypto/Kconfig| 17 ++
20 matches
Mail list logo
