All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dannenberg <dannenberg@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 07/16] ti: AM43xx: Use CONFIG options from SOC Kconfig
Date: Tue, 19 Apr 2016 10:10:21 -0500	[thread overview]
Message-ID: <20160419151021.GE13405@borg.dal.design.ti.com> (raw)
In-Reply-To: <1460417838-22343-8-git-send-email-d-allred@ti.com>

On Mon, Apr 11, 2016 at 06:37:09PM -0500, Daniel Allred wrote:
> From: Madan Srinivas <madans@ti.com>
> 
> 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.
> 
> Signed-off-by: Madan Srinivas <madans@ti.com>
> Signed-off-by: Daniel Allred <d-allred@ti.com>

Tested-by: Andreas Dannenberg <dannenberg@ti.com>

Regards,

--
Andreas Dannenberg
Texas Instruments Inc

  parent reply	other threads:[~2016-04-19 15:10 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 23:37 [U-Boot] [PATCH 00/16] Support for boot image creation for TI secure devices Daniel Allred
2016-04-11 23:37 ` [U-Boot] [PATCH 01/16] doc: Add info on using secure devices from TI Daniel Allred
2016-04-15  9:47   ` Lokesh Vutla
2016-04-19 15:21   ` Andreas Dannenberg
2016-04-21 13:38   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 02/16] arm: am33xx: Kconfig: Add secure device definitions Daniel Allred
2016-04-15  9:47   ` Lokesh Vutla
2016-04-19 15:13   ` Andreas Dannenberg
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 03/16] arm: Kconfig: Add support for AM43xx SoC specific Kconfig Daniel Allred
2016-04-15  9:48   ` Lokesh Vutla
2016-04-15 10:57   ` Lokesh Vutla
2016-04-18 21:03     ` Andreas Dannenberg
2016-04-18 23:04       ` Andreas Dannenberg
2016-04-11 23:37 ` [U-Boot] [PATCH 04/16] ti: omap-common: Add Kconfig file for secure device support Daniel Allred
2016-04-15  9:48   ` Lokesh Vutla
2016-04-20 22:48   ` Andreas Dannenberg
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 05/16] ti: omap-common: Add commands for generating secure SPL images Daniel Allred
2016-04-15  9:48   ` Lokesh Vutla
2016-04-20 22:47   ` Andreas Dannenberg
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 06/16] ti: AM43xx: config.mk: Add support for generating secure boot images Daniel Allred
2016-04-15  9:49   ` Lokesh Vutla
2016-04-19 15:12   ` Andreas Dannenberg
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 07/16] ti: AM43xx: Use CONFIG options from SOC Kconfig Daniel Allred
2016-04-15  9:54   ` Lokesh Vutla
2016-04-19 15:10   ` Andreas Dannenberg [this message]
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 08/16] ti: AM43xx: board: Detect AM43xx HS EVM Daniel Allred
2016-04-15  9:55   ` Lokesh Vutla
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 09/16] defconfig: Add configs for AM43xx secure parts Daniel Allred
2016-04-15  9:58   ` Lokesh Vutla
2016-04-21 13:40     ` Tom Rini
2016-04-21 18:24       ` Allred, Daniel
2016-04-21 19:04         ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 10/16] ti_omap5_common: Update SPL start address on " Daniel Allred
2016-04-15  9:58   ` Lokesh Vutla
2016-04-20 22:50   ` Andreas Dannenberg
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 11/16] spl: build: ti: add support for secure boot images Daniel Allred
2016-04-15  9:59   ` Lokesh Vutla
2016-04-21 13:39   ` Tom Rini
2016-04-21 17:27   ` Andreas Dannenberg
2016-04-11 23:37 ` [U-Boot] [PATCH 12/16] ARM: omap4/5: Add device type to CPU string Daniel Allred
2016-04-15  9:59   ` Lokesh Vutla
2016-04-19 16:26   ` Andreas Dannenberg
2016-04-21 17:55     ` Andreas Dannenberg
2016-04-21 18:01       ` Allred, Daniel
2016-04-21 18:59         ` Andreas Dannenberg
2016-04-21 20:27           ` Tom Rini
2016-04-21 22:56             ` Andreas Dannenberg
2016-04-21 23:38               ` Tom Rini
2016-04-22 15:50                 ` Andreas Dannenberg
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 13/16] ARM: omap5: add hooks for cpu/SoC fdt fixups Daniel Allred
2016-04-15 10:03   ` Lokesh Vutla
2016-04-20 22:53   ` Andreas Dannenberg
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 14/16] ARM: omap5: add ft_board_setup for dra7xx/am57xx Daniel Allred
2016-04-15 10:03   ` Lokesh Vutla
2016-04-20 22:55   ` Andreas Dannenberg
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 15/16] ARM: omap5: Add config for board/cpu fdt fixups Daniel Allred
2016-04-15 10:05   ` Lokesh Vutla
2016-04-20 22:55   ` Andreas Dannenberg
2016-04-21 13:39   ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 16/16] defconfig: ti: Add configs for OMAP5-class secure parts Daniel Allred
2016-04-15 10:05   ` Lokesh Vutla
2016-04-20 22:57   ` Andreas Dannenberg
2016-04-21 13:40   ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160419151021.GE13405@borg.dal.design.ti.com \
    --to=dannenberg@ti.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.