From: Lokesh Vutla <lokeshvutla@ti.com>
To: <linux-crypto@vger.kernel.org>, <linux-omap@vger.kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <davem@davemloft.net>,
<herbert@gondor.hengli.com.au>, <rnayak@ti.com>, <nsekhar@ti.com>,
<joelf@ti.com>, <lokeshvutla@ti.com>
Subject: [PATCH 0/4] crypto: omap-sham: Add support for SHA384/SHA512 for OMAP5/AM43xx Soc's
Date: Fri, 26 Jul 2013 12:29:13 +0530 [thread overview]
Message-ID: <1374821957-30141-1-git-send-email-lokeshvutla@ti.com> (raw)
This patch series adds support for SHA348 and SHA512 in addition to MD5,
SHA1, SHA224 SHA256 that the omap sha module supports. Also adding the pdata
for OMAP5 and AM43xx Soc's.
And using devm_* calls to make cleanup paths simpler.
Lokesh Vutla (4):
crypto: omap-sham: Add SHA384 and SHA512 Support
crypto: omap-sham: Add OMAP5/AM43XX SHAM Support
crypto: omap-sham: Convert to devm_request_irq()
crypto: omap-sham: Convert to devm_kzalloc()
drivers/crypto/Kconfig | 11 +-
drivers/crypto/omap-sham.c | 314 +++++++++++++++++++++++++++++++++++---------
2 files changed, 262 insertions(+), 63 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-07-26 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 6:59 Lokesh Vutla [this message]
2013-07-26 6:59 ` [PATCH 1/4] crypto: omap-sham: Add SHA384 and SHA512 Support Lokesh Vutla
2013-07-26 6:59 ` [PATCH 2/4] crypto: omap-sham: Add OMAP5/AM43XX SHAM Support Lokesh Vutla
2013-08-09 15:31 ` Mark Rutland
2013-07-26 6:59 ` [PATCH 3/4] crypto: omap-sham: Convert to devm_request_irq() Lokesh Vutla
2013-07-26 6:59 ` [PATCH 4/4] crypto: omap-sham: Convert to devm_kzalloc() Lokesh Vutla
2013-08-01 1:47 ` [PATCH 0/4] crypto: omap-sham: Add support for SHA384/SHA512 for OMAP5/AM43xx Soc's 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=1374821957-30141-1-git-send-email-lokeshvutla@ti.com \
--to=lokeshvutla@ti.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=joelf@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rnayak@ti.com \
/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