* Cousson, Benoit <b-cousson@xxxxxx> [110316 07:31]: > Hi Aaro, > > On 3/16/2011 2:49 PM, Aaro Koskinen wrote: > >Hi, > > > >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? > > > > >[...] > > > >[ 4.306549] OMAP GPIO hardware version 2.5 > >[ 4.310913] omap_hwmod: gpio4: enabling > >[ 4.314971] omap_hwmod: gpio4: enabling clocks > >[ 4.320037] OMAP GPIO hardware version 2.5 > >[ 4.324401] omap_hwmod: gpio5: enabling > >[ 4.328460] omap_hwmod: gpio5: enabling clocks > >[ 4.333526] OMAP GPIO hardware version 2.5 > >[ 4.337921] omap_hwmod: gpio6: enabling > >[ 4.341949] omap_hwmod: gpio6: enabling clocks > >[ 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? FYI, my rx51 boots fine with omap2plus defconfig, also with earlyprintk. Sounds like it's some HS omap issue on both your boards. I think you have ttyO in your CONFIG_CMDLINE if you're using omap2plus_defconfig. Then for rm680 you'll probably need also: CONFIG_CMDLINE_FORCE=y 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
