Hi,
On Wed, 16 Mar 2011, Cousson, Benoit wrote:
On 3/16/2011 2:49 PM, Aaro Koskinen wrote:
On Tue, 15 Mar 2011, Cousson, Benoit wrote:
Mmm, that looks like an access to a secure timer from hwmod code on a HS
device. Could you comment out the timer12 entry (&omap3xxx_timer12_hwmod)
in
the omap3 hwmod list at the end of omap_hwmod_3xxx_data.c to check that?
With timer12 entry commented out and omap_hwmod debugs enabled, it now
hangs here:
Do you need that timer BTW?
Probably no at the moment. :-)
[ 4.347015] OMAP GPIO hardware version 2.5
GPIO are now initialized during postcore_initcall, so it is hard to know what
will happen after that:-(
Could you try with initcall_debug in your command line?
Somehow I figured this out, the patch "arm: mach-omap2: omap_l3_smx:
fix irq handler setup" fixes the hang for me (and of course I still need
to comment out timer 12).
A.
--
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
