From mboxrd@z Thu Jan  1 00:00:00 1970
From: Fabio Estevam <festevam@gmail.com>
Date: Tue, 5 Jul 2016 17:56:33 -0300
Subject: [U-Boot] [PATCH 4/9] mx7: set soc environment according to
 exact SoC type
In-Reply-To: <7c4acd79f34bca4ab7ea125cabc51b01@agner.ch>
References: <20160703193354.25900-1-stefan@agner.ch>
 <20160703193354.25900-5-stefan@agner.ch>
 <CAOMZO5D0SUHdHJa=qNVxmpKDfP5570sEniJ_X-rU=51mzX1Dpg@mail.gmail.com>
 <7c4acd79f34bca4ab7ea125cabc51b01@agner.ch>
Message-ID: <CAOMZO5Dea6yy2PqDC=WJm9jmrrCxsUg8EMq-q=Hq_kWXV4uKEg@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Tue, Jul 5, 2016 at 5:47 PM, Stefan Agner <stefan@agner.ch> wrote:

> Sounds sensible. Would be the first use of
> CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG in arch/arm/, but I guess that is
> fine.

To keep the consistency you could add
CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG in your board file, just like the
other boards.

> Note that CONFIG_SYS_SOC, which defines the environment variable "soc",
> is currently defined "mx7" by default...
>
> What do you think, do we want
> CONFIG_ARCH_MISC_INIT/CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG set for i.MX
> 7 Sabre/Warp7? Put it in Common directly? Afaik those boards only exist
> in a single variant, hence they always will load the same device tree
> and therefore it wouldn't be really required to determine the SoC at
> runtime.

Correct: we don't need to use CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG for
mx7sabresd/warp as they only use a single variant of the MX7 chip.


>
> --
> Stefan