* Tony Lindgren <tony@xxxxxxxxxxx> [110325 08:54]: > * DebBarma, Tarun Kanti <tarun.kanti@xxxxxx> [110324 23:53]: > > Hi Tony, > > [...] > > > Well the dmtimer code can then become just a regular platform_device > > > based driver, except for clockevent and clocksource on omap2 & 3. > > Should I re-post the patch series with removal of duplicate initialization > > Which Kevin pointed out + other relevant comments? > > Or, wait for your patch series! > > Just wait few days please, I should have something available that mostly > deals with timer-gp.c, so it should not cause too many issues with your > patches. FYI, posted some patches in the "omap init_early changes for irq and timer init" thread, also available in devel-timer branch. Few notes regarding updating your dmtimer series: - Add the dmtimer arch_initcall into arch/arm/mach-omap2/timer.c so we don't end up with yet another timer*.c file there - Make use of omap_dm_timer_init_one in the dmtimer arch_initcall so sys_timer initialized struct omap_dm_timer can be picked up - You can pick the reserved clockevent and clocksource timers based on the sys_timer_reserved mask and then create proper dev entries for those too later on during the init - Now arch/arm/plat-omap/dmtimer.c can become just a driver module living under drivers somewhere Other than that, your patches should be pretty easy to rebase. Regards, 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
