diff options
author | Stephen Warren <swarren@nvidia.com> | 2017-09-14 12:51:18 -0400 |
---|---|---|
committer | mobile promotions <svcmobile_promotions@nvidia.com> | 2017-10-29 14:00:42 -0400 |
commit | 20bb0324e532863cafc5dc41e8cd5a6ec28413d8 (patch) | |
tree | b1dffa63f11bb210bfc6b84ce0fc6f940428fa61 /drivers/crypto/Kconfig | |
parent | c04513ee6f787a70c9cc839117918e92e38ae9ff (diff) |
nvidia: use kernel overlay features
Update all Kconfig files and Makefiles to rely on the kernel overlay
feature. In particular, don't include any Kconfig files or Makefiles
from other overlays. -I directives in CFLAGS are not yet cleaned up.
Bug 1978395
Change-Id: I425d37d55f8ea61fb3a082a1504f994ff30cec03
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Reviewed-on: https://git-master.nvidia.com/r/1561187
Reviewed-by: Terje Bergstrom <tbergstrom@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Diffstat (limited to 'drivers/crypto/Kconfig')
-rw-r--r-- | drivers/crypto/Kconfig | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig new file mode 100644 index 000000000..c71a21cfc --- /dev/null +++ b/drivers/crypto/Kconfig | |||
@@ -0,0 +1,40 @@ | |||
1 | if CRYPTO_HW | ||
2 | |||
3 | config TEGRA_CRYPTO_DEV | ||
4 | tristate "Device node to access tegra aes hardware" | ||
5 | depends on CRYPTO_DEV_TEGRA_ELLIPTIC_SE | ||
6 | help | ||
7 | Dev node /dev/tegra-crypto in order to get access to tegra aes | ||
8 | hardware from user space | ||
9 | |||
10 | config CRYPTO_DEV_TEGRA_SE | ||
11 | tristate "Tegra SE driver for crypto algorithms" | ||
12 | select CRYPTO_AES | ||
13 | help | ||
14 | This option allows you to have support of Security Engine for crypto acceleration. | ||
15 | |||
16 | config CRYPTO_DEV_TEGRA_ELLIPTIC_SE | ||
17 | tristate "Tegra SE for Elliptic crypto algorithms" | ||
18 | select CRYPTO_ECDH | ||
19 | select CRYPTO_ECDSA | ||
20 | help | ||
21 | This option allows you to have support of Security Engine | ||
22 | for Elliptic PKA1 and RNG1 Crypto Algorithms. PKA1 supports | ||
23 | Public Key Algorithms, RSA (upto 4K bits) and ECC (Elliptic | ||
24 | Curve Cryptography, upto 521 bits) features internally. RNG1 | ||
25 | supports random number generation. | ||
26 | |||
27 | config CRYPTO_DEV_TEGRA_SE_USE_HOST1X_INTERFACE | ||
28 | tristate "Use Host1x Interface for Tegra SE crypto algorithms" | ||
29 | depends on ARCH_TEGRA_18x_SOC | ||
30 | help | ||
31 | This allows you to use Host1x Memory Interface for Tegra SE Driver | ||
32 | Crypto algorithms. | ||
33 | |||
34 | config CRYPTO_DEV_TEGRA_VIRTUAL_SE_INTERFACE | ||
35 | tristate "Virtual SE interface for Tegra SE crypto algorithms" | ||
36 | depends on ARCH_TEGRA_18x_SOC && CRYPTO_DEV_TEGRA_SE | ||
37 | help | ||
38 | This allows you to use Virtual SE interface for Tegra Crypto algorithms. | ||
39 | |||
40 | endif | ||