From: "Mathew McBride" <matt@traverse.com.au>
To: "Tom Rini" <trini@konsulko.com>
Cc: u-boot@lists.denx.de, "Priyanka Jain" <priyanka.jain@nxp.com>
Subject: Re: [PATCH v2 2/2] board: traverse: add initial Ten64 support
Date: Thu, 18 Nov 2021 09:09:44 +1100 [thread overview]
Message-ID: <017630d6-ca34-4121-b5a7-c306948dae1b@www.fastmail.com> (raw)
In-Reply-To: <20211111182046.GU24579@bill-the-cat>
Hi Tom,
On Fri, Nov 12, 2021, at 5:20 AM, Tom Rini wrote:
> On Wed, Nov 10, 2021 at 04:46:39AM +0000, Mathew McBride wrote:
>
> > Signed-off-by: Mathew McBride <matt@traverse.com.au>
> > ---
> > arch/arm/Kconfig | 16 ++
> > arch/arm/dts/Makefile | 2 +
> > arch/arm/dts/fsl-ls1088a-ten64.dts | 377 +++++++++++++++++++++++++
>
> What is the status of this dts with upstream Linux?
It's been in Linux since v5.15, though there is going to be some flux between U-Boot and Linux for a short while as some devices will be introduced into one or the other other first.
e.g traverse,ten64-controller does not and will not have a Linux (kernel) counterpart but I'll try and get it added to the dt yaml's for validation.
(The upstream DTS intentionally left out some I2C devices that don't have Linux drivers or formal DT bindings yet)
> [snip]
>
>
> > +#define QSPI_NOR_BOOTCOMMAND "run distro_bootcmd"
> > +#define SD_BOOTCOMMAND "run distro_bootcmd"
>
> You should just set CONFIG_USE_BOOTCOMMAND and then CONFIG_BOOTCOMMAND
> will be "run distro_bootcmd". Thanks!
This actually comes about from fsl_setenv_bootcmd:
https://elixir.bootlin.com/u-boot/latest/source/arch/arm/cpu/armv8/fsl-layerscape/soc.c#L800
Which gets hooked into board_late_init
https://elixir.bootlin.com/u-boot/latest/source/arch/arm/cpu/armv8/fsl-layerscape/soc.c#L961
The main reason I understand that exists is because the secure boot (FSL trust architecture) setup differs a depending on where the board has booted from:
https://elixir.bootlin.com/u-boot/latest/source/include/configs/ls1088ardb.h#L448
(There is also a similar issue with mcinitcmd which does affect us)
Since trust architecture isn't supported on our board yet, it just collapses down to "run distro_bootcmd" regardless of where the board started from.
I guess this behaviour could be hidden behind a Kconfig so it's opt-in?
- Matt
next prev parent reply other threads:[~2021-11-17 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 4:46 [PATCH v2 0/2] Initial Traverse Ten64 board support Mathew McBride
2021-11-10 4:46 ` [PATCH v2 1/2] board: traverse: add Ten64 board controller driver Mathew McBride
2021-11-10 4:46 ` [PATCH v2 2/2] board: traverse: add initial Ten64 support Mathew McBride
2021-11-11 18:20 ` Tom Rini
2021-11-17 22:09 ` Mathew McBride [this message]
2021-11-17 22:29 ` 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=017630d6-ca34-4121-b5a7-c306948dae1b@www.fastmail.com \
--to=matt@traverse.com.au \
--cc=priyanka.jain@nxp.com \
--cc=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.