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,
-- 
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>