u-boot/u-boot.git, branch DBG/clk-support-arbitrary-clk_register-sequence

Merge patch series "clk: support arbitrary clk_register() sequence"

2026-02-02T19:40:50+00:00

Yang Xiwen says: Currently, the U-Boot clk framework mandates that clock registration begins at the root and proceeds to children. This creates an additional requirement that does not exist in the Linux kernel, making the porting of clk drivers more difficult. This series handles the dependency entirely within the clk framework, allowing drivers the freedom to register clocks in any order. This is achieved by assigning the parent "lazily". The framework caches the parent name in the core clk struct and attempts to resolve the actual parent when clk consumers call clk_get_parent(). The process is transparent to clk consumers as long as they use standard clk framework APIs. I've run `ut dm clk*` and verified these commits do not break any existing test cases. It also passes the new test case. This feature is disabled for xPLs by default. I have not found a clean way to enable this separately for xPLs without introducing a repetitive Kconfig entry (e.g., xPL_CLK_LAZY_REPARENT), which looks very ugly. Link: https://lore.kernel.org/r/20260120-clk-reparent-v3-0-0d43d4b362ac@outlook.com

test: clk: add test for CLK_LAZY_REPARENT

2026-02-02T19:40:41+00:00

Add a test for the newly introduced CLK_LAZY_REPARENT feature. Modify clk_sandbox_ccf driver to register two clocks(i2s and i2s_root) in reversed order. The test function then try to acquire the clocks and asserts that their internal states are maintained correctly. Ensure clk->parent_name is NULL in all "normal" cases so existing drivers are not broken by this feature. Signed-off-by: Yang Xiwen

clk: allow assigning parent lazily

2026-02-02T19:40:41+00:00

Don't mandate the parent device exists when registering a clock. Instead, cache the parent name in the core clk struct and resolve the parent in clk_get_parent(), which is called lazily upon real use. Disable this feature for xPLs by default to save size. Reviewed-by: Simon Glass Signed-off-by: Yang Xiwen

clk: use clk_get_parent() helper in clk_en(dis)able()

2026-02-02T19:40:41+00:00

Update clk_enable() and clk_disable() to use clk_get_parent() instead of manually accessing clk->dev->parent. Reviewed-by: Simon Glass Signed-off-by: Yang Xiwen

clk: add uclass id check to clk_get_parent()

2026-02-02T19:40:41+00:00

Check the uclass id in clk_get_parent() before casting dev->priv to struct clk *. This sanity check can be also found in some other places and should be enforced. Reviewed-by: Simon Glass Signed-off-by: Yang Xiwen

test: dm: core: add some assertions for device_reparent()

2026-02-02T19:40:41+00:00

The original tests only assert the return value of device_reparent(), but does not check the actual relation between the new parent and the child. Add some assertions to check this behavior. It also lacks the logic to test orphan/root devices. Add tests for that. Signed-off-by: Yang Xiwen

drivers: core: device: set new parent when old parent is NULL

2026-02-02T19:40:41+00:00

The current logic does not update the new parent in device_reparent() if old parent is NULL. The behavior is not desired. Fix it by setting the parent in this case. Fixes: cfecbaf4e768 ("dm: core: add support for device re-parenting") Signed-off-by: Yang Xiwen

Merge patch series "arm: mach-k3: j721s2: Provide a way to obtain boot device for non SPLs"

2026-02-02T19:39:52+00:00

This series from Dominik Haller provides a way for TI K3 platforms to determine their boot device outside of SPL and then adds support for the PHYTEC phyCORE-AM68x/TDA4x SoM. Link: https://lore.kernel.org/r/20260116014116.767555-1-d.haller@phytec.de

doc: board: phytec: Add phyCORE-AM68x/TDA4x

2026-02-02T19:39:42+00:00

Add documentation for the PHYTEC phyCORE-AM68x/TDA4x (J721S2 family) SoM. Signed-off-by: Dominik Haller Reviewed-by: Wadim Egorov

board: phytec: Add PHYTEC phyCORE-AM68x/TDA4x SoM

2026-02-02T19:39:42+00:00

Add support for the PHYTEC phyCORE-AM68x/TDA4x (J721S2 family) SoM. Supported features: - 4GB LPDDR4 RAM - eMMC - SD-Card - Ethernet - OSPI - AVS - debug UART Signed-off-by: Dominik Haller Reviewed-by: Wadim Egorov