u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Michal Simek <michal.simek@amd.com>,
	Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] fdt_support: add optional board_rng_seed() hook
Date: Tue, 23 Aug 2022 07:35:46 -0700	[thread overview]
Message-ID: <CAPnjgZ2Xm=Y+e2agPj5v-07rSkXaef0G5gn2Tw4+fJrx=dp1WA@mail.gmail.com> (raw)
In-Reply-To: <4557fbd0-812c-27eb-78b3-b8fc6a1201a8@prevas.dk>

Hi Rasmus,

On Tue, 23 Aug 2022 at 07:06, Rasmus Villemoes
<rasmus.villemoes@prevas.dk> wrote:
>
> On 23/08/2022 15.38, Simon Glass wrote:
>
> >> +/**
> >> + * board_rng_seed() - Provide a seed to be passed via /chosen/rng-seed
> >> + *
> >> + * This function is called if CONFIG_BOARD_RNG_SEED is set, and must
> >> + * be provided by the board. It should return, via @buf, some suitable
> >> + * seed value to pass to the kernel.
> >> + *
> >> + * @param buf         A struct abuf for returning the seed and its size.
> >> + * @return            0 if ok, negative on error.
> >> + */
> >> +int board_rng_seed(struct abuf *buf);
> >
> > Instead of yet another hook, can we use EVT_FT_FIXUP? An even better
> > option might be to use EVT_FT_FIXUP and then call a UCLASS_BOARD
> > method to obtain the information.
>
> I didn't know there was anything called EVT_FT_FIXUP, and from grepping,
> it seems suffer the same problem as ft_board_setup() as I mention,
> namely running after the command line (aka /chosen/bootargs) has been
> set up.

If that is the only problem, then you could add another event for
doing an earlier fixup.

>
> Also, I can't see how it can actually affect the blob being passed to
> the kernel, doesn't
>
>                 fixup.tree = oftree_default();
>                 ret = event_notify(EVT_FT_FIXUP, &fixup, sizeof(fixup));
>
> mean that fixup.tree points at U-Boot's control fdt rather than the blob
> that will be passed as the kernel's fdt? That seems wrong.

Yes that is wrong for many platforms. We should probably just change
it, but there is a complication.

My recent series made a start at supporting writing to a DT using the
ofnode interface. See vbe_simple_test_base() for some comments on the
current state. You could require OF_LIVE to be enabled for your new
feature.

Ideally I'd like to see ofnode used for all devicetree access, but it
will need to be done in stages. In the meantime we should try to head
in that direction.

Regards,
Simon

  reply	other threads:[~2022-08-23 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  7:34 [PATCH] fdt_support: add optional board_rng_seed() hook Rasmus Villemoes
2022-08-23 13:38 ` Simon Glass
2022-08-23 14:06   ` Rasmus Villemoes
2022-08-23 14:35     ` Simon Glass [this message]
2022-08-24  6:57       ` Rasmus Villemoes
2022-08-25  1:25         ` Simon Glass
2022-08-28  1:52           ` Simon Glass
2022-09-01 23:52             ` Simon Glass
2022-09-02  7:00               ` Rasmus Villemoes
2022-09-02 19:59                 ` Simon Glass
2022-09-05 13:03                   ` Rasmus Villemoes
2022-09-12 16:48                   ` Simon Glass

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='CAPnjgZ2Xm=Y+e2agPj5v-07rSkXaef0G5gn2Tw4+fJrx=dp1WA@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=michal.simek@amd.com \
    --cc=rasmus.villemoes@prevas.dk \
    --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 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).