From: Mark Rutland <mark.rutland@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] perf: pmuv3: Add Cortex-A520, Cortex-A715, and Cortex-A720 PMUs
Date: Mon, 3 Jul 2023 11:09:35 +0100 [thread overview]
Message-ID: <ZKKeX4LU0_8qpTxk@FVFF77S0Q05N> (raw)
In-Reply-To: <20230630185602.2175559-2-robh@kernel.org>
On Fri, Jun 30, 2023 at 12:56:02PM -0600, Rob Herring wrote:
> Add support for the Arm Cortex-A520, Cortex-A715, and Cortex-A720 CPU
> PMUs. They are straight-forward additions with just new compatible
> strings.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> drivers/perf/arm_pmuv3.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/perf/arm_pmuv3.c b/drivers/perf/arm_pmuv3.c
> index 08b3a1bf0ef6..0bf522b05dc3 100644
> --- a/drivers/perf/arm_pmuv3.c
> +++ b/drivers/perf/arm_pmuv3.c
> @@ -1266,7 +1266,10 @@ PMUV3_INIT_SIMPLE(armv8_cortex_a76)
> PMUV3_INIT_SIMPLE(armv8_cortex_a77)
> PMUV3_INIT_SIMPLE(armv8_cortex_a78)
> PMUV3_INIT_SIMPLE(armv9_cortex_a510)
> +PMUV3_INIT_SIMPLE(armv9_cortex_a520)
> PMUV3_INIT_SIMPLE(armv9_cortex_a710)
> +PMUV3_INIT_SIMPLE(armv9_cortex_a715)
> +PMUV3_INIT_SIMPLE(armv9_cortex_a720)
> PMUV3_INIT_SIMPLE(armv8_cortex_x1)
> PMUV3_INIT_SIMPLE(armv9_cortex_x2)
> PMUV3_INIT_SIMPLE(armv8_neoverse_e1)
> @@ -1334,7 +1337,10 @@ static const struct of_device_id armv8_pmu_of_device_ids[] = {
> {.compatible = "arm,cortex-a77-pmu", .data = armv8_cortex_a77_pmu_init},
> {.compatible = "arm,cortex-a78-pmu", .data = armv8_cortex_a78_pmu_init},
> {.compatible = "arm,cortex-a510-pmu", .data = armv9_cortex_a510_pmu_init},
> + {.compatible = "arm,cortex-a520-pmu", .data = armv9_cortex_a520_pmu_init},
> {.compatible = "arm,cortex-a710-pmu", .data = armv9_cortex_a710_pmu_init},
> + {.compatible = "arm,cortex-a715-pmu", .data = armv9_cortex_a715_pmu_init},
> + {.compatible = "arm,cortex-a720-pmu", .data = armv9_cortex_a720_pmu_init},
> {.compatible = "arm,cortex-x1-pmu", .data = armv8_cortex_x1_pmu_init},
> {.compatible = "arm,cortex-x2-pmu", .data = armv9_cortex_x2_pmu_init},
> {.compatible = "arm,neoverse-e1-pmu", .data = armv8_neoverse_e1_pmu_init},
> --
> 2.40.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:[~2023-07-03 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 18:56 [PATCH 1/2] dt-bindings: arm: pmu: Add Cortex-A520, Cortex-A715, and Cortex-A720 Rob Herring
2023-06-30 18:56 ` [PATCH 2/2] perf: pmuv3: Add Cortex-A520, Cortex-A715, and Cortex-A720 PMUs Rob Herring
2023-07-03 10:09 ` Mark Rutland [this message]
2023-07-03 16:07 ` [PATCH 1/2] dt-bindings: arm: pmu: Add Cortex-A520, Cortex-A715, and Cortex-A720 Conor Dooley
2023-07-03 19:40 ` Robin Murphy
2023-07-05 21:40 ` 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=ZKKeX4LU0_8qpTxk@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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