Re: [RFC PATCH 1/2 v1] arch: arm: Kconfig: Add config to use subnode's bootph property for binding drivers

[Moteen Shah <m-shah@ti.com>]

Hey Udit,

On 12/02/25 20:19, Kumar, Udit wrote:
>
> On 2/12/2025 2:48 PM, Moteen Shah 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-shah@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
>
> Why config, this fix looks to be valid for all configs ?
True, but for vendors having a fixed up DT and have constraints for faster
boot times, this fix will add up overheads of traversing all of the nodes.

Regards,
Moteen
>
>
>>       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
>> +    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"