From: Andreas Westin <andreas.westin@stericsson.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: <linux-crypto@vger.kernel.org>,
Andreas Westin <andreas.westin@stericsson.com>
Subject: [PATCH 0/2] crypto: ux500 crypto and hash driver
Date: Thu, 23 Feb 2012 13:58:55 +0100 [thread overview]
Message-ID: <1330001937-2108-1-git-send-email-andreas.westin@stericsson.com> (raw)
Hi,
This adds a driver for the ST-Ericsson ux500 hardware
crypto and hash module.
It supports:
* AES with 128, 192 and 256bit keysize and ECB, CBC and CTR modes.
* DES and 3DES
* SHA-1 and SHA-256
One patch for the driver and one for core support.
/Andreas
Andreas Westin (2):
crypto: ux500 - Add driver for CRYP/HASH hardware.
mach-ux500: Crypto: core support for CRYP/HASH module.
arch/arm/mach-ux500/board-mop500.c | 48 +
arch/arm/mach-ux500/board-u5500.c | 48 +
arch/arm/mach-ux500/clock.c | 18 +-
arch/arm/mach-ux500/devices-common.c | 16 +
arch/arm/mach-ux500/devices-common.h | 23 +
arch/arm/mach-ux500/devices-db5500.h | 5 +
arch/arm/mach-ux500/devices-db8500.h | 5 +
arch/arm/mach-ux500/include/mach/crypto-ux500.h | 21 +
arch/arm/mach-ux500/include/mach/devices.h | 3 +
arch/arm/mach-ux500/ste-dma40-db5500.h | 9 +-
drivers/crypto/Kconfig | 11 +
drivers/crypto/Makefile | 1 +
drivers/crypto/ux500/Kconfig | 29 +
drivers/crypto/ux500/Makefile | 8 +
drivers/crypto/ux500/cryp/Makefile | 13 +
drivers/crypto/ux500/cryp/cryp.c | 418 +++++
drivers/crypto/ux500/cryp/cryp.h | 308 +++
drivers/crypto/ux500/cryp/cryp_core.c | 2276 +++++++++++++++++++++++
drivers/crypto/ux500/cryp/cryp_irq.c | 45 +
drivers/crypto/ux500/cryp/cryp_irq.h | 31 +
drivers/crypto/ux500/cryp/cryp_irqp.h | 125 ++
drivers/crypto/ux500/cryp/cryp_p.h | 124 ++
drivers/crypto/ux500/hash/Makefile | 11 +
drivers/crypto/ux500/hash/hash_alg.h | 387 ++++
drivers/crypto/ux500/hash/hash_alg_p.h | 26 +
drivers/crypto/ux500/hash/hash_core.c | 2036 ++++++++++++++++++++
26 files changed, 6034 insertions(+), 11 deletions(-)
create mode 100644 arch/arm/mach-ux500/include/mach/crypto-ux500.h
create mode 100644 drivers/crypto/ux500/Kconfig
create mode 100644 drivers/crypto/ux500/Makefile
create mode 100644 drivers/crypto/ux500/cryp/Makefile
create mode 100644 drivers/crypto/ux500/cryp/cryp.c
create mode 100644 drivers/crypto/ux500/cryp/cryp.h
create mode 100644 drivers/crypto/ux500/cryp/cryp_core.c
create mode 100644 drivers/crypto/ux500/cryp/cryp_irq.c
create mode 100644 drivers/crypto/ux500/cryp/cryp_irq.h
create mode 100644 drivers/crypto/ux500/cryp/cryp_irqp.h
create mode 100644 drivers/crypto/ux500/cryp/cryp_p.h
create mode 100644 drivers/crypto/ux500/hash/Makefile
create mode 100644 drivers/crypto/ux500/hash/hash_alg.h
create mode 100644 drivers/crypto/ux500/hash/hash_alg_p.h
create mode 100644 drivers/crypto/ux500/hash/hash_core.c
--
1.7.9
next reply other threads:[~2012-02-23 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 12:58 Andreas Westin [this message]
2012-02-23 12:58 ` [PATCH 2/2] mach-ux500: Crypto: core support for CRYP/HASH module Andreas Westin
-- strict thread matches above, loose matches on Subject: below --
2012-02-24 13:57 [PATCH 0/2] crypto: ux500 crypto and hash driver Andreas Westin
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=1330001937-2108-1-git-send-email-andreas.westin@stericsson.com \
--to=andreas.westin@stericsson.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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).