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

[Quentin Schulz]

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.

[1] https://fitspec.osfw.foundation/#optional-properties compatible paragraph
[2] https://fitspec.osfw.foundation/#select-a-configuration-to-boot

Signed-off-by: Quentin Schulz <quentin.schulz at cherry.de>
---
Quentin Schulz (4):
      boot/fit: use constants for property strings
      lib: rsa: use FIT_ALGO_PROP constant instead of "algo" in FIT
      boot/fit: declare (and use) new constant for conf's compatible prop
      boot/fit: print all configuration node compatibles

 boot/common_fit.c    |  4 ++--
 boot/image-fit.c     | 15 +++++++++++++--
 include/image.h      |  1 +
 lib/rsa/rsa-verify.c |  2 +-
 4 files changed, 17 insertions(+), 5 deletions(-)
---
base-commit: 341cafc31e4c6941a1b05feb18d18c99ffaebcc1
change-id: 20250409-fit-compat-ebe94f690b08

Best regards,
-- 
Quentin Schulz <quentin.schulz at cherry.de>