devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Nicolas Pitre <nico@linaro.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Kukjin Kim <kgene@kernel.org>,
	Abhilash Kesavan <a.kesavan@samsung.com>,
	Arnd Bergmann <arnd@arndb.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
	Olof Johansson <olof@lixom.net>, Pawel Moll <Pawel.Moll@arm.com>,
	Punit Agrawal <Punit.Agrawal@arm.com>,
	Sudeep Holla <Sudeep.Holla@arm.com>,
	Catalin Marinas <Catalin.Marinas@arm.com>
Subject: Re: [PATCHv3 0/5] arm-cci400: PMU monitoring support on ARM64
Date: Wed, 18 Mar 2015 10:09:49 +0000	[thread overview]
Message-ID: <55094EED.6060804@arm.com> (raw)
In-Reply-To: <20150317185449.GF8399@arm.com>

On 17/03/15 18:54, Will Deacon wrote:
> On Tue, Mar 10, 2015 at 03:18:50PM +0000, Suzuki K. Poulose wrote:
>> From: "Suzuki K. Poulose" <suzuki.poulose@arm.com>
>>
>> This series enables the PMU monitoring support for CCI400 on ARM64.
>> The existing CCI400 driver code is a mix of PMU driver and the MCPM
>> driver code. The MCPM driver is only used on ARM(32) and contains
>> arm32 assembly and hence can't be built on ARM64. This patch splits
>> the code to
>>
>>   - ARM_CCI400_PORT_CTRL driver - depends on ARM && V7
>>   - ARM_CCI400_PMU driver
>
> If you repost this with acks added and my feedback addressed, then I'm
> happy to put together a branch for arm-soc along with your other CCI PMU
> fix for event validation.

Sure, I will do that.

Thanks
Suzuki

>
> Will
>

      reply	other threads:[~2015-03-18 10:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 15:18 [PATCHv3 0/5] arm-cci400: PMU monitoring support on ARM64 Suzuki K. Poulose
2015-03-10 15:18 ` [PATCH 1/5] arm-cci: Rearrange code for splitting PMU vs driver code Suzuki K. Poulose
     [not found] ` <1426000735-14375-1-git-send-email-suzuki.poulose-5wv7dgnIgG8@public.gmane.org>
2015-03-10 15:18   ` [PATCH 2/5] arm-cci: Abstract the CCI400 PMU speicific definitions Suzuki K. Poulose
     [not found]     ` <1426000735-14375-3-git-send-email-suzuki.poulose-5wv7dgnIgG8@public.gmane.org>
2015-03-17 18:49       ` Will Deacon
2015-03-10 16:09   ` [PATCHv3 0/5] arm-cci400: PMU monitoring support on ARM64 Nicolas Pitre
2015-03-10 16:11     ` Suzuki K. Poulose
2015-03-11 11:40   ` Punit Agrawal
2015-03-10 15:18 ` [PATCH 3/5] arm-cci: Get rid of secure transactions for PMU driver Suzuki K. Poulose
2015-03-17  9:51   ` [UPDATED] " Suzuki K. Poulose
2015-03-19 17:25     ` Mark Rutland
     [not found]     ` <1426585901-19137-1-git-send-email-suzuki.poulose-5wv7dgnIgG8@public.gmane.org>
2015-03-19 17:32       ` Mark Rutland
2015-03-19 17:38         ` Sudeep Holla
2015-03-19 17:52           ` Suzuki K. Poulose
     [not found]             ` <550B0CF6.8070205-5wv7dgnIgG8@public.gmane.org>
2015-03-19 17:54               ` Mark Rutland
2015-03-10 15:18 ` [PATCH 4/5] arm-cci: Split the code for PMU vs driver support Suzuki K. Poulose
     [not found]   ` <1426000735-14375-5-git-send-email-suzuki.poulose-5wv7dgnIgG8@public.gmane.org>
2015-03-10 16:24     ` Sudeep Holla
2015-03-10 15:18 ` [PATCH 5/5] arm-cci: Fix CCI PMU event validation Suzuki K. Poulose
     [not found]   ` <1426000735-14375-6-git-send-email-suzuki.poulose-5wv7dgnIgG8@public.gmane.org>
2015-03-17 18:52     ` Will Deacon
2015-03-10 16:21 ` [PATCHv3 0/5] arm-cci400: PMU monitoring support on ARM64 Sudeep Holla
2015-03-10 16:24   ` Suzuki K. Poulose
2015-03-17 18:54 ` Will Deacon
2015-03-18 10:09   ` 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=55094EED.6060804@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=Pawel.Moll@arm.com \
    --cc=Punit.Agrawal@arm.com \
    --cc=Sudeep.Holla@arm.com \
    --cc=a.kesavan@samsung.com \
    --cc=arnd@arndb.de \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kgene@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@linaro.org \
    --cc=olof@lixom.net \
    --cc=will.deacon@arm.com \
    /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).