From: Avik Sil <aviksil@linux.vnet.ibm.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: arm: pmu: support pmu/perf on OMAP4 - booting problem on pandaboard
Date: Thu, 07 Apr 2011 14:36:22 +0530 [thread overview]
Message-ID: <4D9D7E8E.7020200@linux.vnet.ibm.com> (raw)
In-Reply-To: <BANLkTikxu3DaxWZ88wgCP2cCZD=kNm-YeQ@mail.gmail.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,
WARNING: multiple messages have this Message-ID (diff)
From: aviksil@linux.vnet.ibm.com (Avik Sil)
To: linux-arm-kernel@lists.infradead.org
Subject: arm: pmu: support pmu/perf on OMAP4 - booting problem on pandaboard
Date: Thu, 07 Apr 2011 14:36:22 +0530 [thread overview]
Message-ID: <4D9D7E8E.7020200@linux.vnet.ibm.com> (raw)
In-Reply-To: <BANLkTikxu3DaxWZ88wgCP2cCZD=kNm-YeQ@mail.gmail.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,
next prev parent reply other threads:[~2011-04-07 9:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 14:33 arm: pmu: support pmu/perf on OMAP4 - booting problem on pandaboard Avik Sil
2011-04-02 5:27 ` Ming Lei
2011-04-02 5:27 ` Ming Lei
2011-04-04 14:14 ` Avik Sil
2011-04-04 14:14 ` Avik Sil
2011-04-04 14:23 ` Ming Lei
2011-04-04 14:23 ` Ming Lei
2011-04-04 16:01 ` Avik Sil
2011-04-04 16:01 ` Avik Sil
2011-04-05 2:03 ` Ming Lei
2011-04-05 2:03 ` Ming Lei
2011-04-05 11:05 ` Avik Sil
2011-04-05 11:05 ` Avik Sil
2011-04-06 6:07 ` Ming Lei
2011-04-06 6:07 ` Ming Lei
2011-04-07 9:06 ` Avik Sil [this message]
2011-04-07 9:06 ` Avik Sil
2011-04-07 9:54 ` Ming Lei
2011-04-07 9:54 ` Ming Lei
2011-04-07 10:42 ` Avik Sil
2011-04-07 10:42 ` Avik Sil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D9D7E8E.7020200@linux.vnet.ibm.com \
--to=aviksil@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tom.leiming@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.