From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm-cci500: Rearrange PMU driver for code sharing with CCI-550 PMU
Date: Thu, 10 Dec 2015 15:44:55 +0000 [thread overview]
Message-ID: <20151210154454.GH495@leverpostej> (raw)
In-Reply-To: <1447785040-18599-2-git-send-email-suzuki.poulose@arm.com>
On Tue, Nov 17, 2015 at 06:30:39PM +0000, Suzuki K. Poulose wrote:
> CCI-550 PMU shares most of the CCI-500 PMU attributes including the
> event format, PMU event codes. The only difference is an additional
> master interface (MI6 - 0xe). Hence we share the driver code for both,
> except for a model specific event validate method.
> This patch renames the common CCI500 symbols to CCI5xx, including the
> Kconfig symbol.
>
> No functional changes to the PMU driver.
>
> Cc: Punit Agrawal <punit.agrawal@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Suzuki K. Poulose <suzuki.poulose@arm.com>
> ---
> drivers/bus/Kconfig | 2 +-
> drivers/bus/arm-cci.c | 218 +++++++++++++++++++++++++------------------------
> 2 files changed, 112 insertions(+), 108 deletions(-)
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: "Suzuki K. Poulose" <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, arm@kernel.org,
punit.agrawal@arm.com
Subject: Re: [PATCH 1/2] arm-cci500: Rearrange PMU driver for code sharing with CCI-550 PMU
Date: Thu, 10 Dec 2015 15:44:55 +0000 [thread overview]
Message-ID: <20151210154454.GH495@leverpostej> (raw)
In-Reply-To: <1447785040-18599-2-git-send-email-suzuki.poulose@arm.com>
On Tue, Nov 17, 2015 at 06:30:39PM +0000, Suzuki K. Poulose wrote:
> CCI-550 PMU shares most of the CCI-500 PMU attributes including the
> event format, PMU event codes. The only difference is an additional
> master interface (MI6 - 0xe). Hence we share the driver code for both,
> except for a model specific event validate method.
> This patch renames the common CCI500 symbols to CCI5xx, including the
> Kconfig symbol.
>
> No functional changes to the PMU driver.
>
> Cc: Punit Agrawal <punit.agrawal@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Suzuki K. Poulose <suzuki.poulose@arm.com>
> ---
> drivers/bus/Kconfig | 2 +-
> drivers/bus/arm-cci.c | 218 +++++++++++++++++++++++++------------------------
> 2 files changed, 112 insertions(+), 108 deletions(-)
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
next prev parent reply other threads:[~2015-12-10 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 18:30 [PATCH 0/2] ARM CoreLink CCI-550 PMU driver Suzuki K. Poulose
2015-11-17 18:30 ` Suzuki K. Poulose
2015-11-17 18:30 ` [PATCH 1/2] arm-cci500: Rearrange PMU driver for code sharing with CCI-550 PMU Suzuki K. Poulose
2015-11-17 18:30 ` Suzuki K. Poulose
2015-12-10 15:44 ` Mark Rutland [this message]
2015-12-10 15:44 ` Mark Rutland
2015-12-16 16:55 ` Punit Agrawal
2015-12-16 16:55 ` Punit Agrawal
2015-11-17 18:30 ` [PATCH 2/2] arm-cci: CoreLink CCI-550 PMU driver Suzuki K. Poulose
2015-11-17 18:30 ` Suzuki K. Poulose
2015-12-10 15:46 ` Mark Rutland
2015-12-10 15:46 ` Mark Rutland
2015-12-16 17:00 ` Punit Agrawal
2015-12-16 17:00 ` Punit Agrawal
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=20151210154454.GH495@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.