public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Suzuki.Poulose@arm•com (Suzuki K. Poulose)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] arm-cci PMU updates for 4.1
Date: Tue, 07 Apr 2015 17:43:33 +0100	[thread overview]
Message-ID: <55240935.9060900@arm.com> (raw)
In-Reply-To: <20150403204016.GB23023@localhost>

On 03/04/15 21:40, Olof Johansson wrote:
> 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.
>>
>> Cheers,
>>
>> 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)
>
> Merged now. The Kconfig merge was a bit messy since someone decided to sort the
> file, and Stephen will see that too (cc:d here).
>
Tested the CCI PMU on the for-next branch, works well. Thanks Olof.

Suzuki

      reply	other threads:[~2015-04-07 16:43 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
2015-04-03 20:40 ` Olof Johansson
2015-04-07 16:43   ` Suzuki K. Poulose [this message]

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=55240935.9060900@arm.com \
    --to=suzuki.poulose@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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