On 11/22/2012 1:30 AM, Igor Mazanov wrote: > On Wed, Nov 21, 2012 at 9:38 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: >> * Jean Pihet <jean.pihet@xxxxxxxxxxxxxx> [121114 08:43]: >>> On Wed, Nov 14, 2012 at 4:28 PM, Igor Mazanov <i.mazanov@xxxxxxxxx> wrote: >>>> >>>> Beaglebone boot process is broken with the current git kernel. I use >>>> omap2plus_defconfig for tests. >>>> >>>> It looks like the boot process stops due to the last changes in the AM33xx >>>> clock sysbsystem. A following patch resolves this issue: >> ... >> >>> The patch should change the name of the hwmod entry as well, can you >>> fold this change in the current patch? >> >> Any news on updating this? > > The current kernel boots, but after a switching to CCF doesn't work > the debugss - it's just disabled in the current hwmod code. So, it > looks like we can't use JTAG to connect to the running kernel. > just resumed from vacation... JTAG clock will get disabled because, CONFIG_OMAP_RESET_CLOCKS will disable unused clocks, so as debugss clock. There is another thread started by Joel on the similar issue, http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg80863.html Something below should be done for debugss on AM33xx, diff --git a/arch/arm/mach-omap2/clock33xx_data.c b/arch/arm/mach-omap2/clock33xx_data.c index 17e3de5..60e0b53 100644 --- a/arch/arm/mach-omap2/clock33xx_data.c +++ b/arch/arm/mach-omap2/clock33xx_data.c @@ -584,6 +584,9 @@ static struct clk debugss_ick = { .clkdm_name = "l3_aon_clkdm", .parent = &dpll_core_m4_ck, .ops = &clkops_omap2_dflt, +#ifdef CONFIG_DEBUG_KERNEL + .flags = ENABLE_ON_INIT, +#endif .enable_reg = AM33XX_CM_WKUP_DEBUGSS_CLKCTRL, .enable_bit = AM33XX_MODULEMODE_SWCTRL, .recalc = &followparent_recalc, Thanks, Vaibhav > Regards, > Igor. > >> 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 > -- 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
