linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francesco Valla <francesco@valla.it>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-embedded@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] Add driver for bootstage stash
Date: Fri, 23 May 2025 22:06:31 +0200	[thread overview]
Message-ID: <22690048.4csPzL39Zc@fedora.fritz.box> (raw)
In-Reply-To: <CAMuHMdXqw9igYU-iPFbA-uP8-LrmZocUKT4k9cb8+py1gFp8tA@mail.gmail.com>

Hi Geert,

On Friday, 23 May 2025 at 09:04:48 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >
> > At U-Boot side, following configuration shall then be set:
> >
> >     CONFIG_BOOTSTAGE=y
> >     CONFIG_BOOTSTAGE_STASH_ADDR=0xa4300000
> >     CONFIG_BOOTSTAGE_STASH_SIZE=0x1000
> 
> I think this can be simplified further, using either of these two options:
>   1. If the bootstage@a4300000 node would already be present in the
>      DTB used by U-Boot, the two CONFIG_BOOTSTAGE_STASH_*
>      options would no longer be needed.
>   2. U-Boot could add the bootstage@a4300000 to the DTB that is
>      passed to the kernel, just like it already adds/updates the memory
>      nodes.
> 

The second option is probably the best one, as it aligns with other
similar usecases (e.g.: OP-TEE node [1]). Once it has been determined that
this driver is the right approach, it should be pretty simple to do.

[1] https://elixir.bootlin.com/u-boot/v2025.04/source/lib/optee/optee.c#L112

> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> 

Regards,

Francesco






  reply	other threads:[~2025-05-23 20:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 22:42 [RFC PATCH 0/1] Add driver for bootstage stash Francesco Valla
2025-05-22 22:42 ` [PATCH 1/1] drivers: misc: add " Francesco Valla
2025-05-23  6:29   ` Krzysztof Kozlowski
2025-05-23 19:34     ` Rob Landley
2025-05-24  6:16       ` Krzysztof Kozlowski
2025-05-23 19:43     ` Francesco Valla
2025-05-24  6:15       ` Krzysztof Kozlowski
2025-05-23 23:43   ` Bird, Tim
2025-05-24  7:18   ` kernel test robot
2025-05-23  7:04 ` [RFC PATCH 0/1] Add " Geert Uytterhoeven
2025-05-23 20:06   ` Francesco Valla [this message]
     [not found] ` <PA4PR08MB604681FF6392B25A19926A11ED98A@PA4PR08MB6046.eurprd08.prod.outlook.com>
2025-05-23  7:34   ` Federico Giovanardi
2025-05-23 19:43     ` Rob Landley
2025-05-23 20:11     ` Francesco Valla
2025-05-24  0:07     ` Bird, Tim
2025-05-24  0:28       ` Bird, Tim

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=22690048.4csPzL39Zc@fedora.fritz.box \
    --to=francesco@valla.it \
    --cc=geert@linux-m68k.org \
    --cc=linux-embedded@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).