[PATCH v2 2/3] clk: stm322mp13: Resolve scmi clk before using it
Marek Vasut
marek.vasut at mailbox.org
Fri Dec 12 16:36:48 CET 2025
On 12/11/25 4:52 PM, Patrice Chotard wrote:
> During clock's registration, clock's name are used to establish parent -
> child relation. On STM32MP13, most of SCMI clocks are parent
> clocks.
>
> Since commit fdb1bffe2827 ("clk: scmi: Postpone clock name resolution"),
> all scmi clocks are named by default "scmi-%zu" until they are enabled,
> it breaks clocks registration and boot process for STM32MP13 platforms.
>
> By resolving SCMI clocks before clocks registration, it solves the issue.
>
> Fixes: fdb1bffe2827 ("clk: scmi: Postpone clock name resolution")
> Signed-off-by: Patrice Chotard <patrice.chotard at foss.st.com>
Shouldn't the relationship between RCC and SCMI clock be described in DT
using "clock" property and phandles / clock cells ? Once that is in
place, you should be able to resolve the parent clock using that
relationship described in DT, without the need to explicitly do these
SCMI calls in RCC driver.
More information about the U-Boot
mailing list