Hello all, To see the background on this see here[0].
As Simon suggested we are now using a linker list to keep any and all TEE specific code out of common files as, unlike kernel, dtb, and ramdisk TEE images may not be used by needed by all users. The last 4 patches in this series are an example of how one can now add a handler for an image type for their platform. Thanks, Andrew [0] http://lists.denx.de/pipermail/u-boot/2016-November/272614.html Changes from v1: - Added some additional documentation - Last 4 patches are now the compleate working TEE loading solution for our DRA7xx/AM57xx platforms, not just an example Andrew F. Davis (4): image: Add FIT image loadable section custom processing image: Add Trusted Execution Environment image type board: ti: dra7xx: add FIT image TEE processing board: ti: am57xx: add FIT image TEE processing Harinarayan Bhatta (2): arm: omap5: add function to make an SMC call on cpu1 arm: omap5: Add TEE loading support arch/arm/include/asm/omap_common.h | 1 + arch/arm/include/asm/omap_sec_common.h | 6 ++ arch/arm/mach-omap2/omap5/Makefile | 1 + arch/arm/mach-omap2/omap5/sec-fxns.c | 114 ++++++++++++++++++++++++++ arch/arm/mach-omap2/omap5/sec_entry_cpu1.S | 123 +++++++++++++++++++++++++++++ board/ti/am57xx/board.c | 7 ++ board/ti/dra7xx/evm.c | 7 ++ common/image.c | 34 ++++++++ doc/uImage.FIT/source_file_format.txt | 4 +- include/image.h | 31 ++++++++ 10 files changed, 327 insertions(+), 1 deletion(-) create mode 100644 arch/arm/mach-omap2/omap5/sec_entry_cpu1.S -- 2.10.2 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
