mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-23 05:03:52 +07:00
b4b8cbf679
Every developer always thinks that _their_ code is so special and magical that it should be enabled by default. And most of them are completely and utterly wrong. That's definitely the case when you write a specialty driver for a very unsual "security processor". It does *not* get to mark itself as "default m". If you solve world hunger, and make a driver that cures people of cancer, by all means enable it by default. But afaik, the Cavium CNN55XX does neither. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
21 lines
477 B
Plaintext
21 lines
477 B
Plaintext
#
|
|
# Cavium NITROX Crypto Device configuration
|
|
#
|
|
config CRYPTO_DEV_NITROX
|
|
tristate
|
|
select CRYPTO_BLKCIPHER
|
|
select CRYPTO_AES
|
|
select CRYPTO_DES
|
|
select FW_LOADER
|
|
|
|
config CRYPTO_DEV_NITROX_CNN55XX
|
|
tristate "Support for Cavium CNN55XX driver"
|
|
depends on PCI_MSI && 64BIT
|
|
select CRYPTO_DEV_NITROX
|
|
help
|
|
Support for Cavium NITROX family CNN55XX driver
|
|
for accelerating crypto workloads.
|
|
|
|
To compile this as a module, choose M here: the module
|
|
will be called n5pf.
|