From: Varun Wadekar Subject: [PATCH v5 0/2] *** SUBJECT HERE *** Date: Wed, 16 Nov 2011 13:54:08 +0530 Message-ID: <1321431850-21906-1-git-send-email-vwadekar@nvidia.com> Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org, ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org, Varun Wadekar To: linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-crypto.vger.kernel.org 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 as well. 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