Hi Kevin, On Sat, Nov 03, 2012 at 17:13:54, Kevin Hilman wrote: > On 11/02/2012 01:32 PM, Vaibhav Bedia wrote: > > AM33XX has only one usable timer in the WKUP domain. > > Currently the timer instance in WKUP domain is used > > as the clockevent and the timer in non-WKUP domain > > as the clocksource. The timer in WKUP domain can keep > > running in suspend from a 32K clock and hence serve > > as the persistent clock. To enable this, interchange > > the timers used as clocksource and clockevent for > > AM33XX. > > Doesn't this also mean that you won't get timer wakeups > in idle? Or are you keeping the domain where the clockevent is > on during idle? > The lowest idle state that we are targeting will have MPU powered off with external memory in self-refresh mode. Peripheral domain with the clockevent will be kept on. Regards, Vaibhav -- 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
