* Mike Turquette <mturquette@xxxxxxxxxx> [130513 16:56]: > Quoting Nishanth Menon (2013-05-08 12:06:11) > <snip> > > Overall strategy introduced here is simple: a clock node described in > > device tree blob is used to identify the exact clock provided in the > > SoC specific data. This is then linked back using of_clk_add_provider > > to the device node to be accessible by of_clk_get. > > > > FYI, I'm working on moving the OMAP clocks over to DT which is a better > alternative than this patch. I'll share what I have on the list, > hopefully next week. That's good news! What's your plan on using the indexing the clocks? I'd rather avoid indexing as that's basically same as the old IRQ numbering and GPIO numbering schemes that don't work well in the long term. We already have quite a few sets of clocks for omaps, so the indexing is already an issue. My thinking is that indexing should only be used if the same physical clock has multiple outputs. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
