Re: Two-output clk provider with standard clk consumer

[Mason <slash.tmp@free.fr>]

On 15/10/2015 14:09, Michael Turquette wrote:

> Regarding the reliance on string names when clock-output-names is not
> used, that is an on-going discussion[0] affecting multiple drivers right
> now. We're trying to find a long-term solution that moves away from
> string names and uses the DT hierarchy to establish parent-child
> relationships.

Thanks for your help!

The important thing I was missing is that of_clk_get_parent_name()
actually looks up the parent's "clock-output-names" property.

  if (of_property_read_string_index(clkspec.np, "clock-output-names", index, &clk_name) < 0)
    clk_name = clkspec.np->name;

but since I had "hardcoded" the clock names, the parent didn't
have a "clock-output-names" property.

Regards.