From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v4, 01/10] Kconfig: Separate AM33XX SOC config from target board config
Date: Mon, 3 Oct 2016 09:38:16 -0400 [thread overview]
Message-ID: <20161003133816.GS4884@bill-the-cat> (raw)
In-Reply-To: <20160830190629.13956-2-afd@ti.com>
On Tue, Aug 30, 2016 at 02:06:20PM -0500, Andrew F. Davis wrote:
> The config option AM33XX is used in several boards and should be
> defined as a stand-alone option for this SOC. We break this out
> from target boards that use this SoC and common headers then enable
> AM33XX on in all the boards that used these targets to eliminate any
> functional change with this patch.
>
> This is similar to what has already been done in
> 9de852642cae ("arm: Kconfig: Add support for AM43xx SoC specific Kconfig")
> and is done for the same reasons.
>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
> Acked-by: Lokesh Vutla <lokeshvutla@ti.com>
> Reviewed-by: Tom Rini <trini@konsulko.com>
Applied to u-boot/master, thanks!
--
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/20161003/36a021d9/attachment.sig>
next prev parent reply other threads:[~2016-10-03 13:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 19:06 [U-Boot] [PATCH v4 00/10] Allow secure boot on AM33xx devices Andrew F. Davis
2016-08-30 19:06 ` [U-Boot] [PATCH v4 01/10] Kconfig: Separate AM33XX SOC config from target board config Andrew F. Davis
2016-08-31 3:26 ` Lokesh Vutla
2016-08-31 16:06 ` Hannes Schmelzer
2016-08-31 16:16 ` Andrew F. Davis
2016-08-31 17:45 ` Hannes Schmelzer
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` Tom Rini [this message]
2016-08-30 19:06 ` [U-Boot] [PATCH v4 02/10] am33xx: config.mk: Add support for additional secure boot image types Andrew F. Davis
2016-08-31 3:26 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 03/10] doc: Update info on using AM33xx secure devices from TI Andrew F. Davis
2016-08-31 3:26 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 04/10] am33xx: config.mk: Fix option used to enable SPI SPL image type Andrew F. Davis
2016-08-31 3:27 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 05/10] board: am33xx-hs: Allow post-processing of FIT image on AM33xx Andrew F. Davis
2016-08-31 3:28 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 06/10] ti: omap-common: Allow AM33xx devices to be built securely Andrew F. Davis
2016-08-31 3:28 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 07/10] am335x: configs: Use ISW_ENTRY_ADDR to set SPL_TEXT_BASE Andrew F. Davis
2016-08-31 3:28 ` Lokesh Vutla
2016-09-02 14:53 ` Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 08/10] config: Remove usage of CONFIG_STORAGE_EMMC Andrew F. Davis
2016-08-31 3:28 ` Lokesh Vutla
2016-09-02 14:54 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 09/10] ti_armv7_common: Disable Falcon Mode on HS devices Andrew F. Davis
2016-08-31 3:29 ` Lokesh Vutla
2016-09-02 14:54 ` Tom Rini
2016-10-03 13:38 ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 10/10] defconfig: Add a config for AM335x High Security EVM with SD Boot support Andrew F. Davis
2016-08-31 3:30 ` Lokesh Vutla
2016-09-02 14:54 ` Tom Rini
2016-09-02 14:57 ` Andrew F. Davis
2016-09-02 14:58 ` Tom Rini
2016-09-07 18:04 ` Andrew F. Davis
2016-10-03 13:39 ` [U-Boot] [U-Boot, v4, " 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=20161003133816.GS4884@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 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.