summaryrefslogtreecommitdiff
path: root/configs/lion-rk3368_defconfig
diff options
context:
space:
mode:
authorPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>2017-09-13 19:46:03 +0200
committerPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>2017-11-01 23:20:53 +0100
commitee14ee242290da6d59b7820a534b5735ccbac6a2 (patch)
tree7ab617b210444b5be72ed3436432ba5c1c67c18b /configs/lion-rk3368_defconfig
parent670fda8c2310ed7772281ed1891d8fa94c000223 (diff)
rockchip: defconfig: lion-rk3368: sync up with SPL changes for ATF
This tracks the SPL changes for ATF for the RK3368-uQ7: * renames ATF_SUPPORT to ATF * drops CONFIG_SPL_ATF_TEXT_BASE (now dynamically retrieved from the .itb file) Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Series-cc: Kever Yang <kever.yang@rock-chips.com> Series-cc: sjg Series-cc: Klaus Goger <klaus.goger@theobroma-systems.com> Cover-letter: spl: atf: update booting images via ATF to use info from FIT images A number of things about how we boot the RK3368 and RK3399 through ATF are less than ideal today, especially when considering future platforms that will follow a similar boot concept: - the auto-detection of images from the FIT images was limited (i.e. the start address of the BL33 image could not automatically retrieved) - no implementation for the platform-specific parameters existed (and there is a danger that we'll end up with highly different, proprietary platform parameters for different SOCs and boards, even though the ATF code base already has FDT support) This series tries to put us into a better position to support various boot scenarios (e.g. loading an OPTEE from the FIT image; and: booting a Linux kernel via ATF) in the future... and it establishes the FDT as a mechanism to pass boot-info to later stages. For a practical example, refer to how we use this on the RK3399-Q7: * the ATF can read the full U-Boot's FDT to determine how to best issue a cold-reset for the board * we inject information on where we loaded the M0 firmware into the same FDT that is now visible to the ATF, so the ATF can relocate it to its final destination---and we no longer need to overwrite parts of the SPL binary during bootup Note that there are still some limitations (e.g. the support for passing OPTEE as a BL3-2, is not in this version ... and there isn't support for booting Linux directly via ATF yet, either), but these can now be plugged cleanly into this infrastructure. END
Diffstat (limited to 'configs/lion-rk3368_defconfig')
-rw-r--r--configs/lion-rk3368_defconfig3
1 files changed, 1 insertions, 2 deletions
diff --git a/configs/lion-rk3368_defconfig b/configs/lion-rk3368_defconfig
index 8dae75cefd..9548b961e3 100644
--- a/configs/lion-rk3368_defconfig
+++ b/configs/lion-rk3368_defconfig
@@ -32,8 +32,7 @@ CONFIG_SPL_BOOTROM_SUPPORT=y
CONFIG_TPL_SYS_MALLOC_SIMPLE=y
CONFIG_SPL_STACK_R=y
CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR=0x200
-CONFIG_SPL_ATF_SUPPORT=y
-CONFIG_SPL_ATF_TEXT_BASE=0x10000
+CONFIG_SPL_ATF=y
CONFIG_TPL=y
CONFIG_TPL_BOOTROM_SUPPORT=y
CONFIG_TPL_DRIVERS_MISC_SUPPORT=y