[PATCH V2] ARM: i.MX5: Allow DT clock providers
Martin Fuzzey
mfuzzey at parkeon.com
Thu Apr 18 04:36:53 EDT 2013
On 18/04/13 08:30, Shawn Guo wrote:
> +static struct clk * __init mx5_obtain_fixed_clock_from_dt(const char *name)
> +{
> +#ifdef CONFIG_OF
> We have selected USE_OF at the sub-architecture level, so the ifdef
> plays nothing here.
Ah ok so what happens on non DT platforms (looks like Babbage)
Does this mean that there is an empty DT in that case?
I was going by the existing code which already has this #ifdef
>> + struct of_phandle_args phandle = {0};
>> + struct clk *clk = ERR_PTR(-ENODEV);
>> + char *compatible;
>> +
>> + compatible = kasprintf(GFP_KERNEL, "fsl,imx-%s", name);
> What about finding the node by path as below?
>
> path = kasprintf(GFP_KERNEL, "/clocks/%s", name);
> phandle.np = of_find_node_by_path(path);
>
> I have to admit that those imx custom compatibles for fixed-clock
> shouldn't necessarily be there at all. Let's stop spreading the use.
I can't find anything in the DT binding documentation that says the
clocks have to be
under /clocks (but then again the fsl,imx- compatible string isn't
documented either).
My understanding of DT is that the absolute node path is generally
unimportant with
the exception of a few special nodes like /, /memory, /chosen
But I don't have a strong opinion on this - if the consensus is that
path based lookup
is better I'll do that.
Regards,
Martin
More information about the linux-arm-kernel
mailing list