From: Herve Codina <herve.codina@bootlin.com>
To: Simon Glass <sjg@chromium.org>
Cc: Devicetree Compiler <devicetree-compiler@vger.kernel.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v2 07/15] dtc: Move label-reference handling out of the grammar
Date: Thu, 5 Nov 2026 10:07:14 +0100 [thread overview]
Message-ID: <20261105100714.47bf0434@bootlin.com> (raw)
In-Reply-To: <20261104211807.972610-8-sjg@chromium.org>
Hi David, Simon,
On Wed, 4 Nov 2026 14:17:46 -0700
Simon Glass <sjg@chromium.org> wrote:
> The grammar action for a top-level &label { ... } holds its merge logic,
> including making an overlay fragment in a plugin when the label is not
> found.
>
> Move it into a new merge_ref(), passing it a struct fragment for the
> reference and node.
>
> The output does not change.
>
> Assisted-by: Claude:claude-opus-5-5
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> Changes in v2:
> - Rename merge_label_ref() to merge_ref()
> - Build the fragment in one step, with build_fragment_ref()
> - Return true on success from merge_ref()
> - Check the fragment type with assert()
>
> dtc-parser.y | 23 +++++++++--------------
> dtc.h | 1 +
> livetree.c | 26 ++++++++++++++++++++++++++
> 3 files changed, 36 insertions(+), 14 deletions(-)
>
> diff --git a/dtc-parser.y b/dtc-parser.y
> index 9b9b6db..c58a66d 100644
> --- a/dtc-parser.y
> +++ b/dtc-parser.y
> @@ -214,21 +214,16 @@ devicetree:
> }
> | devicetree DT_LABEL_REF nodedef
> {
> - struct node *target = get_node_by_ref($1, $2);
> + struct fragment *f;
>
> - if (target) {
> - merge_nodes(target, $3);
> - } else {
> - /*
> - * We rely on the rule being always:
> - * versioninfo plugindecl memreserves devicetree
> - * so $-1 is what we want (plugindecl)
> - */
> - if ($<flags>-1 & DTSF_PLUGIN)
> - add_orphan_node($1, $3, $2);
> - else
> - ERROR(&@2, "Label or path %s not found", $2);
> - }
> + f = build_fragment_ref(NULL, NULL, $2, &@2, $3);
> + /*
> + * We rely on the rule being always:
> + * versioninfo plugindecl memreserves devicetree
> + * so $-1 is what we want (plugindecl)
> + */
> + if (!merge_ref($1, f, $<flags>-1 & DTSF_PLUGIN))
> + treesource_error = true;
> $$ = $1;
> }
> | devicetree DT_DEL_NODE dt_ref ';'
> diff --git a/dtc.h b/dtc.h
> index 8c4d7bf..9b4389b 100644
> --- a/dtc.h
> +++ b/dtc.h
> @@ -373,6 +373,7 @@ struct fragment *build_fragment_omit_if_no_ref(char *ref,
> struct fragment *append_fragment(struct fragment *list, struct fragment *new);
> void free_fragment(struct fragment *f);
> bool is_ref_relative(const char *ref);
> +bool merge_ref(struct node *dt, struct fragment *f, bool plugin);
> bool merge_delete_node(struct node *dt, struct fragment *f);
> bool merge_omit_if_no_ref(struct node *dt, struct fragment *f);
>
> diff --git a/livetree.c b/livetree.c
> index 3ff4e14..179866d 100644
> --- a/livetree.c
> +++ b/livetree.c
> @@ -573,6 +573,32 @@ bool is_ref_relative(const char *ref)
> return ref[0] != '/' && strchr(&ref[1], '/');
> }
>
> +/*
> + * Merge a fragment which refers to a label into the node with that label. In
> + * a plugin, a label which is not found becomes an overlay fragment.
> + *
> + * Returns true on success, false on an error, which has been reported.
> + */
> +bool merge_ref(struct node *dt, struct fragment *f, bool plugin)
> +{
> + struct node *target = get_node_by_ref(dt, f->ref);
> +
> + assert(f->type == FRAGMENT_NODE);
> + if (target) {
> + merge_nodes(target, f->node);
> + return true;
> + }
> + if (!plugin) {
> + srcpos_error(f->ref_srcpos, "Error",
> + "Label or path %s not found", f->ref);
> + return false;
> + }
> + /* The label may be in the base tree, so add a fragment@N node for it */
> + add_orphan_node(dt, f->node, f->ref);
> +
> + return true;
> +}
> +
Even if this function is slightly modified in later patches, I think it mixes
two different operations:
- Merging fragments
- Converting fragments in overlay output format.
IHMO, those two operations should be fully decoupled.
merge_ref() or any other operation whose goal is to merge a fragment should
only merge fragment either in the existing root node or in a previous fragment
available in the fragment list.
add_orphan_node() should not be called from a merge_*() function related to
fragments.
After merging all fragment we should have a root node and/or a list of fragment
reduced to unmerged ones.
Base on that, the overlay conversion can be performed using a dedicated
function, out of merge_*() functions.
Something like this:
---- 8< ----
void convert_to_overlay_output_format(struct dt_info *dti)
{
struct fragment *f;
if (!dti->dt) {
/* The root node is not present. Create an empty one */
dti->dt = ...;
}
/*
* The fragment list have been previously merged.
* Available fragment left in the list are fragments
* that cannot be merged and so those fragments are
* orphan nodes.
*
* Convert those orphan nodes to the /fragment@N format overlay
* format.
*/
for (f = dti->fragments; f; f = next) {
add_orphan_node(dti->dt, f->node, f->ref);
/* Add __fixups__ and __local_fixups__ nodes ? */
todo();
}
in main():
/* Parse input */
dti = dt_from_*();
checks_pre_fragment_merge(dti);
merge_fragments(dti); /* <--- Fragments are merged.
* Remaining items in the fragment list, if
* any are Orphan nodes (i.e. fragments that
* couldn't be merged).
*/
checks_post_fragment_merge(dti); <--- Orphan ok for overlays but ko for !overlay dts
/* Convert outputs */
if (dti->dtsflags & DTSF_PLUGIN) {
convert_to_overlay_output_format(dti);
checks_overlay_format(dti); /* <--- Not sure it is needed */
}
/* Generate output */
dt_to_*();
}
--- 8< ---
Best regards,
Hervé
next prev parent reply other threads:[~2026-11-05 9:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 21:17 [PATCH v2 00/15] dtc: Merge the fragments of a dts file after parsing Simon Glass
2026-11-04 21:17 ` [PATCH v2 01/15] tests: Check each error when merging a dts file Simon Glass
2026-11-04 21:17 ` [PATCH v2 02/15] srcpos: Allow srcpos_string() to accept NULL Simon Glass
2026-11-04 21:17 ` [PATCH v2 03/15] dtc: Add a struct for the top-level fragments of a dts file Simon Glass
2026-11-04 21:17 ` [PATCH v2 04/15] dtc: Move the /delete-node/ handling out of the grammar Simon Glass
2026-11-04 21:17 ` [PATCH v2 05/15] dtc: Move the /omit-if-no-ref/ " Simon Glass
2026-11-04 21:17 ` [PATCH v2 06/15] dtc: Move is_ref_relative() to livetree.c Simon Glass
2026-11-04 21:17 ` [PATCH v2 07/15] dtc: Move label-reference handling out of the grammar Simon Glass
2026-11-05 9:07 ` Herve Codina [this message]
2026-11-05 21:49 ` Simon Glass
2026-11-06 6:56 ` Herve Codina
2026-11-06 13:05 ` Simon Glass
2026-11-06 15:55 ` Herve Codina
2026-11-06 17:30 ` Simon Glass
2026-11-04 21:17 ` [PATCH v2 08/15] dtc: Merge &{label} in a plugin as with &label Simon Glass
2026-11-04 21:17 ` [PATCH v2 09/15] dtc: Move path-reference handling out of the grammar Simon Glass
2026-11-04 21:17 ` [PATCH v2 10/15] dtc: Move labelled-reference " Simon Glass
2026-11-04 21:17 ` [PATCH v2 11/15] dtc: Move first-reference " Simon Glass
2026-11-04 21:17 ` [PATCH v2 12/15] dtc: Add merge_fragment() to merge any fragment Simon Glass
2026-11-04 21:17 ` [PATCH v2 13/15] dtc: Add helpers for the errors when merging a fragment Simon Glass
2026-11-04 21:17 ` [PATCH v2 14/15] dtc: Merge the fragments of a dts file after parsing Simon Glass
2026-11-04 21:17 ` [PATCH v2 15/15] dtc: Merge the fragments of a dts file in main() 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=20261105100714.47bf0434@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=sjg@chromium.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;
as well as URLs for NNTP newsgroup(s).