From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 4/5] arm: shmobile: specify PMUs are for ARMv7 CPUs
Date: Wed, 21 Jan 2015 09:17:59 +0900 [thread overview]
Message-ID: <20150121001758.GC338@verge.net.au> (raw)
In-Reply-To: <1421770049-32029-5-git-send-email-mark.rutland@arm.com>
On Tue, Jan 20, 2015 at 04:07:28PM +0000, Mark Rutland wrote:
> Now that we can specify which PMU variant we're likely to deal with, do
> so in the shmobile board code. This will allow us to split the ARMv6,
> ARMv7, and XScale PMU drivers
>
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Magnus Damm <magnus.damm@gmail.com>
> Cc: Olof Johansson <olof@lixom.net>
> Cc: Simon Horman <horms@verge.net.au>
Tested-by: Simon Horman <horms+renesas@verge.net.au>
Acked-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> arch/arm/mach-shmobile/setup-r8a7740.c | 2 +-
> arch/arm/mach-shmobile/setup-sh73a0.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-shmobile/setup-r8a7740.c b/arch/arm/mach-shmobile/setup-r8a7740.c
> index 79ad93d..6edde2f 100644
> --- a/arch/arm/mach-shmobile/setup-r8a7740.c
> +++ b/arch/arm/mach-shmobile/setup-r8a7740.c
> @@ -656,7 +656,7 @@ static struct resource pmu_resources[] = {
> };
>
> static struct platform_device pmu_device = {
> - .name = "arm-pmu",
> + .name = "armv7-pmu",
> .id = -1,
> .num_resources = ARRAY_SIZE(pmu_resources),
> .resource = pmu_resources,
> diff --git a/arch/arm/mach-shmobile/setup-sh73a0.c b/arch/arm/mach-shmobile/setup-sh73a0.c
> index 93ebe34..bdfa7a5 100644
> --- a/arch/arm/mach-shmobile/setup-sh73a0.c
> +++ b/arch/arm/mach-shmobile/setup-sh73a0.c
> @@ -563,7 +563,7 @@ static struct resource pmu_resources[] = {
> };
>
> static struct platform_device pmu_device = {
> - .name = "arm-pmu",
> + .name = "armv7-pmu",
> .id = -1,
> .num_resources = ARRAY_SIZE(pmu_resources),
> .resource = pmu_resources,
> --
> 1.9.1
>
>
> _______________________________________________
> 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-01-21 0:17 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 [this message]
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
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=20150121001758.GC338@verge.net.au \
--to=horms@verge.net.au \
--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.