summaryrefslogtreecommitdiffstats
path: root/drivers/iommu/omap-iommu.c
diff options
context:
space:
mode:
authorThierry Reding <treding@nvidia.com>2015-02-06 11:44:05 +0100
committerJoerg Roedel <jroedel@suse.de>2015-02-25 13:40:52 +0100
commita7b67cd5d9afb94fdcacb71b43066b8d70d1d218 (patch)
tree74f1a6d6dbeee860f6ac299125fb771e3225cf8e /drivers/iommu/omap-iommu.c
parent367bd978b81c2c7bcdcacdd3156645a27fab0676 (diff)
downloadop-kernel-dev-a7b67cd5d9afb94fdcacb71b43066b8d70d1d218.zip
op-kernel-dev-a7b67cd5d9afb94fdcacb71b43066b8d70d1d218.tar.gz
iommu/exynos: Play nice in multi-platform builds
The Exynos System MMU driver unconditionally executes code and registers a struct iommu_ops with the platform bus irrespective of whether it runs on an Exynos SoC or not. This causes problems in multi-platform kernels where drivers for other SoCs will no longer be able to register their own struct iommu_ops or even try to use a struct iommu_ops for an IOMMU that obviously isn't there. The smallest fix I could think of is to check for the existence of any Exynos System MMU devices in the device tree and skip initialization otherwise. This fixes a problem on Tegra20 where the DRM driver will try to use the obviously non-existent Exynos System MMU. Reported-by: Nicolas Chauvet <kwizart@gmail.com> Cc: Kukjin Kim <kgene@kernel.org> Signed-off-by: Thierry Reding <treding@nvidia.com> Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/iommu/omap-iommu.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud