> -----Original Message----- > From: Tony Lindgren [mailto:[email protected]] > Sent: Tuesday, March 08, 2011 5:37 AM > To: DebBarma, Tarun Kanti > Cc: Shilimkar, Santosh; [email protected] > Subject: Re: [PATCH v11 6/8] dmtimer: switch-over to platform device > driver > > * DebBarma, Tarun Kanti <[email protected]> [110307 04:52]: > > > > > > I agree with Tony. We can still registers only the system > > > timer because the timer ID is known well before we do > > > initialization. > > I must say, there was a gap in my understanding of the comment. > > So, here is the implementation change: > > > > -> Call omap2_dm_timer_early_init(u8 gptimer_id) from > omap2_gp_timer_init() > > -> Initialize only gptimer_id inside this function > > -> In the regular init skip initialization of gptimer_id > > > > As a result of this, we can rid of double registration and related code. > > I suggest we keep the system timer completely separate from the > rest of the timers. This way we avoid adding hwmod dependencies > early on when the system timer is initialized, and can still > use hwmod for handling the the rest of the timers nicely. Yes, just the system timer is initialized now. We just call omap_hwmod_setup_one() to initialize system timer.
> > The rest of the timers can then become just a regular device > driver that ignores the physical system timer. Right, system timer is NOT touched at all later. > > Regards, > > Tony -- 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
