mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org, mtr@pengutronix.de
Subject: Re: [PATCH] state: add deep probe aware helpers to get state
Date: Mon, 7 Feb 2022 10:00:48 +0100	[thread overview]
Message-ID: <20220207090048.GG18637@pengutronix.de> (raw)
In-Reply-To: <20220202111932.1227416-1-a.fatoum@pengutronix.de>

On Wed, Feb 02, 2022 at 12:19:32PM +0100, Ahmad Fatoum wrote:
> state_by_name itself can't be made deep probe aware as it doesn't have
> enough information on what to probe. Board code calling it must instead
> itself ensure that the state has been proved (either via initcall
> ordering or by calling e.g. of_ensure_probed_by_alias). For
> state_by_node we can do it better: We can ensure probe of the supplied
> device node. For most purposes, users just want to probe the default
> state. This can now be done with state_by_alias("state").
> 
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
>  common/state/state.c | 20 +++++++++++++++++++-
>  include/state.h      | 12 +++++++++---
>  2 files changed, 28 insertions(+), 4 deletions(-)

Applied, thanks

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 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


      reply	other threads:[~2022-02-07  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 11:19 Ahmad Fatoum
2022-02-07  9:00 ` Sascha Hauer [this message]

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=20220207090048.GG18637@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=mtr@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