ARM: pmu: improve PMU type identification
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest0 of 4 patches 0 repliesNew
Patches in v2 No applies recorded yet
None of the 4 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 [PATCHv2 0/4] ARM: pmu: improve PMU type identification
Mark,
Quoted 20 lines · Mark Rutland
Hi,
This is version 2 of the patches originally posted here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2011-June/052865.htmlChanges since v1 include:
* Added Acks from Jamie Iles & Rob Herring.
* Add "arm-pmu" binding to theplatform_device_idtable, as driver name matching is not used whenplatform_driver::id_tableexists.
* Fixed name clash inPLAT_MATCH_PMUmacro.
* Removed unnecessary casts forplatform_device_id::driver_data.
* Aligned trailing backslashes on multi-line*_MATCH_PMUmacros.
* Removed spaces after casts.The patches use {of,platform}_device_id tables to provide the PMU type, which can be used similarly (the macros make entries look identical apart from the {plat,of} prefix). This allows us to stop (ab)using
platform_device::id, and should allow for easier addition/modification of PMU driver bindings.
Quoted 7 lines
BSPs need no longer care about the Type of PMUs they register; as long as a binding exists the type will be assigned correctly.
Rob, Jamie: would you mind if patches 3 & 4 were squashed together? Patch 4 depends heavily on patch 3, and there doesn't seem to be a clean way of fixing that.
Interdependency is not really a good reason to combine patches, so I would leave them as is. Functionality wise, they are doing different things.
Rob