From: Sascha Hauer <s.hauer@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 2/3] bootsource: add function to get device_node we booted from
Date: Mon, 19 Feb 2024 16:21:07 +0100 [thread overview]
Message-ID: <ZdNx4yaum8DXpMAZ@pengutronix.de> (raw)
In-Reply-To: <20240219145936.uiwy7frsbk4grtcy@pengutronix.de>
On Mon, Feb 19, 2024 at 03:59:36PM +0100, Marco Felsch wrote:
> On 24-02-19, Sascha Hauer wrote:
> > We have a relation between the bootsource and the corresponding
> > device_node. Add a function to get the device_node we booted from.
> > This is already open coded in of_fixup_bootargs_bootsource(),
> > use the newly created function for it.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > ---
> > common/bootsource.c | 14 ++++++++++++++
> > common/oftree.c | 7 +------
> > include/bootsource.h | 1 +
> > 3 files changed, 16 insertions(+), 6 deletions(-)
> >
> > diff --git a/common/bootsource.c b/common/bootsource.c
> > index da528a5b9b..5666d8d30d 100644
> > --- a/common/bootsource.c
> > +++ b/common/bootsource.c
> > @@ -108,6 +108,20 @@ char *bootsource_get_alias_name(void)
> > return basprintf("%s%d", stem, bootsource_instance);
> > }
> >
> > +struct device_node *bootsource_of_node_get(struct device_node *root)
> > +{
> > + struct device_node *np;
> > + char *alias_name;
> > +
> > + alias_name = bootsource_get_alias_name();
>
> if (!alias_name) {
> pr_warn("No alias found for bootsource\n");
> return 0;
> }
I'll have to look over this. With this we assume that for example the
mmcx alias really matches bootsource instance x. This is not the case,
instead we have to look for an alias named "barebox,bootsource-%s%u".
This alias doesn't exist for the majority of platforms, so when we
issue a warning here it would be seen on most boards.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-02-19 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 14:51 [PATCH 0/3] use environment partitions in GPT Sascha Hauer
2024-02-19 14:51 ` [PATCH 1/3] partitions: efi: Allow to create barebox environment partition Sascha Hauer
2024-02-19 15:20 ` Ahmad Fatoum
2024-02-20 10:52 ` Sascha Hauer
2024-02-19 14:51 ` [PATCH 2/3] bootsource: add function to get device_node we booted from Sascha Hauer
2024-02-19 14:59 ` Marco Felsch
2024-02-19 15:21 ` Sascha Hauer [this message]
2024-02-20 10:56 ` Sascha Hauer
2024-02-19 14:51 ` [PATCH 3/3] environment: use barebox environment from GPT partitions Sascha Hauer
2024-02-19 15:06 ` [PATCH 0/3] use environment partitions in GPT Marco Felsch
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=ZdNx4yaum8DXpMAZ@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@pengutronix.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