From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: pmu: add platform_device_id table support
Date: Mon, 13 Jun 2011 13:41:08 +0100 [thread overview]
Message-ID: <000001cc29c7$2c0222f0$840668d0$@rutland@arm.com> (raw)
In-Reply-To: <4DF60384.4050805@ru.mvista.com>
Hi,
> -----Original Message-----
> From: Sergei Shtylyov [mailto:sshtylyov at mvista.com]
> Sent: 13 June 2011 13:33
> To: Mark Rutland
> Cc: Rob Herring; Jamie Iles; Will Deacon; linux-arm-
> kernel at lists.infradead.org
> Subject: Re: [PATCH 4/4] ARM: pmu: add platform_device_id table support
>
> Hello.
>
> On 13-06-2011 13:35, Mark Rutland wrote:
>
> > This patch adds support for platform_device_id tables, allowing new
> > PMU types to be registered with the correct type, without requiring
> > new platform_driver shims to provide the type.
>
> > Macros matching functionality of the of_device_id table macros are
> > provided for convenience.
>
> > Cc: Jamie Iles<jamie@jamieiles.com>
> > Cc: Will Deacon<will.deacon@arm.com>
> > ---
> > arch/arm/kernel/pmu.c | 19 +++++++++++++++++++
> > 1 files changed, 19 insertions(+), 0 deletions(-)
>
> > diff --git a/arch/arm/kernel/pmu.c b/arch/arm/kernel/pmu.c
> > index d34cf88..23c3af2 100644
> > --- a/arch/arm/kernel/pmu.c
> > +++ b/arch/arm/kernel/pmu.c
> [...]
> > @@ -73,6 +86,11 @@ enum arm_pmu_type armpmu_device_type(struct
> platform_device *pdev)
> > return (enum arm_pmu_type) of_id->data;
> > }
> >
> > + /* Provided by platform_device_id table */
> > + if ((pdev_id = platform_get_device_id(pdev))) {
>
> scripts/checkpatch.pl should warn about using = in the *if*
> statement...
>
> > + return (enum arm_pmu_type) pdev_id->driver_data;
> > + }
>
> scripts/checkpatch.pl should warn about unneeded {} here.
> Did you run your patch thru it?
>
> WBR, Sergei
Thanks, will fix in v2 along with any other issues.
Mark.
next prev parent reply other threads:[~2011-06-13 12:41 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 ` [PATCH 0/4] ARM: pmu: improve PMU type identification Mark Rutland
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 [this message]
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='000001cc29c7$2c0222f0$840668d0$@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).