From: tom.leiming@gmail.com (tom.leiming at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch v2 0/3] arm: pmu: support pmu/perf on OMAP4
Date: Wed, 2 Mar 2011 18:56:57 +0800 [thread overview]
Message-ID: <1299063420-22203-1-git-send-email-tom.leiming@gmail.com> (raw)
Hi,
This patches support pmu irq routed from CTI, such as implemented
on OMAP4:
- introduce some CTI helpers and registers' definition
- introduce .enable_irq and .disable_irq into platform_data,
so perf irq handler can handle irq correctly if it is
routed from CTI on OMAP4
- configure CTI on OMAP4 so that perf can work on OMAP4
The patches have been tested Ok on Pandaboard, and 'perf' does work
after applying them.
v2:
- move cti related code out of perf_event.c
- introduce .enable_irq and .disable_irq into platform_data
as suggested by Will.
v1:
- rebase the patch set against 2.6.38-rc6-next-20110301, fix
conflicts, which is pointed out by Will Deacon
arch/arm/include/asm/cti.h | 177 +++++++++++++++++++++++++++++++++++++++++
arch/arm/include/asm/pmu.h | 15 +++-
arch/arm/kernel/perf_event.c | 15 +++-
arch/arm/mach-omap2/dbg44xx.h | 18 ++++
arch/arm/mach-omap2/devices.c | 83 ++++++++++++++++++-
5 files changed, 299 insertions(+), 9 deletions(-)
thanks,
--
Lei Ming
next reply other threads:[~2011-03-02 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 10:56 tom.leiming at gmail.com [this message]
2011-03-02 10:56 ` [patch v2 1/3] arm: introduce cross trigger interface helpers tom.leiming at gmail.com
2011-03-02 10:56 ` [patch v2 2/3] arm: pmu: allow platform specifc irq enable/disable handling tom.leiming at gmail.com
2011-03-02 12:10 ` Will Deacon
[not found] ` <-3190832915456449126@unknownmsgid>
2011-03-02 14:35 ` Ming Lei
2011-03-02 15:46 ` Will Deacon
2011-03-02 10:57 ` [patch v2 3/3] arm: omap4: support pmu tom.leiming at gmail.com
2011-03-02 12:43 ` Santosh Shilimkar
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=1299063420-22203-1-git-send-email-tom.leiming@gmail.com \
--to=tom.leiming@gmail.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;
as well as URLs for NNTP newsgroup(s).