Re: [PATCH v13 1/3] dt-bindings: perf: Add Broadcom Raspberry Pi AXI PMU definition
Uwe Kleine-König <[email protected]>
| Newsgroups | org.kernel.vger.linux-perf-users,dev.linux.lists.sashiko-reviews |
|---|---|
| Message-ID | <aoDZrWaC20bfc2jX@monoceros> |
On Sat, Aug 15, 2026 at 05:30:49PM +0000, [email protected] wrote: > > Add Device Tree bindings for the Broadcom AXI PMU hardware blocks present > > in the Raspberry Pi SoC line (BCM2835, BCM2711, BCM2712). > > > > Depending on the SoC and security configuration, these PMUs support either > > direct MMIO access or routing via the Raspberry Pi firmware Mailbox IPC. > > The bindings support defining 1 or 2 backing MMIO regions natively map > > the system and VPU control surfaces. > > > > Assisted-by: Antigravity:gemini-3.6-flash > > Signed-off-by: Ian Rogers <[email protected]> > > Sashiko has reviewed this patch and found no issues. It looks great! While Sashiko doesn't find issues any more, checkpatch still does. It (rightfully!) criticizes usage of LINUX_VERSION_CODE which is unsuitable for mainline inclusion. Florian already pointed that out in reply to v10 or v11 (these two versions were not marked with a vX and I don't feel like doing the detective work to find that out. Usually you can see that using the Date they were sent, but they were sent on the same day and both in reply to v9 (which was also sent the same day 🙄)). Sad Ian knew better and continued using LINUX_VERSION_CODE. :-( Best regards Uwe
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmqA3JwACgkQj4D7WH0S /k7vGAgAh9OCi5rmtHL/MLTSp+jox4z83Dr/Oz5u4Sf4Fu/1aEN07NgJdZFpZd7d mkVkEbHsHb6kdOzrr+VOHA1kkc6Eiz9VuXkFuC/qgFW9OHPp/hmYcTtOXSF1jGEN zApJE8qSeau6iuGcC18uHn8ygprg1asloNf9+prmTe1iS/M9di+oDRSq8M5mk5Mp r60LrdKZim+gtGnlzN/2s9FlgJEZwdxtI5MCjWOfZFgjTi9vjEFbvGY0idXLrEO8 aMSmWdgk+nrS0u3GiXsXiVJo+/cAn+ZcEfkfxUFMaKtnkQhccktg+7AYDGGUpFv6 w9pOo+QPuGcbpuXYV+1KOU9NzkuBDQ== =Xlbr -----END PGP SIGNATURE-----