From: Moteen Shah <m-shah@ti.com>
To: <u-boot@lists.denx.de>
Cc: <trini@konsulko.com>, <sjg@chromium.org>, <m-chawdhry@ti.com>,
<n-francis@ti.com>, <vigneshr@ti.com>, <u-kumar1@ti.com>,
<a-chavda@ti.com>, <m-shah@ti.com>
Subject: [RFC PATCH 1/2 v1] arch: arm: Kconfig: Add config to use subnode's bootph property for binding drivers
Date: Wed, 12 Feb 2025 14:48:19 +0530 [thread overview]
Message-ID: <20250212091820.213895-2-m-shah@ti.com> (raw)
In-Reply-To: <20250212091820.213895-1-m-shah@ti.com>
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
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"
--
2.34.1
next prev parent reply other threads:[~2025-02-12 12:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 9:18 [RFC PATCH 0/2 v1] Propagate bootph* property to all parent nodes Moteen Shah
2025-02-12 9:18 ` Moteen Shah [this message]
2025-02-12 14:49 ` [RFC PATCH 1/2 v1] arch: arm: Kconfig: Add config to use subnode's bootph property for binding drivers Kumar, Udit
2025-02-13 4:48 ` Moteen Shah
2025-02-13 14:01 ` Simon Glass
2025-02-14 5:05 ` [EXTERNAL] " Moteen Shah
2025-02-25 21:27 ` Simon Glass
2025-03-07 4:55 ` Moteen Shah
2025-03-27 6:58 ` Moteen Shah
2025-02-12 9:18 ` [RFC PATCH 2/2 v1] drivers: core: lists.c: Bind drivers using bootph* property in subnodes Moteen Shah
2025-02-12 13:37 ` Simon Glass
2025-02-13 13:01 ` [EXTERNAL] " Moteen Shah
2025-02-12 14:59 ` Kumar, Udit
2025-02-17 15:02 ` [RFC PATCH 0/2 v1] Propagate bootph* property to all parent nodes Quentin Schulz
2025-02-26 5:57 ` Moteen Shah
2025-02-26 10:53 ` Quentin Schulz
2025-02-27 16:24 ` Simon Glass
2025-02-28 11:03 ` Quentin Schulz
2025-03-05 14:15 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250212091820.213895-2-m-shah@ti.com \
--to=m-shah@ti.com \
--cc=a-chavda@ti.com \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox