All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Neil Leeder <nleeder@codeaurora.org>,
	Ashwin Chaugule <ashwinc@codeaurora.org>,
	Ashwin Chaugule <ashwin.chaugule@linaro.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Sheetal Sahasrabudhe <sheetals@codeaurora.org>
Subject: Re: [PATCH v3 0/3] Scorpion PMU support
Date: Mon, 2 Mar 2015 18:24:24 +0000	[thread overview]
Message-ID: <20150302182424.GE7919@arm.com> (raw)
In-Reply-To: <1425082295-10941-1-git-send-email-sboyd@codeaurora.org>

On Sat, Feb 28, 2015 at 12:11:32AM +0000, Stephen Boyd wrote:
> These patches add support for the Scorpion PMU found on devices
> such as msm8660, qsd8x50, etc. The first patch is some groundwork
> to make functions more "generic". Even then we end up copying quite
> a bit of code from the Krait part into the Scorpion part with only
> subtle tweaks because two things happen:
> 
>  1. We gain another "region" register, L2LPM
>  2. The way to access the region registers are with different cp15 instructions
> 
> I'm not sure how to make this better, suggestions are welcome. The second
> patch is an optimization for an implementation defined register. The 
> final patch is the one that actually adds support for Scorpion.
> 
> Changes from v2:
>  * New patch 2
>  * Macros instead of an inline function for patch 1

Thanks, Stephen. I'll queue this for 4.1.

Will

WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] Scorpion PMU support
Date: Mon, 2 Mar 2015 18:24:24 +0000	[thread overview]
Message-ID: <20150302182424.GE7919@arm.com> (raw)
In-Reply-To: <1425082295-10941-1-git-send-email-sboyd@codeaurora.org>

On Sat, Feb 28, 2015 at 12:11:32AM +0000, Stephen Boyd wrote:
> These patches add support for the Scorpion PMU found on devices
> such as msm8660, qsd8x50, etc. The first patch is some groundwork
> to make functions more "generic". Even then we end up copying quite
> a bit of code from the Krait part into the Scorpion part with only
> subtle tweaks because two things happen:
> 
>  1. We gain another "region" register, L2LPM
>  2. The way to access the region registers are with different cp15 instructions
> 
> I'm not sure how to make this better, suggestions are welcome. The second
> patch is an optimization for an implementation defined register. The 
> final patch is the one that actually adds support for Scorpion.
> 
> Changes from v2:
>  * New patch 2
>  * Macros instead of an inline function for patch 1

Thanks, Stephen. I'll queue this for 4.1.

Will

  parent reply	other threads:[~2015-03-02 18:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28  0:11 [PATCH v3 0/3] Scorpion PMU support Stephen Boyd
2015-02-28  0:11 ` Stephen Boyd
2015-02-28  0:11 ` [PATCH v3 1/3] ARM: perf: Preparatory work for " Stephen Boyd
2015-02-28  0:11   ` Stephen Boyd
2015-02-28  0:11 ` [PATCH v3 2/3] ARM: perf: Only reset PMxEVCNTCR registers on reset Stephen Boyd
2015-02-28  0:11   ` Stephen Boyd
2015-02-28  0:11 ` [PATCH v3 3/3] ARM: perf: Add support for Scorpion PMUs Stephen Boyd
2015-02-28  0:11   ` Stephen Boyd
2015-02-28  0:11   ` Stephen Boyd
2015-03-02 18:24 ` Will Deacon [this message]
2015-03-02 18:24   ` [PATCH v3 0/3] Scorpion PMU support 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=20150302182424.GE7919@arm.com \
    --to=will.deacon@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=ashwin.chaugule@linaro.org \
    --cc=ashwinc@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nleeder@codeaurora.org \
    --cc=sboyd@codeaurora.org \
    --cc=sheetals@codeaurora.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.