From: ashoks@broadcom.com (Ashok Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/6] arm64: dts: Add Broadcom Vulcan PMU in dts
Date: Mon, 28 Mar 2016 05:23:42 -0700 [thread overview]
Message-ID: <1459167823-487-6-git-send-email-ashoks@broadcom.com> (raw)
In-Reply-To: <1459167823-487-1-git-send-email-ashoks@broadcom.com>
Add "brcm,vulcan-pmu" compatible string for Broadcom Vulcan PMU.
Signed-off-by: Ashok Kumar <ashoks@broadcom.com>
---
arch/arm64/boot/dts/broadcom/vulcan.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/broadcom/vulcan.dtsi b/arch/arm64/boot/dts/broadcom/vulcan.dtsi
index 85820e2..34e11a9 100644
--- a/arch/arm64/boot/dts/broadcom/vulcan.dtsi
+++ b/arch/arm64/boot/dts/broadcom/vulcan.dtsi
@@ -86,7 +86,7 @@
};
pmu {
- compatible = "arm,armv8-pmuv3";
+ compatible = "brcm,vulcan-pmu", "arm,armv8-pmuv3";
interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>; /* PMU overflow */
};
--
2.1.0
next prev parent reply other threads:[~2016-03-28 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 12:23 [PATCH v3 0/6] arm64: perf: Broadcom Vulcan PMU support Ashok Kumar
2016-03-28 12:23 ` [PATCH v3 1/6] arm64/perf: Changed events naming as per ARM ARM Ashok Kumar
2016-03-28 12:23 ` [PATCH v3 2/6] arm64/perf: Define complete ARMv8 recommended implementation defined events Ashok Kumar
2016-03-28 12:23 ` [PATCH v3 3/6] arm64/perf: Filter common events based on PMCEIDn_EL0 Ashok Kumar
2016-03-28 12:23 ` [PATCH v3 4/6] arm64/perf: Add Broadcom Vulcan PMU support Ashok Kumar
2016-03-28 12:23 ` Ashok Kumar [this message]
2016-03-28 12:23 ` [PATCH v3 6/6] Documentation: arm64: pmu: Add Broadcom Vulcan PMU binding Ashok Kumar
2016-03-28 22:04 ` Rob Herring
2016-04-04 11:51 ` [PATCH v3 0/6] arm64: perf: Broadcom Vulcan PMU support Ashok Kumar
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=1459167823-487-6-git-send-email-ashoks@broadcom.com \
--to=ashoks@broadcom.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.