1 # IOMMU_API always gets selected by whoever wants it.
5 menuconfig IOMMU_SUPPORT
6 bool "IOMMU Hardware Support"
9 Say Y here if you want to compile device drivers for IO Memory
10 Management Units into the kernel. These devices usually allow to
11 remap DMA requests and/or remap interrupts from other devices on the
21 bool "Freescale IOMMU support"
24 select GENERIC_ALLOCATOR
26 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
27 PAMU can authorize memory access, remap the memory address, and remap I/O
32 bool "MSM IOMMU Support"
33 depends on ARCH_MSM8X60 || ARCH_MSM8960
36 Support for the IOMMUs found on certain Qualcomm SOCs.
37 These IOMMUs allow virtualization of the address space used by most
38 cores within the multimedia subsystem.
40 If unsure, say N here.
42 config IOMMU_PGTABLES_L2
44 depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
48 bool "AMD IOMMU support"
55 depends on X86_64 && PCI && ACPI
57 With this option you can enable support for AMD IOMMU hardware in
58 your system. An IOMMU is a hardware component which provides
59 remapping of DMA memory accesses from devices. With an AMD IOMMU you
60 can isolate the DMA memory of different devices and protect the
61 system from misbehaving device drivers or hardware.
63 You can find out if your system has an AMD IOMMU if you look into
64 your BIOS for an option to enable it or if you have an IVRS ACPI
67 config AMD_IOMMU_STATS
68 bool "Export AMD IOMMU statistics to debugfs"
72 This option enables code in the AMD IOMMU driver to collect various
73 statistics about whats happening in the driver and exports that
74 information to userspace via debugfs.
78 tristate "AMD IOMMU Version 2 driver"
82 This option enables support for the AMD IOMMUv2 features of the IOMMU
83 hardware. Select this option if you want to use devices that support
84 the PCI PRI and PASID interface.
91 bool "Support for Intel IOMMU using DMA Remapping Devices"
92 depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC)
96 DMA remapping (DMAR) devices support enables independent address
97 translations for Direct Memory Access (DMA) from devices.
98 These DMA remapping devices are reported via ACPI tables
99 and include PCI device scope covered by these DMA
102 config INTEL_IOMMU_DEFAULT_ON
104 prompt "Enable Intel DMA Remapping Devices by default"
105 depends on INTEL_IOMMU
107 Selecting this option will enable a DMAR device at boot time if
108 one is found. If this option is not selected, DMAR support can
109 be enabled by passing intel_iommu=on to the kernel.
111 config INTEL_IOMMU_BROKEN_GFX_WA
112 bool "Workaround broken graphics drivers (going away soon)"
113 depends on INTEL_IOMMU && BROKEN && X86
115 Current Graphics drivers tend to use physical address
116 for DMA and avoid using DMA APIs. Setting this config
117 option permits the IOMMU driver to set a unity map for
118 all the OS-visible memory. Hence the driver can continue
119 to use physical addresses for DMA, at least until this
120 option is removed in the 2.6.32 kernel.
122 config INTEL_IOMMU_FLOPPY_WA
124 depends on INTEL_IOMMU && X86
126 Floppy disk drivers are known to bypass DMA API calls
127 thereby failing to work when IOMMU is enabled. This
128 workaround will setup a 1:1 mapping for the first
129 16MiB to make floppy (an ISA device) work.
132 bool "Support for Interrupt Remapping"
133 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
136 Supports Interrupt remapping for IO-APIC and MSI devices.
137 To use x2apic mode in the CPU's which support x2APIC enhancements or
138 to support platforms with CPU's having > 8 bit APIC ID, say Y.
142 bool "OMAP IOMMU Support"
143 depends on ARCH_OMAP2PLUS
146 config OMAP_IOMMU_DEBUG
147 tristate "Export OMAP IOMMU internals in DebugFS"
148 depends on OMAP_IOMMU && DEBUG_FS
150 Select this to see extensive information about
151 the internal state of OMAP IOMMU in debugfs.
153 Say N unless you know you need this.
155 config TEGRA_IOMMU_GART
156 bool "Tegra GART IOMMU Support"
157 depends on ARCH_TEGRA_2x_SOC
160 Enables support for remapping discontiguous physical memory
161 shared with the operating system into contiguous I/O virtual
162 space through the GART (Graphics Address Relocation Table)
163 hardware included on Tegra SoCs.
165 config TEGRA_IOMMU_SMMU
166 bool "NVIDIA Tegra SMMU Support"
167 depends on ARCH_TEGRA
172 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
173 SoCs (Tegra30 up to Tegra124).
176 bool "Exynos IOMMU Support"
177 depends on ARCH_EXYNOS
179 select ARM_DMA_USE_IOMMU
181 Support for the IOMMU (System MMU) of Samsung Exynos application
182 processor family. This enables H/W multimedia accelerators to see
183 non-linear physical memory chunks as linear memory in their
186 If unsure, say N here.
188 config EXYNOS_IOMMU_DEBUG
189 bool "Debugging log for Exynos IOMMU"
190 depends on EXYNOS_IOMMU
192 Select this to see the detailed log message that shows what
193 happens in the IOMMU driver.
195 Say N unless you need kernel log message for IOMMU debugging.
197 config SHMOBILE_IPMMU
200 config SHMOBILE_IPMMU_TLB
203 config SHMOBILE_IOMMU
204 bool "IOMMU for Renesas IPMMU/IPMMUI"
207 depends on ARCH_SHMOBILE || COMPILE_TEST
209 select ARM_DMA_USE_IOMMU
210 select SHMOBILE_IPMMU
211 select SHMOBILE_IPMMU_TLB
213 Support for Renesas IPMMU/IPMMUI. This option enables
214 remapping of DMA memory accesses from all of the IP blocks
217 Warning: Drivers (including userspace drivers of UIO
218 devices) of the IP blocks on the ICB *must* use addresses
219 allocated from the IPMMU (iova) for DMA with this option
225 prompt "IPMMU/IPMMUI address space size"
226 default SHMOBILE_IOMMU_ADDRSIZE_2048MB
227 depends on SHMOBILE_IOMMU
229 This option sets IPMMU/IPMMUI address space size by
230 adjusting the 1st level page table size. The page table size
231 is calculated as follows:
233 page table size = number of page table entries * 4 bytes
234 number of page table entries = address space size / 1 MiB
236 For example, when the address space size is 2048 MiB, the
237 1st level page table size is 8192 bytes.
239 config SHMOBILE_IOMMU_ADDRSIZE_2048MB
242 config SHMOBILE_IOMMU_ADDRSIZE_1024MB
245 config SHMOBILE_IOMMU_ADDRSIZE_512MB
248 config SHMOBILE_IOMMU_ADDRSIZE_256MB
251 config SHMOBILE_IOMMU_ADDRSIZE_128MB
254 config SHMOBILE_IOMMU_ADDRSIZE_64MB
257 config SHMOBILE_IOMMU_ADDRSIZE_32MB
262 config SHMOBILE_IOMMU_L1SIZE
264 default 8192 if SHMOBILE_IOMMU_ADDRSIZE_2048MB
265 default 4096 if SHMOBILE_IOMMU_ADDRSIZE_1024MB
266 default 2048 if SHMOBILE_IOMMU_ADDRSIZE_512MB
267 default 1024 if SHMOBILE_IOMMU_ADDRSIZE_256MB
268 default 512 if SHMOBILE_IOMMU_ADDRSIZE_128MB
269 default 256 if SHMOBILE_IOMMU_ADDRSIZE_64MB
270 default 128 if SHMOBILE_IOMMU_ADDRSIZE_32MB
273 bool "Renesas VMSA-compatible IPMMU"
275 depends on ARCH_SHMOBILE || COMPILE_TEST
277 select ARM_DMA_USE_IOMMU
279 Support for the Renesas VMSA-compatible IPMMU Renesas found in the
280 R-Mobile APE6 and R-Car H2/M2 SoCs.
284 config SPAPR_TCE_IOMMU
285 bool "sPAPR TCE IOMMU Support"
286 depends on PPC_POWERNV || PPC_PSERIES
289 Enables bits of IOMMU API required by VFIO. The iommu_ops
290 is not implemented as it is not necessary for VFIO.
293 bool "ARM Ltd. System MMU (SMMU) Support"
294 depends on ARM64 || (ARM_LPAE && OF)
296 select ARM_DMA_USE_IOMMU if ARM
298 Support for implementations of the ARM System MMU architecture
299 versions 1 and 2. The driver supports both v7l and v8l table
300 formats with 4k and 64k page sizes.
302 Say Y here if your SoC includes an IOMMU device implementing
303 the ARM SMMU architecture.
305 endif # IOMMU_SUPPORT