From: Stephan Mueller <smueller@chronox.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Marek Vašut" <marex@denx.de>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org
Subject: Re: mxs-dcp: Failed to register sha1 hash
Date: Thu, 26 Nov 2015 16:25:30 +0100 [thread overview]
Message-ID: <160969925.mts3FEnayM@myon.chronox.de> (raw)
In-Reply-To: <CAOMZO5AyAAfZM07KYHCfRaeia8Ut1F6s=jsFg6C3YYzHx8C5UA@mail.gmail.com>
Am Donnerstag, 26. November 2015, 13:14:12 schrieb Fabio Estevam:
Hi Fabio,
> Hi,
>
> On kernel 4.1.13 and also on 4.4.0-rc2-next-20151126 I see the
> following error on mx28:
>
> [ 2.245453] mxs-dcp 80028000.dcp: Failed to register sha1 hash!
> [ 2.253928] mxs-dcp: probe of 80028000.dcp failed with error -22
>
> Does anyone have any idea how to fix this?
Briefly looking into drivers/crypto/mxs-dcp.c, it is an ahash and does not
contain halg.statesize in the algo definitions. Thus it looks very much like
the same issue that I see with ghash.
--
Ciao
Stephan
next prev parent reply other threads:[~2015-11-26 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 15:14 mxs-dcp: Failed to register sha1 hash Fabio Estevam
2015-11-26 15:25 ` Stephan Mueller [this message]
2015-11-26 15:38 ` Fabio Estevam
2015-11-26 15:39 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=160969925.mts3FEnayM@myon.chronox.de \
--to=smueller@chronox.de \
--cc=festevam@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=marex@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox