From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/5] arm: specify PMU type in platform data
Date: Mon, 2 Feb 2015 16:51:30 +0000 [thread overview]
Message-ID: <20150202165130.GH21175@leverpostej> (raw)
In-Reply-To: <20150121143028.GG5044@leverpostej>
[adding arm at kernel.org]
Arnd/Olof, are you happy to take these?
Everything has been appropriately acked, and as mentioned below the
series can also be found on my kernel.org tree:
git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git arm/perf/platform-updates
Thanks,
Mark.
On Wed, Jan 21, 2015 at 02:30:28PM +0000, Mark Rutland wrote:
> On Wed, Jan 21, 2015 at 12:17:18AM +0000, Simon Horman wrote:
> > On Tue, Jan 20, 2015 at 04:07:24PM +0000, Mark Rutland wrote:
> > > Currently the ARMv6, ARMv7, and XScale PMU drivers are coupled with each
> > > other, and all included in the same c file. To enable the splitting of
> > > the ARMv6, ARMv7, and XScale PMU drivers, and the conversion of the
> > > arm_pmu framework to a pure library, we need to be a be more precise
> > > when describing PMUs, to enable association of the PMU with the right
> > > driver. In device tree this is already implicit in the compatible
> > > string, but platform data currently only specifies "arm-pmu".
> > >
> > > Commit 253d8c3d2518ca6f (arm: perf: add more specific platform device
> > > IDs) added "armv6-pmu", "armv7-pmu", and "xscale-pmu" platform device
> > > IDs, enabling the three to be distinguished. This series updates
> > > platform code to use these strings.
> > >
> > > A later patch series will decouple the drivers.
> > >
> > > Since v1 [1]:
> > > * Rebase to v3.19-rc4.
> > > * Add Acks.
> > > * Drop vexpress patches (platform code deleted).
> > >
> > > Simon, in v1 you mentioned you were happy to take the shmobile patch
> > > through your tree. Are you still happy to do so, or to give your ack
> > > such that these can go through arm-soc together?
> > >
> > > While I'm not too concerned which route these patches take, it would be
> > > nice to have a single base for the patches splitting the drivers.
> >
> > Hi Mark,
> >
> > assuming that this is targeted at v3.20 then it looks like your
> > changes do not conflict with anything I have queued up and
> > I am not likely to queue anything more up for the files in question
> > for that release. As my main concern is about conflicts I'm therefore
> > quite happy for you to take the shmobile patch through your tree.
> > I'll supply an ack accordingly.
>
> Thanks, Simon, it's much appreciated.
>
> Arnd, Olof, are you happy to pick this up for v3.20? I believe all the
> patches have now been appropriately acked.
>
> If it makes things any easier I've placed the series (with new acks) on
> my arm/perf/platform-updates branch [2], based atop of v3.19-rc4.
>
> Thanks,
> Mark.
>
> [2] git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git arm/perf/platform-updates
>
> >
> > > Thanks,
> > > Mark.
> > >
> > > [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/304078.html
> > >
> > > Mark Rutland (5):
> > > arm: realview: specify PMU types
> > > arm: pxa: specify PMUs are for XScale CPUs
> > > arm: iop: specify PMUs are for XScale CPUs
> > > arm: shmobile: specify PMUs are for ARMv7 CPUs
> > > arm: omap: specify PMUs are for ARMv7 CPUs
> > >
> > > arch/arm/mach-omap2/pmu.c | 5 +++--
> > > arch/arm/mach-pxa/devices.c | 2 +-
> > > arch/arm/mach-realview/realview_eb.c | 3 ++-
> > > arch/arm/mach-realview/realview_pb1176.c | 2 +-
> > > arch/arm/mach-realview/realview_pb11mp.c | 2 +-
> > > arch/arm/mach-realview/realview_pba8.c | 2 +-
> > > arch/arm/mach-realview/realview_pbx.c | 2 +-
> > > arch/arm/mach-shmobile/setup-r8a7740.c | 2 +-
> > > arch/arm/mach-shmobile/setup-sh73a0.c | 2 +-
> > > arch/arm/plat-iop/pmu.c | 2 +-
> > > 10 files changed, 13 insertions(+), 11 deletions(-)
> > >
> > > --
> > > 1.9.1
> > >
> > >
> > > _______________________________________________
> > > linux-arm-kernel mailing list
> > > linux-arm-kernel at lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> > >
> >
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2015-02-02 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 16:07 [PATCHv2 0/5] arm: specify PMU type in platform data Mark Rutland
2015-01-20 16:07 ` [PATCHv2 1/5] arm: realview: specify PMU types Mark Rutland
2015-01-20 16:07 ` [PATCHv2 2/5] arm: pxa: specify PMUs are for XScale CPUs Mark Rutland
2015-01-20 16:07 ` [PATCHv2 3/5] arm: iop: " Mark Rutland
2015-01-20 16:07 ` [PATCHv2 4/5] arm: shmobile: specify PMUs are for ARMv7 CPUs Mark Rutland
2015-01-21 0:17 ` Simon Horman
2015-01-20 16:07 ` [PATCHv2 5/5] arm: omap: " Mark Rutland
2015-01-20 17:16 ` Tony Lindgren
2015-01-21 0:17 ` [PATCHv2 0/5] arm: specify PMU type in platform data Simon Horman
2015-01-21 14:30 ` Mark Rutland
2015-02-02 16:51 ` Mark Rutland [this message]
2015-02-06 8:13 ` 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=20150202165130.GH21175@leverpostej \
--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 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.