On Fri, May 11, 2012 at 11:58:03AM +0300, Kasatkin, Dmitry wrote:
> Hello,
>
> When allocating hmac like: crypto_alloc_ahash("hmac(sha1)", ..),
> it is actually fallsback to "shash" hmac and software shash hash
> implementation..
> Even when HW accelerator provides AHASH it will not be used with hmac.
>
> Basically HW driver needs to provide its own implementation for async
> hmac, like I did for omap-sham.
>
> .cra_name = "hmac(sha1)",
> .cra_driver_name = "omap-hmac-sha1",
>
> Is that correct, right?
We can add an async version of hmac if your hardware does not
have direct support for it.
Cheers,
--
Email: Herbert Xu <herb...@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
