From: Conor Dooley <conor@kernel.org>
To: Eric Lin <eric.lin@sifive.com>
Cc: 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>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Atish Patra <atishp@rivosinc.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Nick Hu <nick.hu@sifive.com>
Subject: Re: [PATCH RFC] dt-bindings: perf: riscv,pmu: Add interrupts-extended property
Date: Thu, 8 Oct 2026 11:22:02 +0100 [thread overview]
Message-ID: <20261008-e035806a0c080bb90eafb6a7@squawk> (raw)
In-Reply-To: <20260702-pmu-dt-property-v1-1-a7a7737afb72@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 2753 bytes --]
On Thu, Jul 02, 2026 at 05:04:31PM +0800, Eric Lin wrote:
> The interrupts-extended property is used to specify the connection
> between the PMU counter overflow interrupt and the corresponding CPU
> local interrupt controller (riscv,cpu-intc).
>
> This property also allows the software to associate a PMU node with a
> specific CPU. To support future heterogeneous systems, where different
> CPUs may support different PMU events, this property allows the driver
> to identify the correct PMU capabilities for each hart.
>
> Reviewed-by: Nick Hu <nick.hu@sifive.com>
> Signed-off-by: Eric Lin <eric.lin@sifive.com>
This has been sitting for ages, I was kinda waiting to see if there'd be
some feedback from the relevant maintainers (riscv pmu). Was there a
series sent to opensbi or elsewhere to implement support for these
devices?
Thanks,
Conor.
> ---
> Documentation/devicetree/bindings/perf/riscv,pmu.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/perf/riscv,pmu.yaml b/Documentation/devicetree/bindings/perf/riscv,pmu.yaml
> index d01c677ad3c7..13aceb3d42b9 100644
> --- a/Documentation/devicetree/bindings/perf/riscv,pmu.yaml
> +++ b/Documentation/devicetree/bindings/perf/riscv,pmu.yaml
> @@ -34,6 +34,13 @@ properties:
> compatible:
> const: riscv,pmu
>
> + interrupts-extended:
> + minItems: 1
> + maxItems: 4095
> + description:
> + Specifies the interrupt-parent and local interrupt index for each CPU's
> + PMU counter overflow. Each item points to a riscv,cpu-intc node.
> +
> riscv,event-to-mhpmevent:
> $ref: /schemas/types.yaml#/definitions/uint32-matrix
> description:
> @@ -101,6 +108,7 @@ examples:
> - |
> pmu {
> compatible = "riscv,pmu";
> + interrupts-extended = <&cpu0_intc 13>;
> riscv,event-to-mhpmevent = <0x0000B 0x0000 0x0001>;
> riscv,event-to-mhpmcounters = <0x00001 0x00001 0x00000001>,
> <0x00002 0x00002 0x00000004>,
> @@ -127,6 +135,9 @@ examples:
> */
> pmu {
> compatible = "riscv,pmu";
> + interrupts-extended = <&cpu0_intc 13>,
> + <&cpu1_intc 13>,<&cpu2_intc 13>,
> + <&cpu3_intc 13>,<&cpu4_intc 13>;
> riscv,event-to-mhpmevent =
> /* SBI_PMU_HW_CACHE_REFERENCES -> Instruction or Data cache/ITIM busy */
> <0x00003 0x00000000 0x1801>,
>
> ---
> base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
> change-id: 20260701-pmu-dt-property-ff12b35fe0fc
>
> Best regards,
> --
> Eric Lin <eric.lin@sifive.com>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-10-08 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:04 [PATCH RFC] dt-bindings: perf: riscv,pmu: Add interrupts-extended property Eric Lin
2026-07-02 9:16 ` sashiko-bot
2026-10-08 10:22 ` Conor Dooley [this message]
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=20261008-e035806a0c080bb90eafb6a7@squawk \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eric.lin@sifive.com \
--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=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nick.hu@sifive.com \
--cc=palmer@dabbelt.com \
--cc=pjw@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