aboutsummaryrefslogtreecommitdiff
path: root/common/fdt_support.c
diff options
context:
space:
mode:
authorPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>2017-09-13 21:29:32 +0200
committerPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>2017-11-26 00:39:07 +0100
commitd879616e9e64cf5a9c43dedc30677aa2fa463d64 (patch)
treef68476892269c0d00cea158a6e60c4d64238cccc /common/fdt_support.c
parentf2efe6786eeaa2305353a01056ffef55ae520b7d (diff)
downloadu-boot-d879616e9e64cf5a9c43dedc30677aa2fa463d64.zip
u-boot-d879616e9e64cf5a9c43dedc30677aa2fa463d64.tar.gz
u-boot-d879616e9e64cf5a9c43dedc30677aa2fa463d64.tar.bz2
spl: fit: simplify logic for FDT loading for non-OS boots
To better support bootin through an ATF or OPTEE, we need to streamline some of the logic for when the FDT is appended to an image: depending on the image type, we'd like to append the FDT not at all (the case for the OS boot), to the 'firmware' image (if it is a U-Boot) or to one of the loadables (if the 'firmware' is an ATF, an OPTEE, or some other image-type and U-Boot is listed in the loadabled). To achieve this goal, we drop the os_boot flag and track the type of image loaded. If it is of type IH_OS_U_BOOT, we append the FDT. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Acked-by: York Sun <york.sun@nxp.com> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'common/fdt_support.c')
0 files changed, 0 insertions, 0 deletions