Alexandru Gagniuc f6953047cb lib: optee: Remove CONFIG_OPTEE_LOAD_ADDR ... This value is not used by u-boot, and it should not. The load address of an OPTEE image is defined by said image. Either a uImage or a FIT will have a defined load address and entry point. Those values are the correct ones, not CONFIG_OPTEE_LOAD_ADDR. Commit f25006b96e ("optee: Add CONFIG_OPTEE_LOAD_ADDR") justifies this config by requiring its presence in u-boot's .config for other images as part of a larger build, claiming it is "the best way". This argument is not persuasive. U-boot's configuration is driven by platform requirements, not the other way around. It seems more likely that the argument is conflating tooling issues with Kconfig. Yocto and buildroot have excellent mechanisms for defining values across the board (pun intended). u-boot's Kconfig is the wrong place to do it. Furthermore, it is not "best" for u-boot because it hardcodes a value which is then not used. In fact the load address that u-boot uses is the one derived from the OPTEE image. Confused yet? I sure was. To prevent future confusion, remove CONFIG_OPTEE_LOAD_ADDR. Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>		2021-10-05 08:47:13 -04:00
..
Kconfig	lib: optee: Remove CONFIG_OPTEE_LOAD_ADDR	2021-10-05 08:47:13 -04:00
Makefile	lib: optee: remove the duplicate CONFIG_OPTEE	2021-10-05 08:44:48 -04:00
optee.c	lib: optee: Avoid CONFIG_TZDRAM_* in optee_verify_bootm_image()	2021-10-05 08:46:23 -04:00