From: Baolin Wang <baolin.wang@linaro.org>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: broonie@kernel.org, linus.walleij@linaro.org, arnd@arndb.de,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
baolin.wang@linaro.org
Subject: [PATCH 0/3] Introduce the cypto engine framework
Date: Tue, 26 Jan 2016 20:25:37 +0800 [thread overview]
Message-ID: <cover.1453810716.git.baolin.wang@linaro.org> (raw)
Now block cipher engines need to implement and maintain their own queue/thread
for processing requests, moreover currently helpers provided for only the queue
itself (in crypto_enqueue_request() and crypto_dequeue_request()) but they
don't help with the mechanics of driving the hardware (things like running the
request immediately, DMA map it or providing a thread to process the queue in)
even though a lot of that code really shouldn't vary that much from device to
device.
This patch introduces the crypto engine framework to help the crypto hardware
drivers to queue requests.
Baolin Wang (3):
crypto: Introduce crypto_queue_len() helper function
crypto: Introduce the block request crypto engine framework
crypto: omap-aes: Support crypto engine framework
crypto/Kconfig | 3 +
crypto/Makefile | 1 +
crypto/crypto_engine.c | 355 +++++++++++++++++++++++++++++++++++++++++++++
drivers/crypto/Kconfig | 1 +
drivers/crypto/omap-aes.c | 97 ++++++-------
include/crypto/algapi.h | 74 ++++++++++
6 files changed, 478 insertions(+), 53 deletions(-)
create mode 100644 crypto/crypto_engine.c
--
1.7.9.5
next reply other threads:[~2016-01-26 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 12:25 Baolin Wang [this message]
2016-01-26 12:25 ` [PATCH 1/3] crypto: Introduce crypto_queue_len() helper function Baolin Wang
2016-01-26 12:25 ` [PATCH 2/3] crypto: Introduce the block request crypto engine framework Baolin Wang
2016-01-26 12:25 ` [PATCH 3/3] crypto: omap-aes: Support " Baolin Wang
2016-02-01 14:33 ` [PATCH 0/3] Introduce the cypto " Herbert Xu
2016-02-02 1:37 ` 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=cover.1453810716.git.baolin.wang@linaro.org \
--to=baolin.wang@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linus.walleij@linaro.org \
--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).