From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 03/15] arm: Kconfig: Add support for AM43xx SoC specific Kconfig
Date: Fri, 6 May 2016 13:49:01 -0400 [thread overview]
Message-ID: <20160506174901.GF24828@bill-the-cat> (raw)
In-Reply-To: <1461787759-31649-4-git-send-email-d-allred@ti.com>
On Wed, Apr 27, 2016 at 03:09:07PM -0500, Daniel Allred wrote:
> From: Madan Srinivas <madans@ti.com>
>
> Adding support for AM43xx secure devices require the addition
> of some SOC specific config options like the amount of memory
> used by public ROM and the address of the entry point of u-boot
> or SPL, as seen by the ROM code, for the image to be built
> correctly.
>
> This mandates the addition of am AM43xx CONFIG option and the
> ARM Kconfig file has been modified to source this SOC Kconfig
> file. Moving the TARGET_AM43XX_EVM config option to the SOC
> KConfig and out of the arch/arm/Kconfig.
>
> Updating defconfigs to add the CONFIG_AM43XX=y statement and
> removing the #define CONFIG_AM43XX from the header file.
>
> Signed-off-by: Madan Srinivas <madans@ti.com>
> Signed-off-by: Daniel Allred <d-allred@ti.com>
>
> Tested-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160506/191fad36/attachment.sig>
next prev parent reply other threads:[~2016-05-06 17:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 20:09 [U-Boot] [PATCH v2 00/15] Support for boot image creation for TI secure devices Daniel Allred
2016-04-27 20:09 ` [U-Boot] [PATCH v2 01/15] doc: Add info on using secure devices from TI Daniel Allred
2016-04-27 20:09 ` [U-Boot] [PATCH v2 02/15] arm: am33xx: Kconfig: Add secure device definitions Daniel Allred
2016-04-27 20:09 ` [U-Boot] [PATCH v2 03/15] arm: Kconfig: Add support for AM43xx SoC specific Kconfig Daniel Allred
2016-04-28 4:29 ` Heiko Schocher
2016-04-28 13:38 ` Andreas Dannenberg
2016-05-04 5:15 ` Heiko Schocher
2016-05-06 17:49 ` Tom Rini [this message]
2016-04-27 20:09 ` [U-Boot] [PATCH v2 04/15] ti: omap-common: Add Kconfig file for secure device support Daniel Allred
2016-04-27 20:09 ` [U-Boot] [PATCH v2 05/15] ti: omap-common: Add commands for generating secure SPL images Daniel Allred
2016-04-27 20:09 ` [U-Boot] [PATCH v2 06/15] ti: AM43xx: config.mk: Add support for generating secure boot images Daniel Allred
2016-04-27 20:09 ` [U-Boot] [PATCH v2 07/15] ti: AM43xx: Use CONFIG options from SOC Kconfig Daniel Allred
2016-04-27 20:09 ` [U-Boot] [PATCH v2 08/15] ti: AM43xx: board: Detect AM43xx HS EVM Daniel Allred
2016-05-06 17:48 ` Tom Rini
2016-04-27 20:09 ` [U-Boot] [PATCH v2 09/15] defconfig: Add a config for AM43xx secure part Daniel Allred
2016-04-27 21:23 ` Andreas Dannenberg
2016-05-06 17:48 ` Tom Rini
2016-04-27 20:09 ` [U-Boot] [PATCH v2 10/15] ti_omap5_common: Update SPL start address on secure parts Daniel Allred
2016-04-27 21:25 ` Andreas Dannenberg
2016-05-06 17:48 ` Tom Rini
2016-04-27 20:09 ` [U-Boot] [PATCH v2 11/15] spl: build: ti: add support for secure boot images Daniel Allred
2016-04-27 20:09 ` [U-Boot] [PATCH v2 12/15] ARM: omap-common: Add device type to CPU string Daniel Allred
2016-04-27 21:27 ` Andreas Dannenberg
2016-05-06 17:48 ` Tom Rini
2016-04-27 20:09 ` [U-Boot] [PATCH v2 13/15] ARM: omap5: add hooks for cpu/SoC fdt fixups Daniel Allred
2016-04-27 21:28 ` Andreas Dannenberg
2016-05-06 17:48 ` Tom Rini
2016-04-27 20:09 ` [U-Boot] [PATCH v2 14/15] ARM: omap5: add ft_board_setup for dra7xx/am57xx Daniel Allred
2016-04-27 21:29 ` Andreas Dannenberg
2016-05-06 17:48 ` Tom Rini
2016-04-27 20:09 ` [U-Boot] [PATCH v2 15/15] defconfig: ti: Add configs for OMAP5-class secure parts Daniel Allred
2016-04-27 21:31 ` Andreas Dannenberg
2016-05-06 17:48 ` Tom Rini
2016-05-02 4:58 ` [U-Boot] [PATCH v2 00/15] Support for boot image creation for TI secure devices Lokesh Vutla
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=20160506174901.GF24828@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox