From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 4/7] arm: omap4: hwmod: introduce emu hwmod
Date: Fri, 11 Nov 2011 11:47:35 +0000 [thread overview]
Message-ID: <20111111114735.GC5114@totoro> (raw)
In-Reply-To: <20111111114147.GE12410@mudshark.cambridge.arm.com>
On Fri, Nov 11, 2011 at 11:41:47AM +0000, Will Deacon wrote:
> [Adding Benoit to CC].
>
> On Thu, Nov 10, 2011 at 09:02:14AM +0000, Paul Walmsley wrote:
> > On Wed, 9 Nov 2011, Ming Lei wrote:
> > > Also, current arm perf code don't handle three IRQs(one pl310 irq and
> > > two CTI irq) inside one device correctly.
> >
> > To fix this, that ARM perf code should either be using
> > platform_get_irq_byname(), or the hwmod hardware data will need to be
> > rearranged to meet the arbitrary ordering requirement. I'd suggest
> > pinging Will on this issue to see what he wants to do.
>
> The issue stems from the fact that we have to route the PMU interrupts to
> the correct CPU manually (I think only MSM routes them as PPIs, which is
> clearly the correct thing to do). To do this, we expect the IRQ resources to
> be laid out in CPU order. In hindsight, maybe naming the resources might
> have been a good idea, but them we'd still have to generate the names using
> CPU numbers when iterating through the platform device.
There isn't yet a way to do naming of resources with DT, and although I
think there was a proposal for doing named register resources I don't
think this has been accepted and there wasn't anything for IRQ
resources...
Jamie
next prev parent reply other threads:[~2011-11-11 11:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 14:45 [PATCH v5 0/7] arm: pmu: support pmu/perf on OMAP4 ming.lei at canonical.com
2011-10-24 14:45 ` [PATCH v5 1/7] arm: introduce cross trigger interface helpers ming.lei at canonical.com
2011-10-24 14:45 ` [PATCH v5 2/7] arm: pmu: allow platform specific irq enable/disable handling ming.lei at canonical.com
2011-11-01 3:26 ` Ming Lei
2011-11-01 12:52 ` Will Deacon
2011-10-24 14:45 ` [PATCH v5 3/7] arm: perf: support device with other non-irq resources ming.lei at canonical.com
2011-10-24 15:08 ` Will Deacon
2011-10-25 1:09 ` Ming Lei
2011-10-25 8:34 ` Will Deacon
2011-10-25 8:44 ` Paul Walmsley
2011-10-25 10:23 ` Ming Lei
2011-10-25 11:00 ` Paul Walmsley
2011-11-08 9:25 ` Ming Lei
2011-11-08 12:17 ` Will Deacon
2011-10-24 14:45 ` [PATCH v5 4/7] arm: omap4: hwmod: introduce emu hwmod ming.lei at canonical.com
2011-11-08 15:26 ` Paul Walmsley
2011-11-09 9:56 ` Ming Lei
2011-11-10 9:02 ` Paul Walmsley
2011-11-11 11:41 ` Will Deacon
2011-11-11 11:47 ` Jamie Iles [this message]
2011-11-11 11:59 ` Will Deacon
2011-11-11 14:56 ` Cousson, Benoit
2011-11-11 14:58 ` Will Deacon
2011-11-11 15:12 ` Cousson, Benoit
2011-11-11 15:22 ` Will Deacon
2011-11-18 12:58 ` Cousson, Benoit
2011-11-18 14:56 ` Will Deacon
2011-11-19 14:42 ` Ming Lei
2011-11-20 3:27 ` Paul Walmsley
2011-11-21 13:58 ` Will Deacon
2011-11-21 14:53 ` Ming Lei
2011-11-21 15:16 ` Will Deacon
2011-11-21 15:30 ` Ming Lei
2011-11-19 14:37 ` Ming Lei
2011-11-27 1:58 ` Paul Walmsley
2011-11-27 2:07 ` Paul Walmsley
2011-11-29 16:19 ` Cousson, Benoit
2011-11-29 18:11 ` Paul Walmsley
2011-11-30 16:20 ` Cousson, Benoit
2011-11-08 15:42 ` Paul Walmsley
2011-11-09 11:33 ` Ming Lei
2011-10-24 14:45 ` [PATCH v5 5/7] arm: omap4: create pmu device via hwmod ming.lei at canonical.com
2011-10-24 14:45 ` [PATCH v5 6/7] arm: omap4: support pmu ming.lei at canonical.com
2011-11-23 17:47 ` Rabin Vincent
2011-11-25 0:37 ` Ming Lei
2011-10-24 14:45 ` [PATCH v5 7/7] arm: omap4: pmu: support runtime pm ming.lei at canonical.com
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=20111111114735.GC5114@totoro \
--to=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox