Re: arm: pmu: support pmu/perf on OMAP4 - booting problem on pandaboard

[Ming Lei <tom.leiming@gmail.com>]

Hi Avik,

Please check if the option CONFIG_PM is enabled or not.

If not, please try to enable it to see you issue can be fixed.


2011/4/7 Avik Sil <aviksil@linux.vnet.ibm.com>:
> Hi Ming,
>
> On Wednesday 06 April 2011 11:37 AM, Ming Lei wrote:
>>
>> Hi Avik,
>>
>> 2011/4/5 Avik Sil<aviksil@linux.vnet.ibm.com>:
>>>
>>> Even after using ioremapped addresses in omap_writel() I'm getting the
>>> oops.
>>> Can you please point me to the location in mainline, where these l3
>>> clocks
>>> are enabled?
>>
>> I guess you can find here:
>>
>>          l3_main_3_ick&&  l3_instr_ick:
>> arch/arm/mach-omap2/clock44xx_data.c
>>
>> the clocks are set as ENABLE_ON_INIT.
>
> Those clocks are also set ENABLE_ON_INIT in the linaro kernel. But still
> it's hanging at "val = __raw_readl(base + LOCKSTATUS);" in cti_unlock(),
> even after explicitly enabling it using:
>
> omap_writel(1, CM_L3INSTR_L3_3_CLKCTRL);
> omap_writel(1, CM_L3INSTR_L3_INSTR_CLKCTRL);
> omap_writel(2, CM_EMU_CLKSTCTRL);
> while ((omap_readl(CM_EMU_CLKSTCTRL) & 0x300) != 0x300);
>
> BTW, the oops were fixed by replacing omap_writel with __raw_writel.
>
> Regards,
> Avik
>
>>
>> thanks,
>
>


thanks,
-- 
Ming Lei
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html