Hi Magnus,
On Wed, Sep 9, 2015 at 7:05 AM, Magnus Damm <[email protected]> wrote:
> From: Magnus Damm <[email protected]>
>
> This patch hacks the CCF core to take clock-indices into
> consideration when making a default clock name in case
> clock-output-names is not provided.
>
> Without this patch of_clk_get_parent_name() does not work
> for clocks with multiple indices associated with one node.
>
> Proof of concept only. Leaks memory. Not for upstream merge.
>
> Not-Yet-Signed-off-by: Magnus Damm <[email protected]>
While this (probably) solves the issue, is this something we want to do?
What does we gain? E.g. we still need to allocate memory to store the clock
names, so no memory is saved by not providing clock-output-names.
But instead of useful names, the clocks now have autogenerated names, and all
look the same (I don't know e.g. all 384 MSTP clock numbers by heart ;-)
Clocks are too critical to make mistakes, so having useful names matters a lot.
I'm still in favor of keeping clock-output-names for device nodes that
provide multiple clock outputs.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-clk" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
