Hi Joerg,
I have taken the liberty of refreshing the series you have posted
based on my testing and review comments. My unit tests are passing
now with the series. I have summarized the changes below and also
outlined the changes in each patch.
Laurent,
I cannot test the OMAP3 ISP, so request you to verify that the
OMAP3ISP driver functionality is maintained. I have created the
last patch separately for now since it's a separate subsystem,
but ideally I think it should go with the patch that adds the
iommu-group support. I am not sure how we want to merge this
patch.
Changes in v3:
* Added 3 new patches
- The first patch now results in the OMAP IOMMU devices being
probed before the callbacks kick in. This allowed me to go
back and use the patches from v1 where the IOMMU groups are
added in probe.
- The second patch drops the non-DT IOMMU device support so
that the name can be dropped from the platform data as well.
- Patch 7 fixes the OMAP3ISP driver after the addition of the
IOMMU group support.
* Squashed the "iommu/omap: Set dev->archdata.iommu = NULL in
omap_iommu_remove_device" patch into Patch 4
* Failure path cleanups in patches 4, 5 and 6
Changes in v2:
* Dropped patch 2 and moved device-link and
group-handling to attach/detach_dev call-backs for
now.
Joerg Roedel (4):
iommu/omap: Move data structures to omap-iommu.h
iommu/omap: Store iommu_dev pointer in arch_data
iommu/omap: Make use of 'struct iommu_device'
iommu/omap: Add iommu-group support
Suman Anna (3):
iommu/omap: Register driver before setting IOMMU ops
iommu/omap: Drop legacy-style device support
[media] omap3isp: Remove iommu_group related code
drivers/iommu/omap-iommu.c | 190 ++++++++++++++++++++-----------
drivers/iommu/omap-iommu.h | 34 ++++++
drivers/media/platform/omap3isp/isp.c | 17 ---
drivers/media/platform/omap3isp/isp.h | 1 -
include/linux/platform_data/iommu-omap.h | 20 ----
5 files changed, 156 insertions(+), 106 deletions(-)
--
2.12.0
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
