On Tue, 5 Jun 2012, Jon Hunter wrote: > The OMAP dmtimer driver allows you to dynamically configure the functional > clock that drives the timer logic. The dmtimer driver uses the device name and > a "con-id" string to search for the appropriate functional clock. > > Currently, we define a clock alias for each functional clock source each timer > supports. Some functional clock sources are common to all of the timers on a > device and so for these clock sources we can use a single alias with a unique > con-id string. > > The possible functional clock sources for an OMAP device are a 32kHz clock, > a system (MHz range) clock and (for OMAP2 only) an external clock. By defining > a unique con-id name for each of these (timer_32k_ck, timer_sys_ck and > timer_ext_ck) we can eliminate a lot of the clock aliases for timers. This > reduces code, speeds-up searches and clock initialisation time. > > Signed-off-by: Jon Hunter <[email protected]>
Acked-by: Paul Walmsley <[email protected]> At some point we should probably investigate moving these aliases into the hwmod optional clocks, but this requires more thought. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
