From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] arm: pmu: support pmu irq routed from CTI
Date: Tue, 1 Mar 2011 14:00:58 -0000 [thread overview]
Message-ID: <000601cbd819$1780a540$4681efc0$@deacon@arm.com> (raw)
In-Reply-To: <1298985434-3009-3-git-send-email-tom.leiming@gmail.com>
Hello,
> Subject: [PATCH 2/3] arm: pmu: support pmu irq routed from CTI
>
> From: Ming Lei <tom.leiming@gmail.com>
>
> This patch introduces pmu_platform_data struct to
> support pmu irq routed from CTI, such as implemented
> on OMAP4.
>
> Generally speaking, clearing cti irq should be done in
> irq handler, also enabling cti module after calling
> request_irq and disabling cti module before calling
> free_irq.
>
> Signed-off-by: Ming Lei <tom.leiming@gmail.com>
> ---
> arch/arm/include/asm/pmu.h | 12 ++++++++++
> arch/arm/kernel/perf_event.c | 51 ++++++++++++++++++++++++++++++++++++-----
> 2 files changed, 56 insertions(+), 7 deletions(-)
This will conflict with the the ux500 PMU workaround:
http://lists.infradead.org/pipermail/linux-arm-kernel/2011-February/041145.html
Will
next prev parent reply other threads:[~2011-03-01 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 13:17 [PATCH 0/3] arm: support pmu irq routed from CTI tom.leiming at gmail.com
2011-03-01 13:17 ` [PATCH 1/3] arm: introduce cross trigger interface helpers tom.leiming at gmail.com
2011-03-01 13:17 ` [PATCH 2/3] arm: pmu: support pmu irq routed from CTI tom.leiming at gmail.com
2011-03-01 14:00 ` Will Deacon [this message]
[not found] ` <-294597288559385401@unknownmsgid>
2011-03-01 15:31 ` Ming Lei
2011-03-01 13:17 ` [PATCH 3/3] arm: omap4: support pmu tom.leiming
2011-03-01 13:17 ` tom.leiming at gmail.com
2011-03-01 13:36 ` Santosh Shilimkar
2011-03-01 13:36 ` 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='000601cbd819$1780a540$4681efc0$@deacon@arm.com' \
--to=will.deacon@arm.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 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.