From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lokesh Vutla Date: Fri, 15 Apr 2016 15:24:57 +0530 Subject: [U-Boot] [PATCH 07/16] ti: AM43xx: Use CONFIG options from SOC Kconfig In-Reply-To: <1460417838-22343-8-git-send-email-d-allred@ti.com> References: <1460417838-22343-1-git-send-email-d-allred@ti.com> <1460417838-22343-8-git-send-email-d-allred@ti.com> Message-ID: <5710BA71.7080106@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote: > From: Madan Srinivas > > Updates configs/am43xx_evm.h to use CONFIG options from > SOC specific Kconfig file for various calculations. > > On AM43x devices, the address of SPL entry point depends on > the device type, i.e. whether it is secure or non-secure. > > Further, for non-secure devices, the SPL entry point is different > between USB HOST boot mode, other "memory" boot modes (MMC, NAND) > and "peripheral" boot modes (UART, USB) > > To add to the complexity, on secure devices, in addition to the > above differences, the SPL entry point can change because of the > space occupied by other components (other than u-boot or spl) > that go into a secure boot image. > > To prevent the user from having to modify source files every time > any component of the secure image changes, the value of > CONFIG_SPL_TEXT_BASE has been set using a Kconfig option that > is supplied in the am43xx_*_defconfig files > > Using the CONFIG options also enables us to do away with some > compile time flags that were used to specify CONFIG_SPL_TEXT_BASE > for different boot modes. > > On QSPI devices, the same problem described above occurs w.r.t. the > address of the u-boot entry point in flash, when booting secure > devices. To handle this, CONFIG_SYS_TEXT_BASE is also setup via > a Kconfig option and the defconfig files. Reviewed-by: Lokesh Vutla Thanks and regards, Lokesh