linux-toradex.git/include/linux/iommu.h, branch v4.13-rc5

Merge branches 'arm/exynos', 'arm/omap', 'arm/rockchip', 'arm/mediatek', 'arm/smmu', 'arm/core', 'x86/vt-d', 'x86/amd' and 'core' into next

2017-05-04T16:06:17+00:00

iommu: Remove trace-events include from iommu.h

2017-04-28T22:20:50+00:00

It is not needed there anymore. All places needing it are
fixed.

Signed-off-by: Joerg Roedel

iommu: Move report_iommu_fault() to iommu.c

2017-04-27T09:24:11+00:00

The function is in no fast-path, there is no need for it to
be static inline in a header file. This also removes the
need to include iommu trace-points in iommu.h.

Signed-off-by: Joerg Roedel

iommu: Include device.h in iommu.h

2017-04-27T09:24:10+00:00

We make use of 'struct device' in iommu.h, so include
device.h to make it available explicitly.

Re-order the other headers while at it.

Signed-off-by: Joerg Roedel

iommu: Better document the IOMMU_PRIV flag

2017-04-06T15:06:42+00:00

This is a fairly subtle thing - let's make sure it's described as
clearly as possible to avoid potential misunderstandings.

Signed-off-by: Robin Murphy 
Signed-off-by: Will Deacon

iommu: Disambiguate MSI region types

2017-03-22T15:16:17+00:00

The introduction of reserved regions has left a couple of rough edges
which we could do with sorting out sooner rather than later. Since we
are not yet addressing the potential dynamic aspect of software-managed
reservations and presenting them at arbitrary fixed addresses, it is
incongruous that we end up displaying hardware vs. software-managed MSI
regions to userspace differently, especially since ARM-based systems may
actually require one or the other, or even potentially both at once,
(which iommu-dma currently has no hope of dealing with at all). Let's
resolve the former user-visible inconsistency ASAP before the ABI has
been baked into a kernel release, in a way that also lays the groundwork
for the latter shortcoming to be addressed by follow-up patches.

For clarity, rename the software-managed type to IOMMU_RESV_SW_MSI, use
IOMMU_RESV_MSI to describe the hardware type, and document everything a
little bit. Since the x86 MSI remapping hardware falls squarely under
this meaning of IOMMU_RESV_MSI, apply that type to their regions as well,
so that we tell the same story to userspace across all platforms.

Secondly, as the various region types require quite different handling,
and it really makes little sense to ever try combining them, convert the
bitfield-esque #defines to a plain enum in the process before anyone
gets the wrong impression.

Fixes: d30ddcaa7b02 ("iommu: Add a new type field in iommu_resv_region")
Reviewed-by: Eric Auger 
CC: Alex Williamson 
CC: David Woodhouse 
CC: kvm@vger.kernel.org
Signed-off-by: Robin Murphy 
Signed-off-by: Joerg Roedel

Merge branches 'iommu/fixes', 'arm/exynos', 'arm/renesas', 'arm/smmu', 'arm/mediatek', 'arm/core', 'x86/vt-d' and 'core' into next

2017-02-10T14:13:10+00:00

iommu: Remove iommu_register_instance interface

2017-02-10T13:54:37+00:00

And also move its remaining functionality to
iommu_device_register() and 'struct iommu_device'.

Cc: Rob Herring 
Cc: Frank Rowand 
Cc: Matthias Brugger 
Cc: Marek Szyprowski 
Cc: devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Signed-off-by: Joerg Roedel

iommu: Add iommu_device_set_fwnode() interface

2017-02-10T12:44:57+00:00

Allow to store a fwnode in 'struct iommu_device';

Signed-off-by: Joerg Roedel

iommu: Make iommu_device_link/unlink take a struct iommu_device

2017-02-10T12:44:57+00:00

This makes the interface more consistent with
iommu_device_sysfs_add/remove.

Signed-off-by: Joerg Roedel