From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: r8a7795: pmu: switch to Cortex specific device nodes
Date: Fri, 05 Feb 2016 09:54:45 +0000 [thread overview]
Message-ID: <20160205095445.GD16556@verge.net.au> (raw)
In-Reply-To: <56B236F4.4090409@gmail.com>
[CC shiny new linux-renesas-soc ML]
On Wed, Feb 03, 2016 at 06:20:52PM +0100, Dirk Behme wrote:
> On 16.01.2016 15:13, Dirk Behme wrote:
> >Instead of using the generic armv8-pmuv3 compatibility use the more
> >specific Cortex A57 compatibility.
> >
> >Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
> >---
> >Changes in v2: Drop the not yet merged Cortex A53 part.
> >
> > arch/arm64/boot/dts/renesas/r8a7795.dtsi | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> >diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> >index 266c5de..a82bce8 100644
> >--- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> >+++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
> >@@ -247,8 +247,8 @@
> > power-domains = <&cpg>;
> > };
> >
> >- pmu {
> >- compatible = "arm,armv8-pmuv3";
> >+ pmu_a57 {
> >+ compatible = "arm,cortex-a57-pmu";
> > interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>,
> > <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>,
> > <GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>,
> >
>
>
> Any further comments to this? If not, could this be applied?
Hi Dirk,
I apologise for loosing track of this one.
Does this change work? I saw some discussion about using arm,cortex-a57-pmu
not working correctly on the r8a7795 in an earlier thread.
next prev parent reply other threads:[~2016-02-05 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 14:13 [PATCH v2] arm64: dts: r8a7795: pmu: switch to Cortex specific device nodes Dirk Behme
2016-02-03 17:20 ` Dirk Behme
2016-02-05 9:54 ` Simon Horman [this message]
2016-02-05 10:03 ` Dirk Behme
2016-02-08 9:21 ` Simon Horman
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=20160205095445.GD16556@verge.net.au \
--to=horms@verge.net.au \
--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;
as well as URLs for NNTP newsgroup(s).