mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-16 23:45:31 +08:00
eebac67855
DMADEVICES is the top-level option for the slave DMA
subsystem, and should not be selected by device drivers,
as this can cause circular dependencies such as:
drivers/net/ethernet/freescale/Kconfig:6:error: recursive dependency detected!
drivers/net/ethernet/freescale/Kconfig:6: symbol NET_VENDOR_FREESCALE depends on PPC_BESTCOMM
drivers/dma/bestcomm/Kconfig:6: symbol PPC_BESTCOMM depends on DMADEVICES
drivers/dma/Kconfig:6: symbol DMADEVICES is selected by CRYPTO_DEV_SP_CCP
drivers/crypto/ccp/Kconfig:10: symbol CRYPTO_DEV_SP_CCP depends on CRYPTO
crypto/Kconfig:16: symbol CRYPTO is selected by LIBCRC32C
lib/Kconfig:222: symbol LIBCRC32C is selected by LIQUIDIO
drivers/net/ethernet/cavium/Kconfig:65: symbol LIQUIDIO depends on PTP_1588_CLOCK
drivers/ptp/Kconfig:8: symbol PTP_1588_CLOCK is implied by FEC
drivers/net/ethernet/freescale/Kconfig:23: symbol FEC depends on NET_VENDOR_FREESCALE
The LIQUIDIO driver causing this problem is addressed in a
separate patch, but this change is needed to prevent it from
happening again.
Using "depends on DMADEVICES" is what we do for all other
implementations of slave DMA controllers as well.
Fixes: b3c2fee5d6 ("crypto: ccp - Ensure all dependencies are specified")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
56 lines
1.7 KiB
Plaintext
56 lines
1.7 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
config CRYPTO_DEV_CCP_DD
|
|
tristate "Secure Processor device driver"
|
|
depends on CPU_SUP_AMD || ARM64
|
|
default m
|
|
help
|
|
Provides AMD Secure Processor device driver.
|
|
If you choose 'M' here, this module will be called ccp.
|
|
|
|
config CRYPTO_DEV_SP_CCP
|
|
bool "Cryptographic Coprocessor device"
|
|
default y
|
|
depends on CRYPTO_DEV_CCP_DD && DMADEVICES
|
|
select HW_RANDOM
|
|
select DMA_ENGINE
|
|
select CRYPTO_SHA1
|
|
select CRYPTO_SHA256
|
|
help
|
|
Provides the support for AMD Cryptographic Coprocessor (CCP) device
|
|
which can be used to offload encryption operations such as SHA, AES
|
|
and more.
|
|
|
|
config CRYPTO_DEV_CCP_CRYPTO
|
|
tristate "Encryption and hashing offload support"
|
|
default m
|
|
depends on CRYPTO_DEV_CCP_DD
|
|
depends on CRYPTO_DEV_SP_CCP
|
|
select CRYPTO_HASH
|
|
select CRYPTO_SKCIPHER
|
|
select CRYPTO_AUTHENC
|
|
select CRYPTO_RSA
|
|
select CRYPTO_LIB_AES
|
|
help
|
|
Support for using the cryptographic API with the AMD Cryptographic
|
|
Coprocessor. This module supports offload of SHA and AES algorithms.
|
|
If you choose 'M' here, this module will be called ccp_crypto.
|
|
|
|
config CRYPTO_DEV_SP_PSP
|
|
bool "Platform Security Processor (PSP) device"
|
|
default y
|
|
depends on CRYPTO_DEV_CCP_DD && X86_64
|
|
help
|
|
Provide support for the AMD Platform Security Processor (PSP).
|
|
The PSP is a dedicated processor that provides support for key
|
|
management commands in Secure Encrypted Virtualization (SEV) mode,
|
|
along with software-based Trusted Execution Environment (TEE) to
|
|
enable third-party trusted applications.
|
|
|
|
config CRYPTO_DEV_CCP_DEBUGFS
|
|
bool "Enable CCP Internals in DebugFS"
|
|
default n
|
|
depends on CRYPTO_DEV_SP_CCP
|
|
help
|
|
Expose CCP device information such as operation statistics, feature
|
|
information, and descriptor queue contents.
|