All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 05 Apr 2011 16:35:52 +0530	[thread overview]
Message-ID: <4D9AF790.7010504@linux.vnet.ibm.com> (raw)
In-Reply-To: <BANLkTinQ-QQ7zu2KrhhhdWwnzo=a-KynoQ@mail.gmail.com>

On Tuesday 05 April 2011 07:33 AM, Ming Lei wrote:
> Hi,
>
> 2011/4/5 Avik Sil<aviksil@linux.vnet.ibm.com>:
>> #define OMAP4430_CM_L3INSTR_L3_3_CLKCTRL
>> OMAP44XX_CM2_REGADDR(OMAP4430_CM2_CORE_INST, 0x0720)
>> [...]
>>
>> Should I use those identifier instead?
>
> Yes, seems right, but you need to use the ioremap addresses of the identifiers.
>
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?

Regards,
Avik
>> Are there other definitions for the identifiers you have used?
>
> As I said  before, these are not needed for mainline, so I didn't try these.
>
>
> 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: Tue, 05 Apr 2011 16:35:52 +0530	[thread overview]
Message-ID: <4D9AF790.7010504@linux.vnet.ibm.com> (raw)
In-Reply-To: <BANLkTinQ-QQ7zu2KrhhhdWwnzo=a-KynoQ@mail.gmail.com>

On Tuesday 05 April 2011 07:33 AM, Ming Lei wrote:
> Hi,
>
> 2011/4/5 Avik Sil<aviksil@linux.vnet.ibm.com>:
>> #define OMAP4430_CM_L3INSTR_L3_3_CLKCTRL
>> OMAP44XX_CM2_REGADDR(OMAP4430_CM2_CORE_INST, 0x0720)
>> [...]
>>
>> Should I use those identifier instead?
>
> Yes, seems right, but you need to use the ioremap addresses of the identifiers.
>
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?

Regards,
Avik
>> Are there other definitions for the identifiers you have used?
>
> As I said  before, these are not needed for mainline, so I didn't try these.
>
>
> thanks,

  reply	other threads:[~2011-04-05 11:05 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 [this message]
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
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=4D9AF790.7010504@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.