From: Thierry Reding <thierry.reding@gmail.com>
To: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] arm64: perf: Support Denver and Carmel PMUs
Date: Tue, 7 Dec 2021 16:07:45 +0100 [thread overview]
Message-ID: <20211207150746.444478-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20211207150746.444478-1-thierry.reding@gmail.com>
From: Thierry Reding <treding@nvidia.com>
Add support for the NVIDIA Denver and Carmel PMUs using the generic
PMUv3 event map for now.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
arch/arm64/kernel/perf_event.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c
index b4044469527e..8c8cf369c450 100644
--- a/arch/arm64/kernel/perf_event.c
+++ b/arch/arm64/kernel/perf_event.c
@@ -1247,6 +1247,18 @@ static int armv8_vulcan_pmu_init(struct arm_pmu *cpu_pmu)
armv8_vulcan_map_event);
}
+static int armv8_denver_pmu_init(struct arm_pmu *cpu_pmu)
+{
+ return armv8_pmu_init_nogroups(cpu_pmu, "armv8_nvidia_denver",
+ armv8_pmuv3_map_event);
+}
+
+static int armv8_carmel_pmu_init(struct arm_pmu *cpu_pmu)
+{
+ return armv8_pmu_init_nogroups(cpu_pmu, "armv8_nvidia_carmel",
+ armv8_pmuv3_map_event);
+}
+
static const struct of_device_id armv8_pmu_of_device_ids[] = {
{.compatible = "arm,armv8-pmuv3", .data = armv8_pmuv3_init},
{.compatible = "arm,cortex-a34-pmu", .data = armv8_a34_pmu_init},
@@ -1265,6 +1277,8 @@ static const struct of_device_id armv8_pmu_of_device_ids[] = {
{.compatible = "arm,neoverse-n1-pmu", .data = armv8_n1_pmu_init},
{.compatible = "cavium,thunder-pmu", .data = armv8_thunder_pmu_init},
{.compatible = "brcm,vulcan-pmu", .data = armv8_vulcan_pmu_init},
+ {.compatible = "nvidia,denver-pmu", .data = armv8_denver_pmu_init},
+ {.compatible = "nvidia,carmel-pmu", .data = armv8_carmel_pmu_init},
{},
};
--
2.33.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-12-07 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 15:07 [PATCH 1/3] dt-bindings: arm: pmu: Document Denver and Carmel PMUs Thierry Reding
2021-12-07 15:07 ` Thierry Reding [this message]
2021-12-07 16:03 ` [PATCH 2/3] arm64: perf: Support " Mark Rutland
2021-12-08 14:36 ` Thierry Reding
2021-12-14 12:33 ` Will Deacon
2021-12-14 14:28 ` Thierry Reding
2021-12-14 14:36 ` Will Deacon
2021-12-07 15:07 ` [PATCH 3/3] arm64: tegra: Drop arm,armv8-pmuv3 compatible string Thierry Reding
2021-12-08 13:44 ` [PATCH 1/3] dt-bindings: arm: pmu: Document Denver and Carmel PMUs Rob Herring
2021-12-08 14:41 ` Thierry Reding
2021-12-08 17:06 ` Rob Herring
2021-12-08 18:51 ` Rob Herring
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=20211207150746.444478-2-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=will@kernel.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).