> -----Original Message----- > From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] > Sent: Saturday, March 05, 2011 1:07 AM > To: DebBarma, Tarun Kanti > Cc: linux-omap@xxxxxxxxxxxxxxx > Subject: Re: [PATCH v11 6/8] dmtimer: switch-over to platform device > driver > > * DebBarma, Tarun Kanti <tarun.kanti@xxxxxx> [110304 10:50]: > > > -----Original Message----- > > > From: Tony Lindgren [mailto:tony@xxxxxxxxxxx] > > > Sent: Friday, March 04, 2011 10:53 PM > > > To: DebBarma, Tarun Kanti > > > Cc: linux-omap@xxxxxxxxxxxxxxx > > > Subject: Re: [PATCH v11 6/8] dmtimer: switch-over to platform device > > > driver > > > > > > * Tarun Kanti DebBarma <tarun.kanti@xxxxxx> [110224 03:23]: > > > > --- a/arch/arm/mach-omap2/dmtimer.c > > > > +++ b/arch/arm/mach-omap2/dmtimer.c > > > > @@ -197,3 +197,64 @@ static int __init omap_timer_init(struct > omap_hwmod > > > *oh, void *unused) > > > > > > > > return ret; > > > > } > > > > + > > > > +/** > > > > + * 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) > > > > +{ > > > > + int ret = omap_hwmod_for_each_by_class("timer", > > > > + omap_timer_init, NULL); > > > > > > Here we really only want to initialize the system timer. The rest we > > > want to do later, so let's not init all of them early. > > So, that is how it was at the beginning. > > Later we realized different platforms can use different timers for this. > > For example, beagle uses GPT12. Therefore, as part of one of the > comments, > > We decided to provide flexibility so that any of the timers could be > used. > > You can still do it, just register the one that's being used and mark > it reserved so it won't get initialized again later on. May be I was not clear in my explanation. Yes, you are right, the system timer gets reserved early and initialized. Later it is NOT initialized again. > > Tony -- 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
