From: Gianfranco Costamagna <locutusofborg@debian.org>
To: "To: Fabio Estevam" <festevam@gmail.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"marex@denx.de" <marex@denx.de>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH] crypto: mxs-dcp - Remove hash support
Date: Fri, 28 Oct 2016 15:46:13 +0000 (UTC) [thread overview]
Message-ID: <1477960343.1079728.1477669573195@mail.yahoo.com> (raw)
In-Reply-To: <CACJOhtLFGOmrLZfPjb7TXPTcqPAdCXn6H7HEHG-8iQN3Z6gJnA@mail.gmail.com>
Hi,
(sending with my debian.org mail address to avoid spam filters)
I tested the patch and indeed solves my problem (the driver loads correctly now with no warnings)
Tested-by: Gianfranco Costamagna <gianfranco.costamagna@abinsula.com>'
Just a side note about the patch
if (sdcp->caps & MXS_DCP_CAPABILITY1_SHA1) {
ret = crypto_register_ahash(&dcp_ sha1_alg);
if (ret) {
dev_err(dev, "Failed to register %s hash!\n",
dcp_sha1_alg.halg.base.cra_ name);
goto err_unregister_aes;
}
-err_unregister_aes:
- if (sdcp->caps & MXS_DCP_CAPABILITY1_AES128)
- crypto_unregister_algs(dcp_ae s_algs, ARRAY_SIZE(dcp_aes_algs));
-
err_destroy_aes_thread:
kthread_stop(sdcp->thread[DCP_ CHAN_CRYPTO]);
seems that in case of SHA1 register failure, the unregister was done on aes algorithm.
Probably a bad copy-paste, but removing such code will obviously fix it.
thanks,
Gianfranco
next prev parent reply other threads:[~2016-10-28 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 16:40 [PATCH] crypto: mxs-dcp - Remove hash support Fabio Estevam
[not found] ` <CACJOhtJqx6+QN9gefSWtw_vgR3vps7tobXLQdbGM7FeUum_C3A@mail.gmail.com>
[not found] ` <CACJOhtLFGOmrLZfPjb7TXPTcqPAdCXn6H7HEHG-8iQN3Z6gJnA@mail.gmail.com>
2016-10-28 15:46 ` Gianfranco Costamagna [this message]
2016-10-28 20:05 ` 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=1477960343.1079728.1477669573195@mail.yahoo.com \
--to=locutusofborg@debian.org \
--cc=fabio.estevam@nxp.com \
--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