Hi Thierry,

On 02/06/2015 04:44 AM, Thierry Reding wrote:
> From: Thierry Reding <[email protected]>
> 
> Hi Joerg,
> 
> Here are a couple of urgent fixes for a regression on old Tegra devices
> related to IOMMU support. The issue is that many drivers think it's a
> good idea to register IOMMU support unconditionally, which is not the
> smart thing to do at all on multi-platform kernels. This probably went
> unnoticed for a while because the offending drivers aren't enabled in
> any of the multi-platform default configurations. Fedora ARM has their
> own config where the offending drivers did get enabled, hence caused a
> regression on Tegra20. I would expect the same regression to exist on a
> number of other SoCs, possibly all that support IOMMU.
> 
> I've tried to keep the patches minimal in the hopes of still getting
> this into v3.19-rc8 or the final release to avoid the regression.
> 
> Changes in v2:
> - avoid potential leak by dropping references to device tree nodes
> - remove fixups from module exit functions since they are unused

Thanks for the revised patches, tested them on the OMAP platforms. I was
not able to apply the iommu/msm patch though against 3.19-rc7 cleanly.

regards
Suman

> Thierry
> 
> Thierry Reding (4):
>   iommu/exynos: Play nice in multi-platform builds
>   iommu/omap: Play nice in multi-platform builds
>   iommu/rockchip: Play nice in multi-platform builds
>   iommu/msm: Mark driver BROKEN
> 
>  drivers/iommu/Kconfig          | 1 +
>  drivers/iommu/exynos-iommu.c   | 7 +++++++
>  drivers/iommu/omap-iommu.c     | 7 +++++++
>  drivers/iommu/rockchip-iommu.c | 7 +++++++
>  4 files changed, 22 insertions(+)
> 

_______________________________________________
iommu mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/iommu

Reply via email to