On Wed, Aug 23, 2023 at 09:10:33PM +0300, Oleksandr Suvorov wrote: > HAS_CAAM should be enabled for all architecture support it. Whereas > FSL_CAAM enables a driver for a device which may be managed by > another system, like OP-TEE. Allow disabling u-boot FSL CAAM driver > on systems with CAAM to prevent access conflicts. > > Signed-off-by: Oleksandr Suvorov <[email protected]> > --- > > arch/arm/mach-imx/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig > index d94b5828d0d..3c178fb435f 100644 > --- a/arch/arm/mach-imx/Kconfig > +++ b/arch/arm/mach-imx/Kconfig > @@ -52,7 +52,7 @@ config USE_IMXIMG_PLUGIN > config IMX_HAB > bool "Support i.MX HAB features" > depends on ARCH_MX7 || ARCH_MX6 || ARCH_MX5 || ARCH_IMX8M || ARCH_MX7ULP > - select FSL_CAAM if HAS_CAAM > + imply FSL_CAAM if HAS_CAAM > imply CMD_DEKBLOB if HAS_CAAM > help > This option enables the support for secure boot (HAB).
What's the use-case here? FSL_CAAM is one of those extremely long lived symbols / IP blocks on NXP/Freescale parts and getting the Kconfig logic such that (as best I could see) we didn't change in-tree behavior here was tricky. -- Tom
signature.asc
Description: PGP signature
