mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: fpg@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH v2 1/4] efi: payload: ignore ESP state.dtb if device tree is populated
Date: Thu, 15 Oct 2026 11:23:27 +0200	[thread overview]
Message-ID: <20261015092554.210438-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20261015092554.210438-1-a.fatoum@pengutronix.de>

In preparation for allowing the state nodes to ship inside the barebox
binary (as we do for non-EFI-payload already), add provisions to skip
the external file if barebox already has a populated DT.

Do the check before looking at the ESP, so a system with a built-in
state doesn't log that it was unable to read state.dtb. We only warn
if the file exists and is ignored.

Also for the case that a state had already been set up, skip manual
creation of the state node.

Assisted-by: Claude:opus-5
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 efi/payload/init.c | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/efi/payload/init.c b/efi/payload/init.c
index 1e5f2eb8cf56..a79f51ea38fc 100644
--- a/efi/payload/init.c
+++ b/efi/payload/init.c
@@ -284,6 +284,7 @@ static int efi_late_init(void)
 {
 	const char *state_desc = "/boot/EFI/barebox/state.dtb";
 	struct device_node *state_root = NULL;
+	struct device_node *root;
 	size_t size;
 	void *fdt;
 	int ret;
@@ -291,6 +292,19 @@ static int efi_late_init(void)
 	if (!IS_ENABLED(CONFIG_STATE))
 		return 0;
 
+	/*
+	 * A device tree built into barebox takes precedence: any state it
+	 * describes has been instantiated by the state driver already.
+	 */
+	root = of_get_root_node();
+	if (root && !list_empty(&root->children)) {
+		struct stat s;
+
+		if (!stat(state_desc, &s))
+			pr_warn("device tree is populated, ignoring %s\n", state_desc);
+		return 0;
+	}
+
 	if (!get_mounted_path("/boot")) {
 		pr_warn("boot device couldn't be determined%s\n",
 			IS_ENABLED(CONFIG_FS_EFI) ? "" : " without CONFIG_FS_EFI");
@@ -320,6 +334,10 @@ static int efi_late_init(void)
 			return 0;
 		}
 
+		/* probing the registered tree may have instantiated it already */
+		if (state_by_node(np))
+			return 0;
+
 		state = state_new_from_node(np, false);
 		if (IS_ERR(state))
 			return PTR_ERR(state);
-- 
2.47.3




  reply	other threads:[~2026-10-15  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  9:23 [PATCH v2 0/4] efi: payload: allow extension via fragments Ahmad Fatoum
2026-10-15  9:23 ` Ahmad Fatoum [this message]
2026-10-15  9:23 ` [PATCH v2 2/4] kbuild: dtc: introduce empty fallback device tree Ahmad Fatoum
2026-10-15  9:23 ` [PATCH v2 3/4] efi: payload: export device tree in barebox-dtb EFI variable Ahmad Fatoum
2026-10-15  9:23 ` [PATCH v2 4/4] Documentation: efi: describe device tree handling Ahmad Fatoum
2026-10-15 13:07 ` [PATCH v2 0/4] efi: payload: allow extension via fragments Sascha Hauer

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=20261015092554.210438-2-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=fpg@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