[PATCH RFC 0/4] fit: print conf node compatibles + use property string constants

[Tom Rini]

On Wed, Dec 03, 2025 at 01:21:35PM +0100, Quentin Schulz wrote:
> Hi all,
> 
> On 4/9/25 5:10 PM, Quentin Schulz wrote:
> > This does a bit of "cleanup" by reusing constants for some FIT
> > properties instead of having the same string in multiple places.
> > 
> > Additionally, this adds a new constant for the compatible property in
> > FIT configuration nodes[1] which is useful for FIT images with multiple
> > FIT configuration nodes to support multiple devices in the same blob.
> > U-Boot will try to figure out which node to select based on that
> > compatible[2].
> > 
> > However, if this property is missing (and the first blob in the fdt
> > property of the configuration node is uncompressed), the compatible from
> > the root node of the associated kernel FDT will be used for the
> > autoselection mechanism. For now, I only print the property if it
> > exists, but maybe it'd make sense to expose the fallback one if it's
> > missing, hence the RFC state for this series.
> > 
> 
> Any feedback on this series?
> 
> It doesn't apply cleanly anymore but the conflict resolution is
> straightforward.

I probably marked it as RFC in patchwork. So, how about v1 non-RFC
rebased on top of next? Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20251203/89e28c23/attachment.sig>