On Thu, Dec 1, 2011 at 12:58 AM, Cousson, Benoit <b-cousson@xxxxxx> wrote: > On 12/1/2011 9:16 AM, Tomi Valkeinen wrote: >> From driver's perspective I think this only makes things more complex, >> as the driver is not interested in the parent, only about the dss fck. > > Fully agree. It should transparent for the driver. The new common clk patches do try to take care of this. A child clk may be marked with CLK_PARENT_RATE_CHANGE flag which tells clk_set_rate to (potentially) propagate up to the parent and change it's rate. This won't help you currently Tomi, but you can take comfort knowing that someday your driver won't have to know details about dss_fck's parent ;-) Regards, Mike -- 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
