Hello Tony, On Tue, Mar 10, 2015 at 6:35 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: >> >> we do have to make sure these wl18xx bindings are future-compatible >> with the wl12xx ones, but i think the current bindings are pretty much >> standard (and are actually a subset of the bindings needed by wl12xx), >> so it should be fine. > > Well how about add just the parsing of the clock and assume it's always > WL12XX_REFCLOCK_38 for now as that's the only thing we're currently > using. Then we can add a property or compatible value if using something > else as needed. > What do you mean by parsing here? IIUC there isn't a clock driver for these clocks and are setup directly in the drivers/net/wireless/ti/wl12xx/main.c driver. So you can't make the WLAN chip dev node a consumer of these clocks by adding a phandle to a clock provider and clock specifiers since there isn't a provider to be referenced in the DT. Or did I misunderstand? > Regards, > > Tony Best regards, Javier -- 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
