From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ian Rogers <irogers@google.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>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Dom Cobley" <popcornmix@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Stefan Wahren" <wahrenst@gmx.net>, "Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
linux-perf-users@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v16 1/3] dt-bindings: perf: Add Broadcom Raspberry Pi AXI PMU definition
Date: Tue, 3 Nov 2026 10:24:56 +0100 [thread overview]
Message-ID: <20261103-electronic-teal-kraken-5ebcec@quoll> (raw)
In-Reply-To: <20261103041416.2940213-2-irogers@google.com>
On Mon, Nov 02, 2026 at 08:14:14PM -0800, Ian Rogers wrote:
> Add device tree bindings for the Broadcom Raspberry Pi AXI PMU block
> found on BCM2835, BCM2711, and BCM2712 SoCs.
>
> Depending on the SoC and security configuration, these PMUs support
> either direct MMIO access for the System monitor or routing via the
> Raspberry Pi firmware mailbox IPC for the VideoCore VPU monitor.
In such case, where is mboxes property?
>
> Co-developed-by: Dom Cobley <popcornmix@gmail.com>
> Signed-off-by: Dom Cobley <popcornmix@gmail.com>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> .../bindings/perf/brcm,bcm2835-axiperf.yaml | 50 +++++++++++++++++++
> MAINTAINERS | 7 +++
> 2 files changed, 57 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/perf/brcm,bcm2835-axiperf.yaml
...
> +description: |
Do not need '|' unless you need to preserve formatting.
> + The Broadcom BCM2835 series (including BCM2711 and BCM2712) features hardware
> + performance monitors on the AXI bus for evaluating memory bandwidth and
> + system traffic. Two monitor register blocks are present: the primary monitor
> + evaluates the System fabric, while the secondary monitor evaluates the
> + VideoCore VPU fabric. This block is distinct from the BCM5301X AXI Trace
> + Module.
> +
> +properties:
> + compatible:
> + enum:
> + - brcm,bcm2711-axiperf
> + - brcm,bcm2712-axiperf
> + - brcm,bcm2835-axiperf
> +
> + reg:
> + items:
> + - description: System monitor registers
> + - description: VPU monitor registers
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + pmu@7e009800 {
> + compatible = "brcm,bcm2835-axiperf";
> + reg = <0x7e009800 0x100>,
> + <0x7ee08000 0x100>;
> + };
> + - |
> + pmu@7c012800 {
> + compatible = "brcm,bcm2712-axiperf";
> + reg = <0x7c012800 0x100>,
> + <0x7ee00000 0x100>;
> + };
Drop the second example, redundant. They are the same.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-03 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 4:14 [PATCH v16 0/3] perf: Add Raspberry Pi AXI PMU driver Ian Rogers
2026-11-03 4:14 ` [PATCH v16 1/3] dt-bindings: perf: Add Broadcom Raspberry Pi AXI PMU definition Ian Rogers
2026-11-03 9:24 ` Krzysztof Kozlowski [this message]
2026-11-03 4:14 ` [PATCH v16 2/3] perf: Add Raspberry Pi BCM2835 AXI PMU driver Ian Rogers
2026-11-03 4:14 ` [PATCH v16 3/3] perf: Add Raspberry Pi 5 (BCM2712) AXI PMU support Ian Rogers
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=20261103-electronic-teal-kraken-5ebcec@quoll \
--to=krzk@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=irogers@google.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=popcornmix@gmail.com \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=wahrenst@gmx.net \
--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
all inboxes | Powered by JetHome®