Hi Moteen, On Wed, 12 Feb 2025 at 02:18, Moteen Shah <m-s...@ti.com> wrote: > > Add a new config when set will traverse through all the subnodes of > a given node scanning for bootph-all property and propagate it to > all of its parent node up the hierarchy. > > Signed-off-by: Moteen Shah <m-s...@ti.com> > --- > arch/arm/Kconfig | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig > index 314916527c9..51fc952b0db 100644 > --- a/arch/arm/Kconfig > +++ b/arch/arm/Kconfig > @@ -805,6 +805,7 @@ config ARCH_K3 > select FIT > select REGEX > select FIT_SIGNATURE if ARM64 > + imply BIND_FROM_CHILD_BOOTPH > imply TI_SECURE_DEVICE > > config ARCH_OMAP2PLUS > @@ -2232,6 +2233,16 @@ config SYS_KWD_CONFIG > Path within the source directory to the kwbimage.cfg file to use > when packaging the U-Boot image for use. > > + > +config BIND_FROM_CHILD_BOOTPH
How about DM_F_STRICT_BOOTPH ? or DM_F_CHILD_BOOTPH ? It indicates that it relates to driver model before relocation. This behaviour is actually required by the schema. I agree it should be optional, but only due to its performance issues. A Binman solution would not have any performance issues. > + bool "Bind drivers from bootph* in subnode" > + depends on ARCH_K3 > + help > + This config must be set to bind drivers in pre reloc stage whose > + compatible parent nodes are implicitly declared to be bound to > + their respective drivers by having bootph* property in one of > + their subnodes. > + > source "arch/arm/mach-apple/Kconfig" > > source "arch/arm/mach-aspeed/Kconfig" > -- > 2.34.1 > Regards, Simon
