Today, only a few platforms enable SPL_LOAD_FIT_FULL, and all enable
SPL_LOAD_FIT. As can be seen in usage, the FULL symbol is a superset of
the first symbol, not an alternative. Update Kconfig entries based on
this and simplify the only code which checks for either being set.
Signed-off-by: Tom Rini <trini@konsulko.com>
config SPL_FIT_SIGNATURE
bool "Enable signature verification of FIT firmware within SPL"
depends on SPL_DM
- depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
+ depends on SPL_LOAD_FIT
select FIT_SIGNATURE
select SPL_FIT
select SPL_CRYPTO
config SPL_LOAD_FIT_FULL
bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
- select SPL_FIT
+ depends on SPL_LOAD_FIT
help
Normally with the SPL framework a legacy image is generated as part
of the build. This contains U-Boot along with information as to
config SPL_OPTEE_IMAGE
bool "Support OP-TEE Trusted OS image in SPL"
depends on ARM
- depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
+ depends on SPL_LOAD_FIT
help
OP-TEE is an open source Trusted OS which is loaded by SPL.
More detail at: https://github.com/OP-TEE/optee_os
return IS_ENABLED(CONFIG_SPL_LOAD_IMX_CONTAINER);
case FIT_INTERNAL:
case FIT_EXTERNAL:
- return IS_ENABLED(CONFIG_SPL_LOAD_FIT) ||
- IS_ENABLED(CONFIG_SPL_LOAD_FIT_FULL);
+ return IS_ENABLED(CONFIG_SPL_LOAD_FIT);
}
return false;