1 # IOMMU_API always gets selected by whoever wants it.
5 menuconfig IOMMU_SUPPORT
6 bool "IOMMU Hardware Support"
10 Say Y here if you want to compile device drivers for IO Memory
11 Management Units into the kernel. These devices usually allow to
12 remap DMA requests and/or remap interrupts from other devices on the
17 menu "Generic IOMMU Pagetable Support"
19 # Selected by the actual pagetable implementations
20 config IOMMU_IO_PGTABLE
23 config IOMMU_IO_PGTABLE_LPAE
24 bool "ARMv7/v8 Long Descriptor Format"
25 select IOMMU_IO_PGTABLE
26 depends on HAS_DMA && (ARM || ARM64 || COMPILE_TEST)
28 Enable support for the ARM long descriptor pagetable format.
29 This allocator supports 4K/2M/1G, 16K/32M and 64K/512M page
30 sizes at both stage-1 and stage-2, as well as address spaces
31 up to 48-bits in size.
33 config IOMMU_IO_PGTABLE_LPAE_SELFTEST
35 depends on IOMMU_IO_PGTABLE_LPAE
37 Enable self-tests for LPAE page table allocator. This performs
38 a series of page-table consistency checks during boot.
40 If unsure, say N here.
49 depends on OF && IOMMU_API
51 # IOMMU-agnostic DMA-mapping layer
54 depends on NEED_SG_DMA_LENGTH
59 bool "Freescale IOMMU support"
61 depends on PPC_E500MC || COMPILE_TEST
63 select GENERIC_ALLOCATOR
65 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
66 PAMU can authorize memory access, remap the memory address, and remap I/O
71 bool "MSM IOMMU Support"
73 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
77 Support for the IOMMUs found on certain Qualcomm SOCs.
78 These IOMMUs allow virtualization of the address space used by most
79 cores within the multimedia subsystem.
81 If unsure, say N here.
83 config IOMMU_PGTABLES_L2
85 depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
89 bool "AMD IOMMU support"
96 depends on X86_64 && PCI && ACPI
98 With this option you can enable support for AMD IOMMU hardware in
99 your system. An IOMMU is a hardware component which provides
100 remapping of DMA memory accesses from devices. With an AMD IOMMU you
101 can isolate the DMA memory of different devices and protect the
102 system from misbehaving device drivers or hardware.
104 You can find out if your system has an AMD IOMMU if you look into
105 your BIOS for an option to enable it or if you have an IVRS ACPI
108 config AMD_IOMMU_STATS
109 bool "Export AMD IOMMU statistics to debugfs"
113 This option enables code in the AMD IOMMU driver to collect various
114 statistics about whats happening in the driver and exports that
115 information to userspace via debugfs.
119 tristate "AMD IOMMU Version 2 driver"
123 This option enables support for the AMD IOMMUv2 features of the IOMMU
124 hardware. Select this option if you want to use devices that support
125 the PCI PRI and PASID interface.
127 # Intel IOMMU support
132 bool "Support for Intel IOMMU using DMA Remapping Devices"
133 depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC)
138 DMA remapping (DMAR) devices support enables independent address
139 translations for Direct Memory Access (DMA) from devices.
140 These DMA remapping devices are reported via ACPI tables
141 and include PCI device scope covered by these DMA
144 config INTEL_IOMMU_DEFAULT_ON
146 prompt "Enable Intel DMA Remapping Devices by default"
147 depends on INTEL_IOMMU
149 Selecting this option will enable a DMAR device at boot time if
150 one is found. If this option is not selected, DMAR support can
151 be enabled by passing intel_iommu=on to the kernel.
153 config INTEL_IOMMU_BROKEN_GFX_WA
154 bool "Workaround broken graphics drivers (going away soon)"
155 depends on INTEL_IOMMU && BROKEN && X86
157 Current Graphics drivers tend to use physical address
158 for DMA and avoid using DMA APIs. Setting this config
159 option permits the IOMMU driver to set a unity map for
160 all the OS-visible memory. Hence the driver can continue
161 to use physical addresses for DMA, at least until this
162 option is removed in the 2.6.32 kernel.
164 config INTEL_IOMMU_FLOPPY_WA
166 depends on INTEL_IOMMU && X86
168 Floppy disk drivers are known to bypass DMA API calls
169 thereby failing to work when IOMMU is enabled. This
170 workaround will setup a 1:1 mapping for the first
171 16MiB to make floppy (an ISA device) work.
174 bool "Support for Interrupt Remapping"
175 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
178 Supports Interrupt remapping for IO-APIC and MSI devices.
179 To use x2apic mode in the CPU's which support x2APIC enhancements or
180 to support platforms with CPU's having > 8 bit APIC ID, say Y.
184 bool "OMAP IOMMU Support"
185 depends on ARM && MMU
186 depends on ARCH_OMAP2PLUS || COMPILE_TEST
189 The OMAP3 media platform drivers depend on iommu support,
190 if you need them say Y here.
192 config OMAP_IOMMU_DEBUG
193 bool "Export OMAP IOMMU internals in DebugFS"
194 depends on OMAP_IOMMU && DEBUG_FS
196 Select this to see extensive information about
197 the internal state of OMAP IOMMU in debugfs.
199 Say N unless you know you need this.
201 config ROCKCHIP_IOMMU
202 bool "Rockchip IOMMU Support"
204 depends on ARCH_ROCKCHIP || COMPILE_TEST
206 select ARM_DMA_USE_IOMMU
208 Support for IOMMUs found on Rockchip rk32xx SOCs.
209 These IOMMUs allow virtualization of the address space used by most
210 cores within the multimedia subsystem.
211 Say Y here if you are using a Rockchip SoC that includes an IOMMU
214 config TEGRA_IOMMU_GART
215 bool "Tegra GART IOMMU Support"
216 depends on ARCH_TEGRA_2x_SOC
219 Enables support for remapping discontiguous physical memory
220 shared with the operating system into contiguous I/O virtual
221 space through the GART (Graphics Address Relocation Table)
222 hardware included on Tegra SoCs.
224 config TEGRA_IOMMU_SMMU
225 bool "NVIDIA Tegra SMMU Support"
226 depends on ARCH_TEGRA
231 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
232 SoCs (Tegra30 up to Tegra210).
235 bool "Exynos IOMMU Support"
236 depends on ARCH_EXYNOS && ARM && MMU
238 select ARM_DMA_USE_IOMMU
240 Support for the IOMMU (System MMU) of Samsung Exynos application
241 processor family. This enables H/W multimedia accelerators to see
242 non-linear physical memory chunks as linear memory in their
245 If unsure, say N here.
247 config EXYNOS_IOMMU_DEBUG
248 bool "Debugging log for Exynos IOMMU"
249 depends on EXYNOS_IOMMU
251 Select this to see the detailed log message that shows what
252 happens in the IOMMU driver.
254 Say N unless you need kernel log message for IOMMU debugging.
256 config SHMOBILE_IPMMU
259 config SHMOBILE_IPMMU_TLB
262 config SHMOBILE_IOMMU
263 bool "IOMMU for Renesas IPMMU/IPMMUI"
265 depends on ARM && MMU
266 depends on ARCH_SHMOBILE || COMPILE_TEST
268 select ARM_DMA_USE_IOMMU
269 select SHMOBILE_IPMMU
270 select SHMOBILE_IPMMU_TLB
272 Support for Renesas IPMMU/IPMMUI. This option enables
273 remapping of DMA memory accesses from all of the IP blocks
276 Warning: Drivers (including userspace drivers of UIO
277 devices) of the IP blocks on the ICB *must* use addresses
278 allocated from the IPMMU (iova) for DMA with this option
284 prompt "IPMMU/IPMMUI address space size"
285 default SHMOBILE_IOMMU_ADDRSIZE_2048MB
286 depends on SHMOBILE_IOMMU
288 This option sets IPMMU/IPMMUI address space size by
289 adjusting the 1st level page table size. The page table size
290 is calculated as follows:
292 page table size = number of page table entries * 4 bytes
293 number of page table entries = address space size / 1 MiB
295 For example, when the address space size is 2048 MiB, the
296 1st level page table size is 8192 bytes.
298 config SHMOBILE_IOMMU_ADDRSIZE_2048MB
301 config SHMOBILE_IOMMU_ADDRSIZE_1024MB
304 config SHMOBILE_IOMMU_ADDRSIZE_512MB
307 config SHMOBILE_IOMMU_ADDRSIZE_256MB
310 config SHMOBILE_IOMMU_ADDRSIZE_128MB
313 config SHMOBILE_IOMMU_ADDRSIZE_64MB
316 config SHMOBILE_IOMMU_ADDRSIZE_32MB
321 config SHMOBILE_IOMMU_L1SIZE
323 default 8192 if SHMOBILE_IOMMU_ADDRSIZE_2048MB
324 default 4096 if SHMOBILE_IOMMU_ADDRSIZE_1024MB
325 default 2048 if SHMOBILE_IOMMU_ADDRSIZE_512MB
326 default 1024 if SHMOBILE_IOMMU_ADDRSIZE_256MB
327 default 512 if SHMOBILE_IOMMU_ADDRSIZE_128MB
328 default 256 if SHMOBILE_IOMMU_ADDRSIZE_64MB
329 default 128 if SHMOBILE_IOMMU_ADDRSIZE_32MB
332 bool "Renesas VMSA-compatible IPMMU"
334 depends on ARCH_SHMOBILE || COMPILE_TEST
336 select IOMMU_IO_PGTABLE_LPAE
337 select ARM_DMA_USE_IOMMU
339 Support for the Renesas VMSA-compatible IPMMU Renesas found in the
340 R-Mobile APE6 and R-Car H2/M2 SoCs.
344 config SPAPR_TCE_IOMMU
345 bool "sPAPR TCE IOMMU Support"
346 depends on PPC_POWERNV || PPC_PSERIES
349 Enables bits of IOMMU API required by VFIO. The iommu_ops
350 is not implemented as it is not necessary for VFIO.
354 bool "ARM Ltd. System MMU (SMMU) Support"
355 depends on (ARM64 || ARM) && MMU
357 select IOMMU_IO_PGTABLE_LPAE
358 select ARM_DMA_USE_IOMMU if ARM
360 Support for implementations of the ARM System MMU architecture
363 Say Y here if your SoC includes an IOMMU device implementing
364 the ARM SMMU architecture.
367 bool "ARM Ltd. System MMU Version 3 (SMMUv3) Support"
368 depends on ARM64 && PCI
370 select IOMMU_IO_PGTABLE_LPAE
371 select GENERIC_MSI_IRQ_DOMAIN
373 Support for implementations of the ARM System MMU architecture
374 version 3 providing translation support to a PCIe root complex.
376 Say Y here if your system includes an IOMMU device implementing
377 the ARM SMMUv3 architecture.
380 def_bool y if S390 && PCI
381 depends on S390 && PCI
384 Support for the IOMMU API for s390 PCI devices.
386 endif # IOMMU_SUPPORT