From: Leonard Crestez <leonard.crestez@nxp.com>
To: Marek Vasut <marek.vasut@gmail.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: Horia Geanta <horia.geanta@nxp.com>,
Franck Lenormand <franck.lenormand@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
Aymen Sghaier <aymen.sghaier@nxp.com>,
"David S . Miller " <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] crypto: mxs-dcp - Fix tcrypt on imx6
Date: Tue, 2 Oct 2018 19:01:46 +0000 [thread overview]
Message-ID: <cover.1538505573.git.leonard.crestez@nxp.com> (raw)
The mxs-dcp driver currently fails to probe on imx6. Fix the whole thing
by porting a cleaned/squashed version of fixes carried in the NXP vendor
tree.
Tested with "modprobe tcrypt" and CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=n
on imx6sl imx6sll imx6ull: no failures.
I'm not very familiar with crypto and did not write write these fixes so
a skeptical review would be appreciated.
Previously:
https://lore.kernel.org/patchwork/patch/989652/
Dan Douglass (1):
crypto: mxs-dcp - Implement sha import/export
Radu Solea (2):
crypto: mxs-dcp - Fix SHA null hashes and output length
crypto: mxs-dcp - Fix AES issues
drivers/crypto/mxs-dcp.c | 121 ++++++++++++++++++++++++++++++++-------
1 file changed, 101 insertions(+), 20 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-02 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 19:01 Leonard Crestez [this message]
2018-10-02 19:01 ` [PATCH 1/3] crypto: mxs-dcp - Implement sha import/export Leonard Crestez
2018-10-03 2:30 ` Fabio Estevam
2018-10-02 19:01 ` [PATCH 2/3] crypto: mxs-dcp - Fix SHA null hashes and output length Leonard Crestez
2018-10-02 19:01 ` [PATCH 3/3] crypto: mxs-dcp - Fix AES issues Leonard Crestez
2018-10-08 5:52 ` [PATCH 0/3] crypto: mxs-dcp - Fix tcrypt on imx6 Herbert Xu
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=cover.1538505573.git.leonard.crestez@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=fabio.estevam@nxp.com \
--cc=franck.lenormand@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=shawnguo@kernel.org \
/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
all inboxes | Powered by JetHome®