arm-trusted-firmware: add option to enable/disable building FIP image
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Sun, 3 Dec 2017 21:48:04 +0000 (22:48 +0100)
committerPeter Korsgaard <peter@korsgaard.com>
Fri, 8 Dec 2017 11:14:42 +0000 (12:14 +0100)
commit543dbf2d01325d0352d9b4b2d69996bf072c906e
treec1854283b1dfb14cf8ca5c429d563d0246f67e01
parentae2a68936fcea83e8eb8f6dc641f3f1b34571af1
arm-trusted-firmware: add option to enable/disable building FIP image

Currently, our arm-trusted-firmware unconditionally builds a FIP
(Firmware Image Package). While this is often needed on platforms
where ATF encapsulates U-Boot, it is not the case on some other
platforms where it's U-Boot that encapsulates parts of ATF.

In order to prepare the support for the later platforms, we make
building the FIP image optional, and update the only defconfig we have
that uses ARM Trusted Firmware.

Note: we considered adding a "default y" here to preserve backward
compatibility, but there really isn't any default that is sane:
whether a FIP image needs to be built or not is purely platform
specific.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: Sergey Matyukevich <geomatsi@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
boot/arm-trusted-firmware/Config.in
boot/arm-trusted-firmware/arm-trusted-firmware.mk
configs/arm_juno_defconfig