From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/13] arm-cci: PMU driver updates for 4.6
Date: Tue, 23 Feb 2016 11:40:03 +0000 [thread overview]
Message-ID: <20160223114003.GF3966@arm.com> (raw)
In-Reply-To: <1456224595-3282-1-git-send-email-suzuki.poulose@arm.com>
On Tue, Feb 23, 2016 at 10:49:42AM +0000, Suzuki K Poulose wrote:
> Here are some fixes and updates for arm-cci pmu driver targeting v4.6,
> applies on top of v4.5-rc5.
>
> Highlights include :
> - Support for CoreLink CCI-550 PMU
> - Reliable writes to PMU Counter registers for CCI-500/550.
>
> All the patches have been Acked. Please let me know how this
> can be merged.
>
> Andrzej Hajda (1):
> arm-cci: fix handling cpumask_any_but return value
>
> Mark Rutland (1):
> arm-cci: simplify sysfs attr handling
>
> Suzuki K Poulose (11):
> arm-cci: Group writes to counter
> arm-cci: Refactor CCI PMU enable/disable methods
> arm-cci: Delay PMU counter writes to pmu::pmu_enable
> arm-cci: write_counter: Remove redundant check
> arm-cci: Get the status of a counter
> arm-cci: Add routines to save/restore all counters
> arm-cci: Add helper to enable PMU without synchornising counters
> arm-cci: Provide hook for writing to PMU counters
> arm-cci: CCI-500: Work around PMU counter writes
> arm-cci500: Rearrange PMU driver for code sharing with CCI-550 PMU
> arm-cci: CoreLink CCI-550 PMU driver
>
> Documentation/devicetree/bindings/arm/cci.txt | 2 +
> drivers/bus/Kconfig | 10 +-
> drivers/bus/arm-cci.c | 612 +++++++++++++++++--------
> 3 files changed, 427 insertions(+), 197 deletions(-)
How do you plan to merge this? I can take it all onto a branch for
arm-soc, or I can include it on my perf/updates branch, or ...?
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, arm@kernel.org,
arnd@arndb.de, olof@lixom.net, punit.agrawal@arm.com,
mark.rutland@arm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/13] arm-cci: PMU driver updates for 4.6
Date: Tue, 23 Feb 2016 11:40:03 +0000 [thread overview]
Message-ID: <20160223114003.GF3966@arm.com> (raw)
In-Reply-To: <1456224595-3282-1-git-send-email-suzuki.poulose@arm.com>
On Tue, Feb 23, 2016 at 10:49:42AM +0000, Suzuki K Poulose wrote:
> Here are some fixes and updates for arm-cci pmu driver targeting v4.6,
> applies on top of v4.5-rc5.
>
> Highlights include :
> - Support for CoreLink CCI-550 PMU
> - Reliable writes to PMU Counter registers for CCI-500/550.
>
> All the patches have been Acked. Please let me know how this
> can be merged.
>
> Andrzej Hajda (1):
> arm-cci: fix handling cpumask_any_but return value
>
> Mark Rutland (1):
> arm-cci: simplify sysfs attr handling
>
> Suzuki K Poulose (11):
> arm-cci: Group writes to counter
> arm-cci: Refactor CCI PMU enable/disable methods
> arm-cci: Delay PMU counter writes to pmu::pmu_enable
> arm-cci: write_counter: Remove redundant check
> arm-cci: Get the status of a counter
> arm-cci: Add routines to save/restore all counters
> arm-cci: Add helper to enable PMU without synchornising counters
> arm-cci: Provide hook for writing to PMU counters
> arm-cci: CCI-500: Work around PMU counter writes
> arm-cci500: Rearrange PMU driver for code sharing with CCI-550 PMU
> arm-cci: CoreLink CCI-550 PMU driver
>
> Documentation/devicetree/bindings/arm/cci.txt | 2 +
> drivers/bus/Kconfig | 10 +-
> drivers/bus/arm-cci.c | 612 +++++++++++++++++--------
> 3 files changed, 427 insertions(+), 197 deletions(-)
How do you plan to merge this? I can take it all onto a branch for
arm-soc, or I can include it on my perf/updates branch, or ...?
Will
next prev parent reply other threads:[~2016-02-23 11:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 10:49 [PATCH 00/13] arm-cci: PMU driver updates for 4.6 Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 01/13] arm-cci: simplify sysfs attr handling Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 02/13] arm-cci: fix handling cpumask_any_but return value Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 03/13] arm-cci: Group writes to counter Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 04/13] arm-cci: Refactor CCI PMU enable/disable methods Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 05/13] arm-cci: Delay PMU counter writes to pmu::pmu_enable Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 06/13] arm-cci: write_counter: Remove redundant check Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 07/13] arm-cci: Get the status of a counter Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 08/13] arm-cci: Add routines to save/restore all counters Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 09/13] arm-cci: Add helper to enable PMU without synchornising counters Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 10/13] arm-cci: Provide hook for writing to PMU counters Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 11/13] arm-cci: CCI-500: Work around PMU counter writes Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 12/13] arm-cci500: Rearrange PMU driver for code sharing with CCI-550 PMU Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 10:49 ` [PATCH 13/13] arm-cci: CoreLink CCI-550 PMU driver Suzuki K Poulose
2016-02-23 10:49 ` Suzuki K Poulose
2016-02-23 11:40 ` Will Deacon [this message]
2016-02-23 11:40 ` [PATCH 00/13] arm-cci: PMU driver updates for 4.6 Will Deacon
2016-02-23 13:55 ` Suzuki K. Poulose
2016-02-23 13:55 ` Suzuki K. Poulose
2016-02-24 16:58 ` Olof Johansson
2016-02-24 16:58 ` Olof Johansson
2016-02-24 17:12 ` Will Deacon
2016-02-24 17:12 ` Will Deacon
2016-02-24 18:46 ` Olof Johansson
2016-02-24 18:46 ` Olof Johansson
2016-02-26 16:48 ` Will Deacon
2016-02-26 16:48 ` Will Deacon
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=20160223114003.GF3966@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 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.