On Tue, Jan 20, 2026 at 03:07:17AM +0800, Yang Xiwen wrote: > 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. > > Signed-off-by: Yang Xiwen <[email protected]>
This, like some previous clk reworks, leads to run-time breakage (failure to boot) on TI K3 and likely other platforms (I want to say some rockchip was broken last time) as well. -- Tom
signature.asc
Description: PGP signature
