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 depends on OF && IOMMU_API
24 bool "Freescale IOMMU support"
27 select GENERIC_ALLOCATOR
29 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
30 PAMU can authorize memory access, remap the memory address, and remap I/O
35 bool "MSM IOMMU Support"
36 depends on ARCH_MSM8X60 || ARCH_MSM8960
39 Support for the IOMMUs found on certain Qualcomm SOCs.
40 These IOMMUs allow virtualization of the address space used by most
41 cores within the multimedia subsystem.
43 If unsure, say N here.
45 config IOMMU_PGTABLES_L2
47 depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
51 bool "AMD IOMMU support"
58 depends on X86_64 && PCI && ACPI
60 With this option you can enable support for AMD IOMMU hardware in
61 your system. An IOMMU is a hardware component which provides
62 remapping of DMA memory accesses from devices. With an AMD IOMMU you
63 can isolate the DMA memory of different devices and protect the
64 system from misbehaving device drivers or hardware.
66 You can find out if your system has an AMD IOMMU if you look into
67 your BIOS for an option to enable it or if you have an IVRS ACPI
70 config AMD_IOMMU_STATS
71 bool "Export AMD IOMMU statistics to debugfs"
75 This option enables code in the AMD IOMMU driver to collect various
76 statistics about whats happening in the driver and exports that
77 information to userspace via debugfs.
81 tristate "AMD IOMMU Version 2 driver"
85 This option enables support for the AMD IOMMUv2 features of the IOMMU
86 hardware. Select this option if you want to use devices that support
87 the PCI PRI and PASID interface.
94 bool "Support for Intel IOMMU using DMA Remapping Devices"
95 depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC)
100 DMA remapping (DMAR) devices support enables independent address
101 translations for Direct Memory Access (DMA) from devices.
102 These DMA remapping devices are reported via ACPI tables
103 and include PCI device scope covered by these DMA
106 config INTEL_IOMMU_DEFAULT_ON
108 prompt "Enable Intel DMA Remapping Devices by default"
109 depends on INTEL_IOMMU
111 Selecting this option will enable a DMAR device at boot time if
112 one is found. If this option is not selected, DMAR support can
113 be enabled by passing intel_iommu=on to the kernel.
115 config INTEL_IOMMU_BROKEN_GFX_WA
116 bool "Workaround broken graphics drivers (going away soon)"
117 depends on INTEL_IOMMU && BROKEN && X86
119 Current Graphics drivers tend to use physical address
120 for DMA and avoid using DMA APIs. Setting this config
121 option permits the IOMMU driver to set a unity map for
122 all the OS-visible memory. Hence the driver can continue
123 to use physical addresses for DMA, at least until this
124 option is removed in the 2.6.32 kernel.
126 config INTEL_IOMMU_FLOPPY_WA
128 depends on INTEL_IOMMU && X86
130 Floppy disk drivers are known to bypass DMA API calls
131 thereby failing to work when IOMMU is enabled. This
132 workaround will setup a 1:1 mapping for the first
133 16MiB to make floppy (an ISA device) work.
136 bool "Support for Interrupt Remapping"
137 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
140 Supports Interrupt remapping for IO-APIC and MSI devices.
141 To use x2apic mode in the CPU's which support x2APIC enhancements or
142 to support platforms with CPU's having > 8 bit APIC ID, say Y.
146 bool "OMAP IOMMU Support"
147 depends on ARCH_OMAP2PLUS
150 config OMAP_IOMMU_DEBUG
151 bool "Export OMAP IOMMU internals in DebugFS"
152 depends on OMAP_IOMMU && DEBUG_FS
154 Select this to see extensive information about
155 the internal state of OMAP IOMMU in debugfs.
157 Say N unless you know you need this.
159 config ROCKCHIP_IOMMU
160 bool "Rockchip IOMMU Support"
162 depends on ARCH_ROCKCHIP || COMPILE_TEST
164 select ARM_DMA_USE_IOMMU
166 Support for IOMMUs found on Rockchip rk32xx SOCs.
167 These IOMMUs allow virtualization of the address space used by most
168 cores within the multimedia subsystem.
169 Say Y here if you are using a Rockchip SoC that includes an IOMMU
172 config TEGRA_IOMMU_GART
173 bool "Tegra GART IOMMU Support"
174 depends on ARCH_TEGRA_2x_SOC
177 Enables support for remapping discontiguous physical memory
178 shared with the operating system into contiguous I/O virtual
179 space through the GART (Graphics Address Relocation Table)
180 hardware included on Tegra SoCs.
182 config TEGRA_IOMMU_SMMU
183 bool "NVIDIA Tegra SMMU Support"
184 depends on ARCH_TEGRA
189 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
190 SoCs (Tegra30 up to Tegra124).
193 bool "Exynos IOMMU Support"
194 depends on ARCH_EXYNOS && ARM
196 select ARM_DMA_USE_IOMMU
198 Support for the IOMMU (System MMU) of Samsung Exynos application
199 processor family. This enables H/W multimedia accelerators to see
200 non-linear physical memory chunks as linear memory in their
203 If unsure, say N here.
205 config EXYNOS_IOMMU_DEBUG
206 bool "Debugging log for Exynos IOMMU"
207 depends on EXYNOS_IOMMU
209 Select this to see the detailed log message that shows what
210 happens in the IOMMU driver.
212 Say N unless you need kernel log message for IOMMU debugging.
214 config SHMOBILE_IPMMU
217 config SHMOBILE_IPMMU_TLB
220 config SHMOBILE_IOMMU
221 bool "IOMMU for Renesas IPMMU/IPMMUI"
224 depends on ARCH_SHMOBILE || COMPILE_TEST
226 select ARM_DMA_USE_IOMMU
227 select SHMOBILE_IPMMU
228 select SHMOBILE_IPMMU_TLB
230 Support for Renesas IPMMU/IPMMUI. This option enables
231 remapping of DMA memory accesses from all of the IP blocks
234 Warning: Drivers (including userspace drivers of UIO
235 devices) of the IP blocks on the ICB *must* use addresses
236 allocated from the IPMMU (iova) for DMA with this option
242 prompt "IPMMU/IPMMUI address space size"
243 default SHMOBILE_IOMMU_ADDRSIZE_2048MB
244 depends on SHMOBILE_IOMMU
246 This option sets IPMMU/IPMMUI address space size by
247 adjusting the 1st level page table size. The page table size
248 is calculated as follows:
250 page table size = number of page table entries * 4 bytes
251 number of page table entries = address space size / 1 MiB
253 For example, when the address space size is 2048 MiB, the
254 1st level page table size is 8192 bytes.
256 config SHMOBILE_IOMMU_ADDRSIZE_2048MB
259 config SHMOBILE_IOMMU_ADDRSIZE_1024MB
262 config SHMOBILE_IOMMU_ADDRSIZE_512MB
265 config SHMOBILE_IOMMU_ADDRSIZE_256MB
268 config SHMOBILE_IOMMU_ADDRSIZE_128MB
271 config SHMOBILE_IOMMU_ADDRSIZE_64MB
274 config SHMOBILE_IOMMU_ADDRSIZE_32MB
279 config SHMOBILE_IOMMU_L1SIZE
281 default 8192 if SHMOBILE_IOMMU_ADDRSIZE_2048MB
282 default 4096 if SHMOBILE_IOMMU_ADDRSIZE_1024MB
283 default 2048 if SHMOBILE_IOMMU_ADDRSIZE_512MB
284 default 1024 if SHMOBILE_IOMMU_ADDRSIZE_256MB
285 default 512 if SHMOBILE_IOMMU_ADDRSIZE_128MB
286 default 256 if SHMOBILE_IOMMU_ADDRSIZE_64MB
287 default 128 if SHMOBILE_IOMMU_ADDRSIZE_32MB
290 bool "Renesas VMSA-compatible IPMMU"
292 depends on ARCH_SHMOBILE || COMPILE_TEST
294 select ARM_DMA_USE_IOMMU
296 Support for the Renesas VMSA-compatible IPMMU Renesas found in the
297 R-Mobile APE6 and R-Car H2/M2 SoCs.
301 config SPAPR_TCE_IOMMU
302 bool "sPAPR TCE IOMMU Support"
303 depends on PPC_POWERNV || PPC_PSERIES
306 Enables bits of IOMMU API required by VFIO. The iommu_ops
307 is not implemented as it is not necessary for VFIO.
310 bool "ARM Ltd. System MMU (SMMU) Support"
311 depends on ARM64 || (ARM_LPAE && OF)
313 select ARM_DMA_USE_IOMMU if ARM
315 Support for implementations of the ARM System MMU architecture
316 versions 1 and 2. The driver supports both v7l and v8l table
317 formats with 4k and 64k page sizes.
319 Say Y here if your SoC includes an IOMMU device implementing
320 the ARM SMMU architecture.
322 endif # IOMMU_SUPPORT