On Wednesday 01 October 2008, Felipe Balbi wrote: > +/** > + * clk_associate - associates a user to a clock so device drivers don't > + * have to care about clock names > + * > + * @id: clock id as defined in arch/arm/mach-omapX/clkxxxx.h > + * @dev: device pointer for the clock user > + * @f: a function for the clock (uart_[if]ck, musb_ick, ehci_[if]ck, etc) > + */ > +void __init clk_associate(const char *id, struct device *dev, const char *f) Heh. I remember coming up with that same abstraction for mach-at91/clock.c a few years back. It seems to have worked fairly well in that far simpler environment, and I can't imagine why it wouldn't work here too. The name might be confusing though, since it's not part of the standard clk_*() interface ... and the name might be needed there, eventually. So mirroring "at91_clock_associate()" ... maybe this should be "omap_clock_associate()" not "clk_associate()". - Dave -- 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
