Arm interconnect PMU driver tidyup
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest posting 2/20 of 6 patches 0 repliesNew
- v2 posting 1/26 patches 0 repliesSuperseded
- v15 patches 0 repliesSuperseded
Patches in v2 posting 2/2 No applies recorded yet
None of the 6 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/6] Arm interconnect PMU driver tidyup
Hi Arnd,
Quoted 7 lines · Arnd Bergmann
Quoted 6 lines · Robin Murphy
Hi arm-soc folks,
PLease consider this series tidying up the Arm interconnect code in
drivers/busto separate the PMU parts out intodrivers/perfwhere Will and Mark can handle future maintenance more easily.
Quoted 5 lines
Quoted 3 lines
FWIW, the patches are also available on a branch here:
git://linux-arm.org/linux-rm.gitperfThis is not a signed tag, so I applied the patches manually to the drivers
Yes, that was merely a convenience branch for reviewers; I see actual pull requests as being for maintainers, whereas I'm just some oik ;)
Quoted 5 lines
branch. To add to the bike-shedding, I would have preferred a different approach over the auxdata array, either exporting a function based interface, or calling
ioremap()on the physical address multiple times, but each of those has other downsides, so your version seems good enough.
Yeah, all of the options were pretty horrible, but this one was about the most concise and didn't need to introduce any new infrastructure. We have this "PMU as a child of some other device" issue coming up on various other IP blocks as well; the resource claiming conflicts seem to get in the way the most.
Thanks for applying!
Robin.