From: Mark Rutland <mark.rutland@arm.com>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"joelf@ti.com" <joelf@ti.com>, "rnayak@ti.com" <rnayak@ti.com>,
"nsekhar@ti.com" <nsekhar@ti.com>,
"herbert@gondor.hengli.com.au" <herbert@gondor.hengli.com.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/4] crypto: omap-sham: Add OMAP5/AM43XX SHAM Support
Date: Fri, 9 Aug 2013 16:31:34 +0100 [thread overview]
Message-ID: <20130809153134.GT27325@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1374821957-30141-3-git-send-email-lokeshvutla@ti.com>
On Fri, Jul 26, 2013 at 07:59:15AM +0100, Lokesh Vutla wrote:
> Add support for the OMAP5 version of the SHAM module
> that is present on OMAP5 and AM43xx SoCs.
>
> This module is very simialar to OMAP4 version of SHAM module,
> and adds SHA384 SHA512 hardware-accelerated hash functions to it.
> To handle the higher digest size of SHA512, few SHA512_DIGEST_i
> (i=1-16, and first 8 registers are duplicated from SHA_DIGEST_i
> registers) registers are added at the end of register set.
> So adding the above register offsets and module info in pdata.
>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> drivers/crypto/omap-sham.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> + {
> + .compatible = "ti,omap5-sham",
> + .data = &omap_sham_pdata_omap5,
> + },
No binding update?
Mark.
next prev parent reply other threads:[~2013-08-09 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 6:59 [PATCH 0/4] crypto: omap-sham: Add support for SHA384/SHA512 for OMAP5/AM43xx Soc's Lokesh Vutla
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 [this message]
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=20130809153134.GT27325@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.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=lokeshvutla@ti.com \
--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