From: Ashok Kumar <ashoks@broadcom.com>
To: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
mark.rutland@arm.com, will.deacon@arm.com,
Suzuki.Poulose@arm.com, robh+dt@kernel.org,
catalin.marinas@arm.com
Cc: jchandra@broadcom.com, Ashok Kumar <ashoks@broadcom.com>,
jglauber@cavium.com
Subject: [PATCH v4 2/6] arm64: dts: Add Broadcom Vulcan PMU in dts
Date: Mon, 11 Apr 2016 06:02:17 -0700 [thread overview]
Message-ID: <1460379741-1181-3-git-send-email-ashoks@broadcom.com> (raw)
In-Reply-To: <1460379741-1181-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 c49b5a8..03dd845 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-04-11 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 13:02 [PATCH v4 0/6] arm64: perf: Broadcom Vulcan PMU support Ashok Kumar
2016-04-11 13:02 ` [PATCH v4 1/6] Documentation: arm64: pmu: Add Broadcom Vulcan PMU binding Ashok Kumar
[not found] ` <1460379741-1181-2-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-04-13 14:33 ` Rob Herring
2016-04-11 13:02 ` Ashok Kumar [this message]
2016-04-11 13:02 ` [PATCH v4 4/6] arm64/perf: Define complete ARMv8 recommended implementation defined events Ashok Kumar
2016-04-11 13:02 ` [PATCH v4 5/6] arm64/perf: Filter common events based on PMCEIDn_EL0 Ashok Kumar
2016-04-11 13:02 ` [PATCH v4 6/6] arm64/perf: Add Broadcom Vulcan PMU support Ashok Kumar
[not found] ` <1460379741-1181-1-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-04-11 13:02 ` [PATCH v4 3/6] arm64/perf: Changed events naming as per ARM ARM Ashok Kumar
2016-04-11 15:34 ` [PATCH v4 0/6] arm64: perf: Broadcom Vulcan PMU support Jan Glauber
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=1460379741-1181-3-git-send-email-ashoks@broadcom.com \
--to=ashoks@broadcom.com \
--cc=Suzuki.Poulose@arm.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jchandra@broadcom.com \
--cc=jglauber@cavium.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.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).