Re: [PATCH v2 0/2] clk: ti: mux: resolve parent clocks by DT index, not by name

[Andreas Kemnade <andreas@kemnade.info>]

Hi,

this seems to produce on OMAP3 (DM3730), even with the init fix.

[    0.000000] clocksource: 32k_counter: mask: 0xffffffff max_cycles: 0xffffffff
, max_idle_ns: 58327039986419 ns                                                
[    0.000030] sched_clock: 32 bits at 33kHz, resolution 30517ns, wraps every 65
535999984741ns                                                                  
[    0.013488] clk: failed to reparent gpt1_fck to omap_32k_fck: -22            
[    0.019805] Failed to initialize '/ocp@68000000/target-module@48318000/timer@
0': -19                                                                         

Regards,
Andreas

On Mon, 27 Jul 2026 09:41:39 +0200
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> wrote:

> This commit aims to solve an issue I've been describing a few months ago
> on AM335x SoC [1]. I believe using the parent_data field of
> clk_init_data structure is now the preferred way to convey that data,
> and it should be more reliable than string comparisons.
> 
> [1]: https://lore.kernel.org/all/DI4RUFQNSSNP.2QMSSQWJW9I2O@bootlin.com/
> 
> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
> ---
> Changes in v2:
> - Also use clk_parent_data structure in composite.c.
> - Rebase on v7.2-rc5.
> - Link to v1: https://lore.kernel.org/r/20260715-mathieu-wdt-clock-theo-v1-1-da65bba1828b@bootlin.com
> 
> ---
> Mathieu Dubois-Briand (2):
>       clk: ti: mux: resolve parent clocks by DT index, not by name
>       clk: ti: composite: resolve parent clocks by DT index, not by name
> 
>  drivers/clk/ti/composite.c | 26 ++++++++++++++------------
>  drivers/clk/ti/mux.c       | 20 +++++++++++---------
>  2 files changed, 25 insertions(+), 21 deletions(-)
> ---
> base-commit: f5098b6bae761e346ebcd9da7f95622c04733cff
> change-id: 20260713-mathieu-wdt-clock-theo-f0c5ba58e258
> 
> Best regards,