On Thu, Sep 15, 2011 at 3:15 AM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > Hi, > > * Tarun Kanti DebBarma <tarun.kanti@xxxxxx> [110908 13:36]: >> Register timer devices by going through hwmod database using >> hwmod API. The driver probes each of the registered devices. >> Functionality which are already performed by hwmod framework >> are removed from timer code. New set of timers present on >> OMAP4 are now supported. > > Adding the support for the different offsets on some omap4 > timers should be a separate patch. > > Also, as we don't need the support for different register offsets > for the first two omap4 timers, please rather implement support > for the new timers and the timeouts directly in plat-omap/dmtimer.c. > > That way we can still keep the minimal timer support simple > for clocksource and clockevent. Of course this means that we'll > be only supporting the first two timers as system timers on > omap4, but that's fine. Ok, I can make the change! But, do we have to keep OMAP5 in mind right now where even timers[1,2] require addition of offsets? -- Tarun [...] -- 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
