On Mon, 25 May 2015 16:05:47 +0800
Herbert Xu <herb...@gondor.apana.org.au> wrote:
> On Fri, May 22, 2015 at 03:33:48PM +0200, Boris Brezillon wrote:
> >
> > +struct ahash_alg mv_ahmac_sha1_alg = {
> > + .init = mv_cesa_ahmac_sha1_init,
> > + .update = mv_cesa_ahash_update,
> > + .final = mv_cesa_ahash_final,
> > + .finup = mv_cesa_ahash_finup,
> > + .digest = mv_cesa_ahmac_sha1_digest,
> > + .setkey = mv_cesa_ahmac_sha1_setkey,
> > + .halg = {
> > + .digestsize = SHA1_DIGEST_SIZE,
> > + .statesize = sizeof(struct sha1_state),
> > + .base = {
> > + .cra_name = "hmac(sha1)",
> > + .cra_driver_name = "mv-hmac-sha1",
> > + .cra_priority = 300,
> > + .cra_flags = CRYPTO_ALG_ASYNC |
> > + CRYPTO_ALG_KERN_DRIVER_ONLY,
> > + .cra_blocksize = SHA1_BLOCK_SIZE,
> > + .cra_ctxsize = sizeof(struct mv_cesa_hmac_ctx),
> > + .cra_init = mv_cesa_ahmac_cra_init,
> > + .cra_module = THIS_MODULE,
> > + }
> > + }
> > +};
>
> So your hmac implementation is purely done in software. Since
> you've already written the code, could you please generalise this
> and make it a template?
Hm, I'm not I understand what you mean: the CESA engine is supporting
hardware HMAC.
What makes you think I'm doing the HMAC operation in software (I guess
I haven't properly filled the ahash_alg structure :-)) ?
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
