If we were to add to arm32/arm then the common event numbers and maybe other JSONs in future would need to be duplicated.
Would there be any reason to add to arm32/arm apart to from being strictly proper? Maybe if lots of other 32b support for other vendors came along then it could make sense (to separate them out).
That's the heart of the question, really. At best it seems unnecessarily confusing as-is.
AFAICS either the naming isn't functional, wherein it would potentially make the most sense to rename the whole thing "pmu-events/arch/arm" if it's merely for categorising Arm architectures in general, or it is actually tied to the host triplet, in which case the above patches are most likely useless.
I'd agree that there doesn't seem much point in trying to separate things along relatively arbitrary lines if it *isn't* functionally necessary - the PMUv2 common events look to be a straightforward subset of the PMUv3 ones, but then there's Cortex-A32 anyway, plus most of the already-supported CPUs could equally run an AArch32 perf tool as well.