devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@gmail.com>
To: linux-sh@vger.kernel.org, horms@verge.net.au, geert+renesas@glider.be
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Yoshifumi Hosoya <yoshifumi.hosoya.wj@renesas.com>,
	Masaru Nagai <masaru.nagai.vx@renesas.com>
Subject: [PATCH 3/3] arm64: dts: r8a7795: Add pmu device nodes
Date: Fri,  4 Dec 2015 14:38:53 +0100	[thread overview]
Message-ID: <1449236333-4410-3-git-send-email-dirk.behme@gmail.com> (raw)
In-Reply-To: <1449236333-4410-1-git-send-email-dirk.behme@gmail.com>

From: Yoshifumi Hosoya <yoshifumi.hosoya.wj@renesas.com>

Enabling the performance monitor unit on r8a7795.

Signed-off-by: Masaru Nagai <masaru.nagai.vx@renesas.com>
Signed-off-by: Yoshifumi Hosoya <yoshifumi.hosoya.wj@renesas.com>
Sigend-off-by: Dirk Behme <dirk.behme@gmail.com>
---
Note: This patch picked from

https://git.kernel.org/cgit/linux/kernel/git/horms/renesas-bsp.git/log/?h=v4.2/rcar-3.0.x

and rebased against

https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git/log/?h=topic/gen3-latest renesas-drivers-2015-12-01-v4.4-rc3

 arch/arm64/boot/dts/renesas/r8a7795.dtsi | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/arch/arm64/boot/dts/renesas/r8a7795.dtsi b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
index 946a5bb..8113b71 100644
--- a/arch/arm64/boot/dts/renesas/r8a7795.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a7795.dtsi
@@ -247,6 +247,18 @@
 			power-domains = <&cpg>;
 		};
 
+		pmu {
+			compatible = "arm,armv8-pmuv3";
+			interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>,
+				     <GIC_SPI 73 IRQ_TYPE_LEVEL_HIGH>,
+				     <GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>,
+				     <GIC_SPI 75 IRQ_TYPE_LEVEL_HIGH>;
+			interrupt-affinity = <&a57_0>,
+					     <&a57_1>,
+					     <&a57_2>,
+					     <&a57_3>;
+		};
+
 		timer {
 			compatible = "arm,armv8-timer";
 			interrupts = <GIC_PPI 13
-- 
2.6.3


  parent reply	other threads:[~2015-12-04 13:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 13:38 [PATCH 1/3] arm64: dts: r8a7795: Add PSCI node Dirk Behme
2015-12-04 13:38 ` [PATCH 2/3] arm64: dts: r8a7795: Add Cortex-A57 CPU cores Dirk Behme
2015-12-11 23:07   ` Simon Horman
2015-12-15  5:12     ` Simon Horman
2015-12-15  6:31       ` Dirk Behme
2015-12-15  8:23       ` Geert Uytterhoeven
2015-12-15  8:38     ` Magnus Damm
2015-12-15  8:48       ` Dirk Behme
2015-12-15  8:55         ` Magnus Damm
2016-03-16  1:19         ` Simon Horman
2016-03-16  3:45           ` Khiem Nguyen
2016-03-16  5:36             ` Simon Horman
2015-12-04 13:38 ` Dirk Behme [this message]
2015-12-11 23:07   ` [PATCH 3/3] arm64: dts: r8a7795: Add pmu device nodes Simon Horman
     [not found]   ` <1449236333-4410-3-git-send-email-dirk.behme-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-14 14:36     ` Sudeep Holla
2015-12-15  8:33       ` Geert Uytterhoeven
2015-12-15  9:50         ` Sudeep Holla
2015-12-11 23:07 ` [PATCH 1/3] arm64: dts: r8a7795: Add PSCI node 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=1449236333-4410-3-git-send-email-dirk.behme@gmail.com \
    --to=dirk.behme@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=masaru.nagai.vx@renesas.com \
    --cc=yoshifumi.hosoya.wj@renesas.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).