Commit 4d11c62ca8d7 ("clkdev: report over-sized strings when creating
clkdev entries") revealed that clock lookup is registered for all fixed
clocks. The mentioned commit added a check if the registered name is not
too long. This fails for some clocks registered for Exynos542x SoCs family.
This lookup is a left-over from early common clock framework days, not
really needed nowadays, so remove it to avoid further issues.
Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
---
Here is the fix for the mentioned 4d11c62ca8d7 commit, which fixes
booting of Exynos542x SoCs:
https://lore.kernel.org/all/20240507064434.3213933-1-m.szyprowski@xxxxxxxxxxx/
This change is independent fix. I've tested it on all Exynos based boards
I have in my test lab. It would be great if someone could test it on
s3c64xx and s3c24xx based boards.
---
drivers/clk/samsung/clk.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/drivers/clk/samsung/clk.c b/drivers/clk/samsung/clk.c
index b6701905f254..6342ff411757 100644
--- a/drivers/clk/samsung/clk.c
+++ b/drivers/clk/samsung/clk.c
@@ -151,15 +151,6 @@ void __init samsung_clk_register_fixed_rate(struct samsung_clk_provider *ctx,
}
samsung_clk_add_lookup(ctx, clk_hw, list->id);
-
- /*
- * Unconditionally add a clock lookup for the fixed rate clocks.
- * There are not many of these on any of Samsung platforms.
- */
- ret = clk_hw_register_clkdev(clk_hw, list->name, NULL);
- if (ret)
- pr_err("%s: failed to register clock lookup for %s",
- __func__, list->name);
}
}
--
2.34.1
