Hi,
this series add the support to load FIT image supplied devicetree overlays.
The v1 of this series can be found here [1].
The overlay loading wasn't coupled to bootm due to the following
reasons:
- By making use of the common overlay handling we can specifiy a
different/separate FIT image which provides only overlays.
- It should be possible to apply FIT image overlay to the barebox
live-tree (not implemented yet).
- Loading a single overlay takes ~20ms (depending on the overlay size)
if the same FIT image is used to supply the kernel, initrd,
devicetree and devicetree-overlays. This is an improvement compared to
the v1 of this series which required ~1sec.
Regards,
Marco
Signed-off-by: Marco Felsch <m.felsch@xxxxxxxxxxxxxx>
---
Changes in v3:
- Link to v2: https://lore.barebox.org/barebox/20240613125818.30499-1-m.felsch@xxxxxxxxxxxxxx/
- drop of.overlay.fitconfigpattern usage and make use of an match-fn
instead
- fit_get_handle(): make use of strcmp
- open_fits: make it static
- fit_close(): use free unconditional
Changes in v2:
- Link to v1: https://lore.pengutronix.de/barebox/20240322164953.1772129-1-m.felsch@xxxxxxxxxxxxxx/
- add caching
---
Marco Felsch (10):
FIT: fix missing free in fit_open error path
FIT: fit_open_configuration: add match function support
of: overlay: make the pattern match function more generic
of: overlay: make search dir/path more generic
FIT: expose useful helpers
of: overlay: add FIT overlay support
of: overlay: drop unnecessary empty check in of_overlay_global_fixup_dir
of: overlay: replace filename with an more unique name
FIT: save filename during fit_open
FIT: add support to cache opened fit images
arch/arm/mach-layerscape/ppa.c | 2 +-
common/bootm.c | 13 ++-
common/image-fit.c | 57 +++++++++--
drivers/of/overlay.c | 222 +++++++++++++++++++++++++++++++++--------
include/image-fit.h | 10 +-
include/of.h | 3 +-
6 files changed, 255 insertions(+), 52 deletions(-)
---
base-commit: bafdf4b35d777d159ac4058efc86d36622ce5ccf
change-id: 20240703-v2024-05-0-topic-fit-overlay-76d5176c1d4e
Best regards,
--
Marco Felsch <m.felsch@xxxxxxxxxxxxxx>
