From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/6] ARM: pmu: provide a registration mechanism for IRQs [v2]
Date: Fri, 12 Mar 2010 17:29:38 +0000 [thread overview]
Message-ID: <1268414985-22699-1-git-send-email-will.deacon@arm.com> (raw)
This is version 2 of the patch series originally posted here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/011162.html
Changes from the original version include:
- Removal of const keyword from IRQs to make it easier to select
the IRQs to register at runtime.
- Support for all the relevant Realview boards
- Support for OMAP2, OMAP3, BCMRING, iop and PXA platforms
The main reason for submitting this is to get some feedback on the
registration code I've added to the board files because I'm not familiar
with how the omap / bcmring / pxa / iop trees are structured.
All feedback welcome [including the results of any testing for the
platforms I've mentioned].
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jamie Iles <jamie.iles@picochip.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Leo Chen <leochen@broadcom.com>
Cc: Lennert Buytenhek <kernel@wantstofly.org>
Cc: Eric Miao <eric.y.miao@gmail.com>
Will Deacon (6):
ARM: pmu: register IRQs at runtime
ARM: Realview: register PMU IRQs during board initialisation
ARM: OMAP: register PMU IRQs during board initialisation
ARM: BCMRING: register PMU IRQ during board initialisation
ARM: iop3xx: register PMU IRQs during board initialisation
ARM: pxa: register PMU IRQs during board initialisation
arch/arm/include/asm/pmu.h | 36 ++++++++---
arch/arm/kernel/perf_event.c | 6 +-
arch/arm/kernel/pmu.c | 103 ++++++++++++++++-------------
arch/arm/mach-bcmring/arch.c | 13 ++++
arch/arm/mach-omap2/devices.c | 30 +++++++++
arch/arm/mach-pxa/pxa25x.c | 14 ++++
arch/arm/mach-pxa/pxa27x.c | 13 ++++
arch/arm/mach-pxa/pxa3xx.c | 14 ++++
arch/arm/mach-realview/realview_eb.c | 15 ++++
arch/arm/mach-realview/realview_pb1176.c | 12 ++++
arch/arm/mach-realview/realview_pb11mp.c | 15 ++++
arch/arm/mach-realview/realview_pba8.c | 12 ++++
arch/arm/mach-realview/realview_pbx.c | 15 ++++
arch/arm/plat-iop/Makefile | 2 +
arch/arm/plat-iop/pmu.c | 37 +++++++++++
15 files changed, 278 insertions(+), 59 deletions(-)
create mode 100644 arch/arm/plat-iop/pmu.c
next reply other threads:[~2010-03-12 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 17:29 Will Deacon [this message]
2010-03-12 17:29 ` [RFC PATCH 1/6] ARM: pmu: register IRQs at runtime Will Deacon
2010-03-12 17:29 ` [RFC PATCH 2/6] ARM: Realview: register PMU IRQs during board initialisation Will Deacon
2010-03-12 17:29 ` [RFC PATCH 3/6] ARM: OMAP: " Will Deacon
2010-03-12 17:29 ` [RFC PATCH 4/6] ARM: BCMRING: register PMU IRQ " Will Deacon
2010-03-12 17:29 ` [RFC PATCH 5/6] ARM: iop3xx: register PMU IRQs " Will Deacon
2010-03-12 17:29 ` [RFC PATCH 6/6] ARM: pxa: " Will Deacon
2010-03-16 11:41 ` [RFC PATCH 1/6] ARM: pmu: register IRQs at runtime Jamie Iles
2010-03-17 16:06 ` Will Deacon
2010-03-17 16:11 ` Will Deacon
2010-03-17 16:11 ` [RFC PATCH 2/6] ARM: Realview: register PMU IRQs during board initialisation Will Deacon
2010-03-18 12:20 ` [RFC PATCH 1/6] ARM: pmu: register IRQs at runtime Jamie Iles
2010-03-24 15:50 ` Will Deacon
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=1268414985-22699-1-git-send-email-will.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 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).