From: Nick Chan <towinchenmi@gmail.com>
To: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Janne Grunau <j@jannau.net>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Neal Gompa <neal@gompa.dev>, Sven Peter <sven@kernel.org>
Cc: Marc Zyngier <maz@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, devicetree@vger.kernel.org,
asahi@lists.linux.dev, linux-kernel@vger.kernel.org,
Nick Chan <towinchenmi@gmail.com>
Subject: [PATCH v8 06/21] drivers/perf: apple_m1: Support per-implementation PMU startup
Date: Mon, 11 Aug 2025 21:54:38 +0800 [thread overview]
Message-ID: <20250811-apple-cpmu-v8-6-c560ebd9ca46@gmail.com> (raw)
In-Reply-To: <20250811-apple-cpmu-v8-0-c560ebd9ca46@gmail.com>
Support for implementations that deliver its interrupts in ways other than
FIQ will be added, which requires a per-implementation startup function.
Signed-off-by: Nick Chan <towinchenmi@gmail.com>
---
drivers/perf/apple_m1_cpu_pmu.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/perf/apple_m1_cpu_pmu.c b/drivers/perf/apple_m1_cpu_pmu.c
index fb2759069fe9e47146f0342fa46e40f3ab836926..303c0e62432281e899a33fc197365c70078d6ac1 100644
--- a/drivers/perf/apple_m1_cpu_pmu.c
+++ b/drivers/perf/apple_m1_cpu_pmu.c
@@ -659,7 +659,6 @@ static int apple_pmu_init(struct arm_pmu *cpu_pmu, u32 counters)
cpu_pmu->read_counter = m1_pmu_read_counter;
cpu_pmu->write_counter = m1_pmu_write_counter;
cpu_pmu->clear_event_idx = m1_pmu_clear_event_idx;
- cpu_pmu->start = m1_pmu_start;
cpu_pmu->stop = m1_pmu_stop;
cpu_pmu->set_event_filter = m1_pmu_set_event_filter;
@@ -681,6 +680,7 @@ static int m1_pmu_ice_init(struct arm_pmu *cpu_pmu)
cpu_pmu->get_event_idx = m1_pmu_get_event_idx;
cpu_pmu->map_event = m1_pmu_map_event;
cpu_pmu->reset = m1_pmu_reset;
+ cpu_pmu->start = m1_pmu_start;
return apple_pmu_init(cpu_pmu, M1_PMU_NR_COUNTERS);
}
@@ -690,6 +690,7 @@ static int m1_pmu_fire_init(struct arm_pmu *cpu_pmu)
cpu_pmu->get_event_idx = m1_pmu_get_event_idx;
cpu_pmu->map_event = m1_pmu_map_event;
cpu_pmu->reset = m1_pmu_reset;
+ cpu_pmu->start = m1_pmu_start;
return apple_pmu_init(cpu_pmu, M1_PMU_NR_COUNTERS);
}
@@ -699,6 +700,7 @@ static int m2_pmu_avalanche_init(struct arm_pmu *cpu_pmu)
cpu_pmu->get_event_idx = m1_pmu_get_event_idx;
cpu_pmu->map_event = m2_pmu_map_event;
cpu_pmu->reset = m1_pmu_reset;
+ cpu_pmu->start = m1_pmu_start;
return apple_pmu_init(cpu_pmu, M1_PMU_NR_COUNTERS);
}
@@ -708,6 +710,7 @@ static int m2_pmu_blizzard_init(struct arm_pmu *cpu_pmu)
cpu_pmu->get_event_idx = m1_pmu_get_event_idx;
cpu_pmu->map_event = m2_pmu_map_event;
cpu_pmu->reset = m1_pmu_reset;
+ cpu_pmu->start = m1_pmu_start;
return apple_pmu_init(cpu_pmu, M1_PMU_NR_COUNTERS);
}
--
2.50.1
next prev parent reply other threads:[~2025-08-11 13:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 13:54 [PATCH v8 00/21] drivers/perf: apple_m1: Add Apple A7-A11, T2 SoC support Nick Chan
2025-08-11 13:54 ` [PATCH v8 01/21] dt-bindings: arm: pmu: Add Apple A7-A11 SoC CPU PMU compatibles Nick Chan
2025-08-11 13:54 ` [PATCH v8 02/21] drivers/perf: apple_m1: Only init PMUv3 remap when EL2 is available Nick Chan
2025-08-11 13:54 ` [PATCH v8 03/21] drivers/perf: apple_m1: Support per-implementation event tables Nick Chan
2025-08-11 13:54 ` [PATCH v8 04/21] drivers/perf: apple_m1: Support a per-implementation number of counters Nick Chan
2025-08-11 13:54 ` [PATCH v8 05/21] drivers/perf: apple_m1: Support configuring counters for 32-bit EL0 Nick Chan
2025-08-11 13:54 ` Nick Chan [this message]
2025-08-11 13:54 ` [PATCH v8 07/21] drivers/perf: apple_m1: Support per-implementation event attr group Nick Chan
2025-08-11 13:54 ` [PATCH v8 08/21] drivers/perf: apple_m1: Add Apple A7 support Nick Chan
2025-08-11 13:54 ` [PATCH v8 09/21] drivers/perf: apple_m1: Add Apple A8/A8X support Nick Chan
2025-08-11 13:54 ` [PATCH v8 10/21] drivers/perf: apple_m1: Add A9/A9X support Nick Chan
2025-08-11 13:54 ` [PATCH v8 11/21] drivers/perf: apple_m1: Add Apple A10/A10X/T2 Support Nick Chan
2025-08-11 13:54 ` [PATCH v8 12/21] drivers/perf: apple_m1: Add Apple A11 Support Nick Chan
2025-08-11 13:54 ` [PATCH v8 13/21] arm64: dts: apple: s5l8960x: Add CPU PMU nodes Nick Chan
2025-08-11 13:54 ` [PATCH v8 14/21] arm64: dts: apple: t7000: " Nick Chan
2025-08-11 13:54 ` [PATCH v8 15/21] arm64: dts: apple: t7001: " Nick Chan
2025-08-11 13:54 ` [PATCH v8 16/21] arm64: dts: apple: s800-0-3: " Nick Chan
2025-08-11 13:54 ` [PATCH v8 17/21] arm64: dts: apple: s8001: " Nick Chan
2025-08-11 13:54 ` [PATCH v8 18/21] arm64: dts: apple: t8010: " Nick Chan
2025-08-11 13:54 ` [PATCH v8 19/21] arm64: dts: apple: t8011: " Nick Chan
2025-08-11 13:54 ` [PATCH v8 20/21] arm64: dts: apple: t8012: " Nick Chan
2025-08-11 13:54 ` [PATCH v8 21/21] arm64: dts: apple: t8015: " Nick Chan
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=20250811-apple-cpmu-v8-6-c560ebd9ca46@gmail.com \
--to=towinchenmi@gmail.com \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j@jannau.net \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=neal@gompa.dev \
--cc=robh@kernel.org \
--cc=sven@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).