From: Varun Wadekar <vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Varun Wadekar <vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: [PATCH v8 0/2] crypto: driver for Tegra AES hardware
Date: Fri, 16 Dec 2011 16:55:53 +0530 [thread overview]
Message-ID: <1324034755-3295-1-git-send-email-vwadekar@nvidia.com> (raw)
The tegra crypto driver uses the tegra_chip_uid API for the RNG
calculation. If one wants to build tegra-aes as a module, then
tegra_chip_uid needs to be exported.
I have also posted "arm: tegra: export tegra_chip_uid" to the mach-tegra
maintainers to get this patch into their tree, but for compiling the
"crypto: driver for Tegra AES hardware" patch, "arm: tegra: export tegra_chip_uid"
has to be present.
I leave it to the linux-crypto maintainers to decide how they want to
tackle this situation. In order to facilitate smooth compilation of the
actual crytpo driver patch sending the tegra_chip_uid patch as well.
v8:
---
Fixed James's comments for patch v7.
v7:
---
Changed the memset/memcpy logic for copying of the key. Now memset and
memcpy work on mutually exclusive addresses.
v6:
---
Fixed the subject line in the cover letter and removed the
'Change-Id: xxxx' lines from the commits
v5:
---
Specifically mention the dependancy between "arm: tegra: export tegra_chip_uid"
and "crypto: driver for Tegra AES hardware"
v4:
---
Mentioned the dependancy on the "arm: tegra: export tegra_chip_uid"
patch
v3:
---
Add the following code from KimP in tegra_aes_handle_req
tfm = crypto_ablkcipher_reqtfm(req);
...
ctx = crypto_ablkcipher_ctx(tfm);
...
dd->ivlen = crypto_ablkcipher_ivsize(tfm);
v2:
---
Fixed the enable/disable irq related comments from Kim Phillips and some
other cosmetic changes.
v1:
---
Fixed the compilation issues that Henning reported. The driver now
builds as a module. Use devm_* apis. Fixed other comments from StephenW
and KimP.
Henning Heinold (1):
arm: tegra: export tegra_chip_uid
Varun Wadekar (1):
crypto: driver for Tegra AES hardware
arch/arm/mach-tegra/fuse.c | 2 +
drivers/crypto/Kconfig | 11 +
drivers/crypto/Makefile | 1 +
drivers/crypto/tegra-aes.c | 1102 ++++++++++++++++++++++++++++++++++++++++++++
drivers/crypto/tegra-aes.h | 103 ++++
5 files changed, 1219 insertions(+), 0 deletions(-)
create mode 100644 drivers/crypto/tegra-aes.c
create mode 100644 drivers/crypto/tegra-aes.h
next reply other threads:[~2011-12-16 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 11:25 Varun Wadekar [this message]
2011-12-16 11:25 ` [PATCH v8 1/2] arm: tegra: export tegra_chip_uid Varun Wadekar
[not found] ` <1324034755-3295-2-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-12 10:39 ` Varun Wadekar
2011-12-16 11:25 ` [PATCH v8 2/2] crypto: driver for Tegra AES hardware Varun Wadekar
[not found] ` <1324034755-3295-3-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-09 5:27 ` Varun Wadekar
[not found] ` <4F0A7AA9.6020104-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-10 5:29 ` Mark Brown
2012-01-12 10:40 ` Varun Wadekar
2011-12-16 19:58 ` [PATCH v8 0/2] " Stephen Warren
[not found] ` <1324034755-3295-1-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-13 5:35 ` Herbert Xu
2012-01-13 5:37 ` Varun Wadekar
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=1324034755-3295-1-git-send-email-vwadekar@nvidia.com \
--to=vwadekar-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).