Kevin, > -----Original Message----- > From: Kevin Hilman [mailto:khilman@xxxxxxxxxxxxxxxxxxx] > Sent: Tuesday, August 24, 2010 5:41 AM > To: DebBarma, Tarun Kanti > Cc: linux-omap@xxxxxxxxxxxxxxx; Gopinath, Thara; Basak, Partha; Nayak, > Rajendra; Paul Walmsley; Tony Lindgren > Subject: Re: [PATCHv2 6/13] dmtimer: hwmod: OMAP2PLUS: device registration > > Tarun Kanti DebBarma <tarun.kanti@xxxxxx> writes: > > > +/** > > +* omap2_dm_timer_early_init - top level early timer initialization > > +* called in the last part of omap2_init_common_hw > > +* > > +* uses dedicated hwmod api to parse through hwmod database for > > +* given class name and then build and register the timer device. > > +* at the end driver is registered and early probe initiated. > > +**/ > > +void __init omap2_dm_timer_early_init(void) > > +{ > > + omap_hwmod_for_each_by_class("timer_1ms", > > + omap_dm_timer_early_init, NULL); > > + omap2_dm_timer_setup(); > > + early_platform_driver_register_all("earlytimer"); > > + early_platform_driver_probe("earlytimer", early_timer_count + 1, 0); > > +} > > It's not clear (or documented) why on the 1ms timers should be the only > earlydevices. > > For example, GPT12 is used as the system timer on Beagle due to a board > bug in early revs of the board. That will no longer function with this > approach. > OK, I will change the design so that any timers could be used as early timers. > Kevin > -- 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
