summaryrefslogtreecommitdiff
path: root/drivers/crypto/Kconfig
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2014-02-19 01:42:57 +0400
committerHerbert Xu <herbert@gondor.apana.org.au>2014-02-27 01:56:57 +0400
commit645af2e43705d8c80c9606d5c5e83eda9a1a1a2e (patch)
tree026c965f1498f721ce6e9d5a4d83a1cdc07e26d2 /drivers/crypto/Kconfig
parent701d0f1940925d40f6b8a40f6c278d14be71402b (diff)
downloadlinux-645af2e43705d8c80c9606d5c5e83eda9a1a1a2e.tar.xz
crypto: tegra - remove driver
This driver has never been hooked up in any board file, and cannot be instantiated via device tree. I've been told that, at least on Tegra20, the HW is slower at crypto than the main CPU. I have no test-case for it. Hence, remove it. Cc: Varun Wadekar <vwadekar@nvidia.com> Signed-off-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/Kconfig')
-rw-r--r--drivers/crypto/Kconfig11
1 files changed, 0 insertions, 11 deletions
diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
index 8e38000990d7..03ccdb0ccf9e 100644
--- a/drivers/crypto/Kconfig
+++ b/drivers/crypto/Kconfig
@@ -311,17 +311,6 @@ config CRYPTO_DEV_S5P
Select this to offload Samsung S5PV210 or S5PC110 from AES
algorithms execution.
-config CRYPTO_DEV_TEGRA_AES
- tristate "Support for TEGRA AES hw engine"
- depends on ARCH_TEGRA
- select CRYPTO_AES
- help
- TEGRA processors have AES module accelerator. Select this if you
- want to use the TEGRA module for AES algorithms.
-
- To compile this driver as a module, choose M here: the module
- will be called tegra-aes.
-
config CRYPTO_DEV_NX
bool "Support for IBM Power7+ in-Nest cryptographic acceleration"
depends on PPC64 && IBMVIO