From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] arm64: dts: juno: describe PMUs separately
Date: Wed, 10 Jun 2015 10:25:36 +0100 [thread overview]
Message-ID: <20150610092536.GB1517@leverpostej> (raw)
In-Reply-To: <20150602104743.GI2175@e106497-lin.cambridge.arm.com>
On Tue, Jun 02, 2015 at 11:47:43AM +0100, Liviu Dudau wrote:
> On Tue, May 26, 2015 at 05:31:16PM +0100, Mark Rutland wrote:
> > The A57 and A53 PMUs in Juno support different events, so describe them
> > separately.
> >
> > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > Cc: Liviu Dudau <liviu.dudau@arm.com>
> > Cc: Will Deacon <will.deacon@arm.com>
>
> Hi Mark,
>
> Arnd has pulled my patches that add juno-r1.dts to the mix and he is going
> to send a pull request for v4.2. Care to respin this patch to add support
> for Juno R1 as well?
Sure. Is there a branch out there with just the juno DT patch(es) in?
The DT patch only makes sense after the code changes, and those are
currently based on Will's perf/updates branch (atop of v4.1-rc1), which
doesn't have the DT changes.
Mark.
next prev parent reply other threads:[~2015-06-10 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 16:31 [PATCH 0/6] arm64: perf: heterogeneous PMU support Mark Rutland
2015-05-26 16:31 ` [PATCH 1/6] arm64: perf: factor out callchain code Mark Rutland
2015-05-26 16:31 ` [PATCH 2/6] arm64: perf: move to shared arm_pmu framework Mark Rutland
2015-05-26 16:31 ` [PATCH 3/6] arm64: perf: condense event number maps Mark Rutland
2015-05-26 16:31 ` [PATCH 4/6] arm64: perf: add Cortex-A53 support Mark Rutland
2015-05-26 16:31 ` [PATCH 5/6] arm64: perf: add Cortex-A57 support Mark Rutland
2015-05-26 16:31 ` [PATCH 6/6] arm64: dts: juno: describe PMUs separately Mark Rutland
2015-06-02 10:47 ` Liviu Dudau
2015-06-10 9:25 ` Mark Rutland [this message]
2015-06-11 10:31 ` Liviu Dudau
2015-06-11 14:11 ` Mark Rutland
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=20150610092536.GB1517@leverpostej \
--to=mark.rutland@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