From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v16 2/3] perf: Add Raspberry Pi BCM2835 AXI PMU driver
Date: Tue, 03 Nov 2026 04:29:39 +0000 [thread overview]
Message-ID: <sashiko-outbox-194566@kernel.org> (raw)
In-Reply-To: <20261103041416.2940213-3-irogers@google.com>
> Add a PMU driver for the Raspberry Pi AXI performance monitors. It
> provides access to the System and VideoCore performance counters on
> Broadcom BCM2835 and BCM2711 platforms natively through the perf
> subsystem.
>
> The driver implements bus-watcher refcounting, group validation, CPU
> hotplug migration, and sysfs event aliases mapping hardware-specific
> events to AXI pipelines (such as DMA, V3D, HVS, and ISP). Memory-mapped
> endpoints for the primary System bus are read synchronously, while the
> VideoCore VPU monitor is polled asynchronously in process context via a
> single bulk Raspberry Pi firmware mailbox read across all active bus
> watchers.
>
> Co-developed-by: Dom Cobley <popcornmix@gmail.com>
> Signed-off-by: Dom Cobley <popcornmix@gmail.com>
> Signed-off-by: Ian Rogers <irogers@google.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103041416.2940213-1-irogers@google.com?part=2
next prev parent reply other threads:[~2026-11-03 4:29 UTC|newest]
Thread overview: 8+ 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 4:19 ` sashiko-bot
2026-11-03 9:24 ` Krzysztof Kozlowski
2026-11-03 4:14 ` [PATCH v16 2/3] perf: Add Raspberry Pi BCM2835 AXI PMU driver Ian Rogers
2026-11-03 4:29 ` sashiko-bot [this message]
2026-11-03 4:14 ` [PATCH v16 3/3] perf: Add Raspberry Pi 5 (BCM2712) AXI PMU support Ian Rogers
2026-11-03 4:18 ` sashiko-bot
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=sashiko-outbox-194566@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.