From mboxrd@z Thu Jan 1 00:00:00 1970 From: aviksil@linux.vnet.ibm.com (Avik Sil) Date: Thu, 07 Apr 2011 16:12:17 +0530 Subject: arm: pmu: support pmu/perf on OMAP4 - booting problem on pandaboard In-Reply-To: References: <4D95E244.1050400@linux.vnet.ibm.com> <4D99D251.6000901@linux.vnet.ibm.com> <4D99EB4B.3020303@linux.vnet.ibm.com> <4D9AF790.7010504@linux.vnet.ibm.com> <4D9D7E8E.7020200@linux.vnet.ibm.com> Message-ID: <4D9D9509.7050804@linux.vnet.ibm.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Ming, On Thursday 07 April 2011 03:24 PM, Ming Lei wrote: > Hi Avik, > > Please check if the option CONFIG_PM is enabled or not. CONFIG_PM is enabled in my config: $ grep CONFIG_PM .config CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_PM_SLEEP_SMP=y CONFIG_PM_SLEEP=y CONFIG_PM_RUNTIME=y CONFIG_PM_OPS=y CONFIG_PM_OPP=y CONFIG_PMIC_DA903X=y CONFIG_PMIC_ADP5520=y As suggested in http://groups.google.com/group/pandaboard/browse_thread/thread/74abf5dafa2fd6e2/b1cc29b5060b4223?#b1cc29b5060b4223 , do you think prcm_setup_regs() has to be called for OMAP4? Regards, Avik > > If not, please try to enable it to see you issue can be fixed. > > > 2011/4/7 Avik Sil: >> Hi Ming, >> >> On Wednesday 06 April 2011 11:37 AM, Ming Lei wrote: >>> >>> Hi Avik, >>> >>> 2011/4/5 Avik Sil: >>>> >>>> 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,