From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: pmu: improve PMU type identification
Date: Mon, 13 Jun 2011 10:35:53 +0100 [thread overview]
Message-ID: <1307957757-23001-1-git-send-email-mark.rutland@arm.com> (raw)
In-Reply-To: <4DEFA5E1.9010600@gmail.com>
Hi Rob,
I've Addded Jamie on Cc here as he was interested in the possibility of
adding platform_device_id tables. Hopefully it'll be easy to discuss
{of,platform}_id_tables in one thread.
As Jamie pointed out to me the existence of platform_device_id tables,
I took a look around and noticed that of_device_id tables also seem to
provide support for driver-specific parameters (I saw an example of
usage in arch/sparc/kernel/pci_schizo.c).
I've had a go at getting {of,platform}_device_id tables to provide the
PMU type, so they can be used similarly (the macros make entries look
identical apart from the {plat,of} prefix).
I don't have any entries currently for the platform_device_id table,
but it'd be useful for system pmus, if we were to add an L2 Cache
controller PMU driver, it might have a binding like:
> PLAT_MATCH("arm,pl310-pmu", ARM_PMU_TYPE_L2CC),
How does the following series look to you? The first 2 patches are the
ones I mentioned before, unchanged (apart from additional acks).
Mark.
Mark Rutland (4):
ARM: pmu: refactor reservation
ARM: pmu: reject duplicate PMU registrations
ARM: pmu: add OF probing support
ARM: pmu: add platform_device_id table support
Documentation/devicetree/bindings/arm/pmu.txt | 22 ++++++
arch/arm/include/asm/pmu.h | 2 +-
arch/arm/kernel/perf_event.c | 4 +-
arch/arm/kernel/pmu.c | 91 ++++++++++++++++++++-----
4 files changed, 99 insertions(+), 20 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/pmu.txt
next prev parent reply other threads:[~2011-06-13 9:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 14:22 [PATCH v2 0/3] DT bindings for Cortex A9 peripherals Rob Herring
2011-06-07 14:22 ` [PATCH 1/3] ARM: pmu: add OF probing support Rob Herring
2011-06-08 15:54 ` Mark Rutland
2011-06-08 16:40 ` Rob Herring
2011-06-13 9:35 ` Mark Rutland [this message]
2011-06-13 9:35 ` [PATCH 1/4] ARM: pmu: refactor reservation Mark Rutland
2011-06-13 9:35 ` [PATCH 2/4] ARM: pmu: reject duplicate PMU registrations Mark Rutland
2011-06-13 9:35 ` [PATCH 3/4] ARM: pmu: add OF probing support Mark Rutland
2011-06-13 13:40 ` Rob Herring
2011-06-13 13:48 ` Mark Rutland
2011-06-13 13:55 ` Rob Herring
2011-06-13 9:35 ` [PATCH 4/4] ARM: pmu: add platform_device_id table support Mark Rutland
2011-06-13 12:33 ` Sergei Shtylyov
2011-06-13 12:41 ` Mark Rutland
2011-06-13 14:29 ` Jamie Iles
2011-06-13 16:44 ` [PATCH 1/3] ARM: pmu: add OF probing support Grant Likely
2011-06-07 14:22 ` [PATCH 2/3] ARM: gic: add OF based initialization Rob Herring
2011-06-13 16:53 ` Grant Likely
2011-06-13 21:39 ` Rob Herring
2011-06-13 22:14 ` Russell King - ARM Linux
2011-06-14 13:56 ` Grant Likely
2011-06-07 14:22 ` [PATCH 3/3] ARM: l2x0: Add " Rob Herring
2011-06-07 16:20 ` Olof Johansson
2011-06-07 16:54 ` Rob Herring
2011-06-07 18:49 ` Olof Johansson
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=1307957757-23001-1-git-send-email-mark.rutland@arm.com \
--to=mark.rutland@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).