From: Marco Felsch <m.felsch@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 2/8] FIT: skip possible overlay config nodes
Date: Fri, 22 Mar 2024 17:49:47 +0100 [thread overview]
Message-ID: <20240322164953.1772129-2-m.felsch@pengutronix.de> (raw)
In-Reply-To: <20240322164953.1772129-1-m.felsch@pengutronix.de>
The FIT spec is not very specific when it comes to device-tree overlay
handling. Overlays can be added directely to an config node:
config-a {
compatible = "machine-compatible";
kernel = "kernel-img-name";
fdt = "fdt-base-name", "fdt-overlay1-name", "...";
}
or they are supplied via dedicated config nodes:
overlay-2 {
fdt = "fdt-overlay2-name";
}
Of course these config nodes can have compatibles as well:
overlay-3 {
compatible = "machine-compatible";
fdt = "fdt-overlay3-name";
}
The current fit_find_compatible_unit() code would skip the overlay node
if the config-a compatible has the same score as the overlay-3
compatible and if the overlay-3 config-node is listed after the config-a
config-node. But if the compatible of config-a config-node has a lower
score or the overlay-3 config-note is listed first (the spec does not
specify any order) we end up in taking the overlay-3 config-node instead
of config-a config-node.
Make to code more robust by skip all config nodes matching the pattern
from global.of.overlay.fitconfigpattern.
Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
---
common/image-fit.c | 26 +++++++++++++++++++++++++-
1 file changed, 25 insertions(+), 1 deletion(-)
diff --git a/common/image-fit.c b/common/image-fit.c
index b16752de05bc..bf1562315b40 100644
--- a/common/image-fit.c
+++ b/common/image-fit.c
@@ -7,6 +7,7 @@
#define pr_fmt(fmt) "FIT: " fmt
#include <common.h>
+#include <environment.h>
#include <init.h>
#include <bootm.h>
#include <libfile.h>
@@ -14,6 +15,7 @@
#include <digest.h>
#include <of.h>
#include <fs.h>
+#include <fnmatch.h>
#include <malloc.h>
#include <linux/ctype.h>
#include <asm/byteorder.h>
@@ -715,6 +717,23 @@ static int fit_config_verify_signature(struct fit_handle *handle, struct device_
return ret;
}
+static bool fit_config_is_overlay(struct device_node *conf_node)
+{
+ const char *overlay_pattern;
+ int no_match;
+
+ if (!IS_ENABLED(CONFIG_OF_OVERLAY))
+ return false;
+
+ overlay_pattern = getenv_nonempty("global.of.overlay.fitconfigpattern");
+ if (!overlay_pattern)
+ return false;
+
+ no_match = fnmatch(overlay_pattern, conf_node->name, 0);
+
+ return no_match ? false : true;
+}
+
static int fit_find_compatible_unit(struct device_node *conf_node,
const char **unit)
{
@@ -733,7 +752,12 @@ static int fit_find_compatible_unit(struct device_node *conf_node,
return -ENOENT;
for_each_child_of_node(conf_node, child) {
- int score = of_device_is_compatible(child, machine);
+ int score;
+
+ if (fit_config_is_overlay(child))
+ continue;
+
+ score = of_device_is_compatible(child, machine);
if (score > best_score) {
best_score = score;
*unit = child->name;
--
2.39.2
next prev parent reply other threads:[~2024-03-22 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 16:49 [PATCH 1/8] of: overlay: add of.overlay.fitconfigpattern param Marco Felsch
2024-03-22 16:49 ` Marco Felsch [this message]
2024-03-25 8:27 ` [PATCH 2/8] FIT: skip possible overlay config nodes Sascha Hauer
2024-06-11 8:36 ` Marco Felsch
2024-06-17 8:04 ` Sascha Hauer
2024-06-26 10:04 ` Marco Felsch
2024-07-01 12:06 ` Sascha Hauer
2024-03-22 16:49 ` [PATCH 3/8] of: overlay: make the pattern match function more generic Marco Felsch
2024-03-22 16:49 ` [PATCH 4/8] of: overlay: make search dir/path " Marco Felsch
2024-03-22 16:49 ` [PATCH 5/8] FIT: expose useful helpers Marco Felsch
2024-03-22 16:49 ` [PATCH 6/8] of: overlay: add FIT overlay support Marco Felsch
2024-03-25 8:51 ` Sascha Hauer
2024-06-11 9:09 ` Marco Felsch
2024-03-22 16:49 ` [PATCH 7/8] of: overlay: drop unnecessary empty check in of_overlay_global_fixup_dir Marco Felsch
2024-03-22 16:49 ` [PATCH 8/8] of: overlay: replace filename with an more unique name 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=20240322164953.1772129-2-m.felsch@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=barebox@lists.infradead.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