Re: [PATCH] clk: ti: composite: resolve parent clocks by name again

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

On Fri Sep 4, 2026 at 8:17 PM CEST, Andreas Kemnade wrote:
> Trying to resolve them by DT index causes massive havoc on OMAP3, Clocks
> around the timers used as a system clocksource are not properly resolved
> causing ealy boot failures. The problem seems to be that parents must be
> resolved by looking into the clocks property of the component node marked
> with "ti,composite-mux-clock", with the switch to dt index, that node
> was not used anymore. It was used by the of_clk_parent_fill() call.
> To a lesser extent also OMAP4/5 boards are affected.
>
> Since this patch was introduced just because of a cleanup request
> and not to solve the actual problem
> (https://lore.kernel.org/linux-omap/alkZmw-XmnCOZfOD@redhat.com/)
> just revert it. Cleanup needs really more thought here.
> The similar change to the TI mux clock, which solves a problem on the AM3
> platform, seems to be harmless.
>
> So just revert
> commit fe3dd92ac54a ("clk: ti: composite: resolve parent clocks by DT index, not by name")
> for now.
>
> Fixes: fe3dd92ac54a ("clk: ti: composite: resolve parent clocks by DT index, not by name")
> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> ---

Hi Andreas,

Thanks for your time and testing it this way.

Reviewed-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com