RE: [PATCH] omap: Move omap_hwmod_late_init() to mdesc->timer->init() code

[Santosh Shilimkar <santosh.shilimkar@ti.com>]

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Tony Lindgren
> Sent: Tuesday, February 22, 2011 10:19 PM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; Paul Walmsley; Kevin Hilman; Benoit
> Cousson
> Subject: Re: [PATCH] omap: Move omap_hwmod_late_init() to mdesc-
> >timer->init() code
>
> * Santosh Shilimkar <santosh.shilimkar@ti.com> [110222 06:35]:
> > To adhere to recent early_init changes, commit '44dc0' made
> > omap_hwmod_late_init() to core_initcall to avoid ioremap()
> failures.
> >
> > Later 'e7c7d7' removed _mpu_rt_va population
> omap_hwmod_late_init()
> >
> > So now if we move the  omap_hwmod_late_init() to mdesc->timer-
> >init(),
> > timer1 should work with hwmod instead of any special hwmod
> settings.
>
> There should be no need to have all hwmods initialized just to get
> the system timer running. The system timer should be initialized
> with minimal code needed.
>
Sure

> Sure it can use hwmod functions as long as it makes sense, but
> we certainly don't want the whole hwmod framework initialized
> that early.
>
Something like hwmod_early_init() would solve the issue of early
devices. At least this is better than hacking early hwmod
drivers.
Looks like that's what we decided to go head with
looking at other thread.

Regards,
Santosh