[PATCH 3/4] iommu/rockchip: Play nice in multi-platform builds

2015-02-03 Thread Thierry Reding
From: Thierry Reding The Rockchip IOMMU driver unconditionally executes code and registers a struct iommu_ops with the platform bus irrespective of whether it runs on a Rockchip SoC or not. This causes problems in multi-platform kernels where drivers for other SoCs will no longer be able to regis

[PATCH 1/4] iommu/exynos: Play nice in multi-platform builds

2015-02-03 Thread Thierry Reding
From: Thierry Reding 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 reg

[PATCH 0/4] iommu: A couple of urgent fixes

2015-02-03 Thread Thierry Reding
From: Thierry Reding 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. T

[PATCH 4/4] iommu/msm: Mark driver BROKEN

2015-02-03 Thread Thierry Reding
From: Thierry Reding The MSM IOMMU driver unconditionally calls bus_set_iommu(), which is a very stupid thing to do on multi-platform kernels. While marking the driver BROKEN may seem a little extreme, there is no other way to make the driver skip initialization. One of the problems is that it do

[PATCH 2/4] iommu/omap: Play nice in multi-platform builds

2015-02-03 Thread Thierry Reding
From: Thierry Reding The OMAP IOMMU driver unconditionally executes code and registers a struct iommu_ops with the platform bus irrespective of whether it runs on an OMAP SoC or not. This causes problems in multi-platform kernels where drivers for other SoCs will no longer be able to register the

Re: [PATCH] iommu: arm-smmu: avoid build warning

2015-02-03 Thread j...@8bytes.org
On Mon, Feb 02, 2015 at 10:20:49AM +, Will Deacon wrote: > On Fri, Jan 30, 2015 at 09:55:55PM +, Arnd Bergmann wrote: > > - reg = (iova & ~0xfff) >> 32; > > + reg = ((u64)iova & ~0xfff) >> 32; > > writel_relaxed(reg, cb_base + ARM_SMMU_CB_ATS1PR_HI); > >

Re: [PATCH 00/26] iommu/fsl: Various cleanup

2015-02-03 Thread Joerg Roedel
On Sat, Jan 31, 2015 at 11:58:58AM -0600, Timur Tabi wrote: > These should all be merged into one patch, IMHO. I agree, it makes more sense to put all this into a single patch. Applied this way. ___ iommu mailing list iommu@lists.linux-foundation.org htt

Re: [PATCH 2/4] iommu/exynos: Make driver depend on REGULATOR

2015-02-03 Thread Marek Szyprowski
Hello, On 2015-01-27 00:50, Joerg Roedel wrote: From: Joerg Roedel When regulator is not selected during kconfig, linking of the exynos iommu driver fails due to missing symbols. Fix it! Frankly, I never observed such issue. Could you provide the .config for such case? I know that existing

Re: [PATCH 3/5] iommu: Limit iommu_attach/detach_device to devices with their own group

2015-02-03 Thread Joerg Roedel
On Tue, Feb 03, 2015 at 01:25:07PM +0100, Thierry Reding wrote: > Sorry for my ignorance, but I don't understand what IOMMU groups are > supposed to be or how to make use of them. It seems like a common idiom > is to simply allocate a new group and add a device to it in the IOMMU's > ->add_device()

Re: [PATCH 3/5] iommu: Limit iommu_attach/detach_device to devices with their own group

2015-02-03 Thread Thierry Reding
On Tue, Jan 27, 2015 at 01:08:57AM +0100, Joerg Roedel wrote: > From: Joerg Roedel > > This patch changes the behavior of the iommu_attach_device > and iommu_detach_device functions. With this change these > functions only work on devices that have their own group. > For all other devices the iom