On Tue, 1 Feb 2011, Rajendra Nayak wrote: > One other thing I was thinking of is if the function name > _add_optional_clock_alias need to be changed to something like > _add_optional_clock_clkdev since we are adding a new clkdev entry, > if it does not exist, and no longer adding an 'alias' for an existing > entry. Fine with me. > Also, the adding of an entry in clkdev is today done for > optional clocks alone. Is there any reason why we should not do > this at runtime for all main clks and interface clks also. > That way we get rid of all dependencies with the static clkdev > table, and we might infact not need one if all entries are added > runtime. Heh, you've just uncovered my "secret" plan. It seemed best to me to wait until all of the hwmod conversions were done to avoid alarming certain people who might be consulting the static clkdev table in mach-omap2/clock*_data.c as a platform reference... - Paul -- 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
