David Gstir 633cb72fb6 KEYS: trusted: improve scalability of trust source config ... Enabling trusted keys requires at least one trust source implementation (currently TPM, TEE or CAAM) to be enabled. Currently, this is done by checking each trust source's config option individually. This does not scale when more trust sources like the one for DCP are added, because the condition will get long and hard to read. Add config HAVE_TRUSTED_KEYS which is set to true by each trust source once its enabled and adapt the check for having at least one active trust source to use this option. Whenever a new trust source is added, it now needs to select HAVE_TRUSTED_KEYS. Signed-off-by: David Gstir <david@sigma-star.at> Tested-by: Jarkko Sakkinen <jarkko@kernel.org> # for TRUSTED_KEYS_TPM Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>		2024-05-09 18:29:03 +03:00
..
Kconfig	KEYS: trusted: improve scalability of trust source config	2024-05-09 18:29:03 +03:00
Makefile	KEYS: trusted: Introduce support for NXP CAAM-based trusted keys	2022-05-23 18:47:50 +03:00
tpm2key.asn1
trusted_caam.c	KEYS: trusted: Introduce support for NXP CAAM-based trusted keys	2022-05-23 18:47:50 +03:00
trusted_core.c	KEYS: trusted: Rollback init_trusted() consistently	2023-10-24 03:06:06 +03:00
trusted_tee.c	KEYS: trusted: tee: Refactor register SHM usage	2023-10-24 03:06:35 +03:00
trusted_tpm1.c
trusted_tpm2.c	security: keys: Modify mismatched function name	2023-07-17 19:40:27 +00:00