diff options
author | Ohad Ben-Cohen <[email protected]> | 2012-02-22 10:52:51 +0200 |
---|---|---|
committer | Joerg Roedel <[email protected]> | 2012-02-24 14:10:50 +0100 |
commit | 46451d6229723ce1428c69e5b4f3308a775473fd (patch) | |
tree | 2c44c2c6ee8789a9ce7ecd87dc9de9b70e84b81d /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 05df1f3c2afaef5672627f2b7095f0d4c4dbc3a0 (diff) |
iommu/omap: fix erroneous omap-iommu-debug API calls
Adapt omap-iommu-debug to the latest omap-iommu API changes, which
were introduced by commit fabdbca "iommu/omap: eliminate the public
omap_find_iommu_device() method".
In a nutshell, iommu users are not expected to provide the omap_iommu
handle anymore - instead, iommus are attached using their user's device
handle.
omap-iommu-debug is a hybrid beast though: it invokes both public and
private omap iommu API, so fix it as necessary (otherwise a crash
is imminent).
Note: omap-iommu-debug is a bit disturbing, as it fiddles with internal
omap iommu data and requires exposing API which is otherwise not needed.
It should better be more tightly coupled with omap-iommu, to prevent
further bit rot and avoid exposing redundant API. Naturally that's out
of scope for the -rc cycle, so for now just fix the obvious.
Reported-by: Russell King <[email protected]>
Signed-off-by: Ohad Ben-Cohen <[email protected]>
Cc: Tony Lindgren <[email protected]>
Cc: Hiroshi Doyu <[email protected]>
Cc: Laurent Pinchart <[email protected]>
Cc: Joerg Roedel <[email protected]>
Signed-off-by: Joerg Roedel <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions