linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/4] ARM: pmu: improve PMU type identification
Date: Wed, 15 Jun 2011 10:01:08 -0500	[thread overview]
Message-ID: <4DF8C934.4020008@gmail.com> (raw)
In-Reply-To: <1308148804-5518-1-git-send-email-mark.rutland@arm.com>

Mark,

On 06/15/2011 09:40 AM, Mark Rutland wrote:
> Hi,
> 
> This is version 2 of the patches originally posted here:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2011-June/052865.html
> 
> Changes since v1 include:
> 
>  * Added Acks from Jamie Iles & Rob Herring.
>  * Add "arm-pmu" binding to the platform_device_id table, as driver name
>    matching is not used when platform_driver::id_table exists.
>  * Fixed name clash in PLAT_MATCH_PMU macro.
>  * Removed unnecessary casts for platform_device_id::driver_data.
>  * Aligned trailing backslashes on multi-line *_MATCH_PMU macros.
>  * Removed spaces after casts.
> 
> The patches use {of,platform}_device_id tables to provide the PMU type, which
> 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.
> 
> Rob, Jamie: would you mind if patches 3 & 4 were squashed together?
> Patch 4 depends heavily on patch 3, and there doesn't seem to be a clean way of
> fixing that.
> 
Interdependency is not really a good reason to combine patches, so I
would leave them as is. Functionality wise, they are doing different things.

Rob

  parent reply	other threads:[~2011-06-15 15:01 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 [this message]
2011-06-29  9:26 ` Russell King - ARM Linux
2011-06-29  9:36   ` Will Deacon
2011-06-29 10:42     ` Jamie Iles
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=4DF8C934.4020008@gmail.com \
    --to=robherring2@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).