From: LABBE Corentin <clabbe.montjoie@gmail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net, baolin.wang@linaro.org
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
LABBE Corentin <clabbe.montjoie@gmail.com>
Subject: [PATCH v2 0/2] crypto: engine: permit to enqueue ashash_request
Date: Mon, 30 May 2016 15:32:00 +0200 [thread overview]
Message-ID: <1464615122-16685-1-git-send-email-clabbe.montjoie@gmail.com> (raw)
Hello
I wanted to use the crypto engine for my Allwinner crypto driver but something
prevented me to use it: it cannot enqueue hash requests.
The first patch convert crypto engine to permit enqueuing of ahash_requests.
The second patch convert the only driver using crypto engine.
The second patch was only compile tested but the crypto engine with
hash support was tested on two different offtree driver (sun4i-ss and sun8i-ce)
Regards
Changes since v1:
- rebased on cryptodev for handling omap-des
LABBE Corentin (2):
crypto: engine: permit to enqueue ashash_request
crypto: omap: convert to the new cryptoengine API
crypto/crypto_engine.c | 17 +++++++----------
drivers/crypto/omap-aes.c | 10 ++++++----
include/crypto/algapi.h | 14 +++++++-------
3 files changed, 20 insertions(+), 21 deletions(-)
--
2.7.3
next reply other threads:[~2016-05-30 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 13:32 LABBE Corentin [this message]
2016-05-30 13:32 ` [PATCH v2 1/2] crypto: engine: permit to enqueue ashash_request LABBE Corentin
2016-06-01 2:27 ` Baolin Wang
2016-06-02 8:32 ` Herbert Xu
2016-06-02 9:12 ` LABBE Corentin
2016-06-02 9:19 ` Herbert Xu
2016-06-02 9:38 ` LABBE Corentin
2016-06-02 9:42 ` Herbert Xu
2016-05-30 13:32 ` [PATCH v2 2/2] crypto: omap: convert to the new cryptoengine API LABBE Corentin
2016-06-01 2:28 ` Baolin Wang
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=1464615122-16685-1-git-send-email-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=baolin.wang@linaro.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).