summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorWill Deacon <will.deacon@arm.com>2011-07-26 22:10:28 +0100
committerWill Deacon <will.deacon@arm.com>2011-08-31 10:17:59 +0100
commitb0e89590f4f27ea5ff30bdedb9a58ea904a6b353 (patch)
tree8d81a0d268dd6780e4c5a7cfa4b9c49708afebc7 /scripts
parenta6c93afed38c242ccf4ec5bcb5ff26ff2521cf36 (diff)
downloadop-kernel-dev-b0e89590f4f27ea5ff30bdedb9a58ea904a6b353.zip
op-kernel-dev-b0e89590f4f27ea5ff30bdedb9a58ea904a6b353.tar.gz
ARM: PMU: move CPU PMU platform device handling and init into perf
Once upon a time, OProfile and Perf fought hard over who could play with the PMU. To stop all hell from breaking loose, pmu.c offered an internal reserve/release API and took care of parsing PMU platform data passed in from board support code. Now that Perf has ingested OProfile, let's move the platform device handling into the Perf driver and out of the PMU locking code. Unfortunately, the lock has to remain to prevent Perf being bitten by out-of-tree modules such as LTTng, which still claim a right to the PMU when Perf isn't looking. Acked-by: Jamie Iles <jamie@jamieiles.com> Reviewed-by: Jean Pihet <j-pihet@ti.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud