From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 01/11] Kconfig: Separate AM33XX SOC config from target board config
Date: Fri, 26 Aug 2016 16:12:09 -0400 [thread overview]
Message-ID: <20160826201209.GL32344@bill-the-cat> (raw)
In-Reply-To: <20160822152131.15340-2-afd@ti.com>
On Mon, Aug 22, 2016 at 10:21:21AM -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_AM335X_* then enable AM33XX on in all the boards that
> used TARGET_AM335X_* to eliminate any functional change with
> this patch. Also conditionally define this in ti_am335x_common.h to prevent
> redefinition. The definition can be removed completely when all platforms
> that include this header have this definition added to their defconfig.
>
> 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>
[snip]
> diff --git a/include/configs/ti_am335x_common.h b/include/configs/ti_am335x_common.h
> index bcd56fc..7a4c043 100644
> --- a/include/configs/ti_am335x_common.h
> +++ b/include/configs/ti_am335x_common.h
> @@ -12,7 +12,9 @@
> #ifndef __CONFIG_TI_AM335X_COMMON_H__
> #define __CONFIG_TI_AM335X_COMMON_H__
>
> +#ifndef CONFIG_AM33XX
> #define CONFIG_AM33XX
> +#endif
> #define CONFIG_ARCH_CPU_INIT
> #define CONFIG_SYS_CACHELINE_SIZE 64
> #define CONFIG_MAX_RAM_BANK_SIZE (1024 << 20) /* 1GB */
We should do the fixup in this commit and drop the line from this
header.
--
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/20160826/2cc0718d/attachment.sig>
next prev parent reply other threads:[~2016-08-26 20:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 15:21 [U-Boot] [PATCH v2 00/11] Allow secure boot on AM33xx devices Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 01/11] Kconfig: Separate AM33XX SOC config from target board config Andrew F. Davis
2016-08-26 20:12 ` Tom Rini [this message]
2016-08-22 15:21 ` [U-Boot] [PATCH v2 02/11] am33xx: config.mk: Add support for additional secure boot image types Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 03/11] am33xx: config.mk: Fix option used to enable SPI SPL image type Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 04/11] doc: Update info on using AM33xx secure devices from TI Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 05/11] ti: omap-common: Allow AM33xx devices to be built securely Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [PATCH v2 06/11] board: am33xx-hs: spl: Allow post-processing of FIT image on AM33xx Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 07/11] omap: Use SD_BOOT in place of EMMC_BOOT Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 08/11] config: Remove usage of CONFIG_STORAGE_EMMC Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 09/11] spl: Kconfig: Add SPL_<media>_SUPPORT as Kconfig option Andrew F. Davis
2016-08-23 6:08 ` Masahiro Yamada
2016-08-23 15:02 ` Andrew F. Davis
2016-08-26 20:06 ` Tom Rini
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 10/11] spl: Kconfig: Add SPL_<media>_BOOT " Andrew F. Davis
2016-08-22 15:21 ` [U-Boot] [RFC PATCH v2 11/11] spl: Kconfig: Add CONFIG_SPL_TEXT_BASE " Andrew F. Davis
2016-08-23 5:45 ` Masahiro Yamada
2016-08-23 14:57 ` Andrew F. Davis
2016-08-26 17:59 ` 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=20160826201209.GL32344@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