mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 0/4] of: fdt: read blspec/FIT DT compat without unflattening
Date: Fri,  1 Mar 2024 14:04:41 +0100	[thread overview]
Message-ID: <20240301130445.171385-1-a.fatoum@pengutronix.de> (raw)

blspec and FIT systems usually have multiple entries/configurations,
where a suitable one should be selected at runtime by comparing each
against the board's barebox DT compatible.

For blspec, this meant we need to unflatten the whole DT only to access
a single property. For FIT, this meant we expected the configuration to
carry a "compatible" property and didn't even attempt to parse it out of
the fdt as fallback. Both are resolved with this series.

Ahmad Fatoum (4):
  of: fdt: factor out FDT header parsing
  of: fdt: implement fdt_machine_is_compatible
  blspec: don't parse whole device tree to compare compatibles
  FIT: support finding compatible configuration by FDT compatible

 common/blspec.c    |  16 ++---
 common/image-fit.c |  39 ++++++++++-
 drivers/of/fdt.c   | 171 ++++++++++++++++++++++++++++++++++++---------
 include/of.h       |   8 +++
 4 files changed, 191 insertions(+), 43 deletions(-)

-- 
2.39.2




             reply	other threads:[~2024-03-01 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 13:04 Ahmad Fatoum [this message]
2024-03-01 13:04 ` [PATCH 1/4] of: fdt: factor out FDT header parsing Ahmad Fatoum
2024-03-01 13:04 ` [PATCH 2/4] of: fdt: implement fdt_machine_is_compatible Ahmad Fatoum
2024-03-04  9:37   ` Sascha Hauer
2024-03-04  9:49     ` Sascha Hauer
2024-03-04  9:50     ` Ahmad Fatoum
2024-03-01 13:04 ` [PATCH 3/4] blspec: don't parse whole device tree to compare compatibles Ahmad Fatoum
2024-03-01 13:04 ` [PATCH 4/4] FIT: support finding compatible configuration by FDT compatible Ahmad Fatoum
2024-03-04  9:49 ` [PATCH 0/4] of: fdt: read blspec/FIT DT compat without unflattening 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=20240301130445.171385-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@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