From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm-cci PMU updates for 4.1
Date: Thu, 2 Apr 2015 15:33:35 +0100 [thread overview]
Message-ID: <20150402143332.GE9719@arm.com> (raw)
In-Reply-To: <20150327172500.GO1562@arm.com>
On Fri, Mar 27, 2015 at 05:25:00PM +0000, Will Deacon wrote:
> Hi Olof, Arnd,
>
> Please can you pull the following ARM CCI PMU updates for 4.1? Suzuki
> has reworked parts of the existing driver so that it can be used on CPUs
> booting in non-secure mode (i.e. ARM64 systems) and also make it easier
> to port over to new IP, such as CCI-500.
>
> It's coming via me as $ARM_PERF_GUY, but Nico has Acked the core driver
> (non-PMU) changes. Note that these have been in next for a bit, but I
> can drop the branch once you've pulled.
Gentle ping as I'm off all next week and won't be able to chase this up...
Will
> --->8
>
> The following changes since commit 06e5801b8cb3fc057d88cb4dc03c0b64b2744cda:
>
> Linux 4.0-rc4 (2015-03-15 17:38:20 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git tags/arm-perf-4.1
>
> for you to fetch changes up to 874c571414d5617f4042298986b6a826816ee885:
>
> arm-cci: Fix CCI PMU event validation (2015-03-27 13:45:02 +0000)
>
> ----------------------------------------------------------------
> CCI-400 PMU updates
>
> This series reworks some of the CCI-400 PMU code so that it can be used
> on both ARM and ARM64-based systems, without the need to boot in secure
> mode on the latter. This paves the way for CCI-500 support in future.
>
> ----------------------------------------------------------------
> Suzuki K. Poulose (6):
> drivers: cci: reject groups spanning multiple HW PMUs
> arm-cci: Rearrange code for splitting PMU vs driver code
> arm-cci: Abstract the CCI400 PMU specific definitions
> arm-cci: Get rid of secure transactions for PMU driver
> arm-cci: Split the code for PMU vs driver support
> arm-cci: Fix CCI PMU event validation
>
> Documentation/devicetree/bindings/arm/cci.txt | 7 +-
> arch/arm/include/asm/arm-cci.h | 42 +++
> arch/arm/mach-exynos/Kconfig | 2 +-
> arch/arm/mach-vexpress/Kconfig | 4 +-
> arch/arm64/include/asm/arm-cci.h | 27 ++
> drivers/bus/Kconfig | 28 +-
> drivers/bus/arm-cci.c | 517 +++++++++++++++-----------
> include/linux/arm-cci.h | 9 +-
> 8 files changed, 399 insertions(+), 237 deletions(-)
> create mode 100644 arch/arm/include/asm/arm-cci.h
> create mode 100644 arch/arm64/include/asm/arm-cci.h
next prev parent reply other threads:[~2015-04-02 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 17:25 [GIT PULL] arm-cci PMU updates for 4.1 Will Deacon
2015-04-02 14:33 ` Will Deacon [this message]
2015-04-03 20:40 ` Olof Johansson
2015-04-07 16:43 ` Suzuki K. Poulose
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=20150402143332.GE9719@arm.com \
--to=will.deacon@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).