From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/4] ARM: pmu: improve PMU type identification
Date: Wed, 29 Jun 2011 11:42:13 +0100 [thread overview]
Message-ID: <20110629104213.GC2589@pulham.picochip.com> (raw)
In-Reply-To: <20110629093652.GH1181@e102144-lin.cambridge.arm.com>
On Wed, Jun 29, 2011 at 10:36:53AM +0100, Will Deacon wrote:
> Russell,
>
> On Wed, Jun 29, 2011 at 10:26:22AM +0100, Russell King - ARM Linux wrote:
> > On Wed, Jun 15, 2011 at 03:40:00PM +0100, Mark Rutland wrote:
> > > can be used similarly (the macros make entries look identical apart from the
> > > {plat,of} prefix). This allows us to stop (ab)using platform_device::id, and
> > > should allow for easier addition/modification of PMU driver bindings.
> > >
> > > BSPs need no longer care about the Type of PMUs they register; as long as a
> > > binding exists the type will be assigned correctly.
> >
> > Could someone please look at adding an entry to the MAINTAINERS file
> > for the ARM PMU stuff, so we know who should be looking after this stuff?
>
> I'm happy to maintain this stuff if nobody has any objections.
No objections from me, I think that sounds like a very good idea!
Jamie
next prev parent reply other threads:[~2011-06-29 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 14:40 [PATCHv2 0/4] ARM: pmu: improve PMU type identification Mark Rutland
2011-06-15 14:40 ` [PATCHv2 1/4] ARM: pmu: refactor reservation Mark Rutland
2011-06-15 14:40 ` [PATCHv2 2/4] ARM: pmu: reject duplicate PMU registrations Mark Rutland
2011-06-15 14:40 ` [PATCHv2 3/4] ARM: pmu: add OF probing support Mark Rutland
2011-06-15 14:40 ` [PATCHv2 4/4] ARM: pmu: add platform_device_id table support Mark Rutland
2011-06-15 14:45 ` [PATCHv2 0/4] ARM: pmu: improve PMU type identification Jamie Iles
2011-06-15 15:01 ` Rob Herring
2011-06-29 9:26 ` Russell King - ARM Linux
2011-06-29 9:36 ` Will Deacon
2011-06-29 10:42 ` Jamie Iles [this message]
2011-06-29 13:32 ` Jean Pihet
2011-06-29 15:29 ` Linus Walleij
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=20110629104213.GC2589@pulham.picochip.com \
--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 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.