Commit fdb1bffe2827 ("clk: scmi: Postpone clock name resolution")
is breaking boot for STM32MP1/STM32MP2 family board.The issue is due to registering clock with default name "scmi-%zu". If one of these clocks has children clocks, it will generate an error when trying to register their child's clocks as shown below: ... clk_register: failed to get ck_axi device (parent of qspi_k) clk_register: failed to get pll4_p device (parent of spi2_k) clk_register: failed to get pll4_p device (parent of spi3_k) clk_register: failed to get ck_hsi device (parent of usart3_k) clk_register: failed to get ck_hsi device (parent of uart5_k) clk_register: failed to get ck_hsi device (parent of uart7_k) ... Update clock management for STM32MP13 and STM32MP2 SoCs family to resolve SCMI clock's name before using them. Patch based on https://lore.kernel.org/u-boot/[email protected]/ Signed-off-by: Patrice Chotard <[email protected]> --- Patrice Chotard (3): clk: stm32mp13: Reorder include files clk: stm322mp13: Resolve scmi clk before using it clk: stm322mp25: Resolve scmi clk before using it drivers/clk/stm32/clk-stm32mp13.c | 71 +++++++++++++++---- drivers/clk/stm32/clk-stm32mp25.c | 139 ++++++++++++++++++++++++++++++++++++++ 2 files changed, 197 insertions(+), 13 deletions(-) --- base-commit: 7cf578e1b57a39522cffa27b6e9096f8092e164c change-id: 20251211-restore_boot_for_stm32mp13_stm32mp25_boards_v2-e7497f503414 Best regards, -- Patrice Chotard <[email protected]>
