diff options
| author | Tero Kristo <t-kristo@ti.com> | 2019-08-07 11:26:51 +0300 |
|---|---|---|
| committer | Joerg Roedel <jroedel@suse.de> | 2019-08-09 17:37:10 +0200 |
| commit | 604629bcb5057d778839652f8f38d23734f2fe1d (patch) | |
| tree | c9641dcd4fd6e4329cbdf8d6347d024221552f86 /drivers/iommu/omap-iommu.h | |
| parent | d9c4d8a6cc0f852adf3829fbe40e2e3f6213b0c6 (diff) | |
iommu/omap: add support for late attachment of iommu devices
Current implementation of OMAP IOMMU enforces strict ordering of device
probe, initiated by iommu and followed by remoteproc later. This doesn't
work too well with the new setup done with ti-sysc changes which may
have the devices probed at pretty much any order. To overcome this limitation,
if iommu has not been probed yet when a consumer tries to attach to it,
add the device to orphan device list which will be parsed during iommu
probe to see if any orphan devices should be attached.
Signed-off-by: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/iommu/omap-iommu.h')
| -rw-r--r-- | drivers/iommu/omap-iommu.h | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/drivers/iommu/omap-iommu.h b/drivers/iommu/omap-iommu.h index 1d15aa857634..18ee713ede78 100644 --- a/drivers/iommu/omap-iommu.h +++ b/drivers/iommu/omap-iommu.h @@ -87,7 +87,8 @@ struct omap_iommu { /** * struct omap_iommu_arch_data - omap iommu private data - * @iommu_dev: handle of the iommu device + * @iommu_dev: handle of the OMAP iommu device + * @dev: handle of the iommu device * * This is an omap iommu private data object, which binds an iommu user * to its iommu device. This object should be placed at the iommu user's @@ -96,6 +97,7 @@ struct omap_iommu { */ struct omap_iommu_arch_data { struct omap_iommu *iommu_dev; + struct device *dev; }; struct cr_regs { |