1# IOMMU_API always gets selected by whoever wants it. 2config IOMMU_API 3 bool 4 5menuconfig IOMMU_SUPPORT 6 bool "IOMMU Hardware Support" 7 depends on MMU 8 default y 9 ---help--- 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 13 system. 14 15if IOMMU_SUPPORT 16 17menu "Generic IOMMU Pagetable Support" 18 19# Selected by the actual pagetable implementations 20config IOMMU_IO_PGTABLE 21 bool 22 23config 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 && !GENERIC_ATOMIC64)) 27 help 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. 32 33config IOMMU_IO_PGTABLE_LPAE_SELFTEST 34 bool "LPAE selftests" 35 depends on IOMMU_IO_PGTABLE_LPAE 36 help 37 Enable self-tests for LPAE page table allocator. This performs 38 a series of page-table consistency checks during boot. 39 40 If unsure, say N here. 41 42config IOMMU_IO_PGTABLE_ARMV7S 43 bool "ARMv7/v8 Short Descriptor Format" 44 select IOMMU_IO_PGTABLE 45 depends on HAS_DMA && (ARM || ARM64 || COMPILE_TEST) 46 help 47 Enable support for the ARM Short-descriptor pagetable format. 48 This supports 32-bit virtual and physical addresses mapped using 49 2-level tables with 4KB pages/1MB sections, and contiguous entries 50 for 64KB pages/16MB supersections if indicated by the IOMMU driver. 51 52config IOMMU_IO_PGTABLE_ARMV7S_SELFTEST 53 bool "ARMv7s selftests" 54 depends on IOMMU_IO_PGTABLE_ARMV7S 55 help 56 Enable self-tests for ARMv7s page table allocator. This performs 57 a series of page-table consistency checks during boot. 58 59 If unsure, say N here. 60 61endmenu 62 63config IOMMU_IOVA 64 tristate 65 66config OF_IOMMU 67 def_bool y 68 depends on OF && IOMMU_API 69 70# IOMMU-agnostic DMA-mapping layer 71config IOMMU_DMA 72 bool 73 select IOMMU_API 74 select IOMMU_IOVA 75 select NEED_SG_DMA_LENGTH 76 77config FSL_PAMU 78 bool "Freescale IOMMU support" 79 depends on PCI 80 depends on PHYS_64BIT 81 depends on PPC_E500MC || (COMPILE_TEST && PPC) 82 select IOMMU_API 83 select GENERIC_ALLOCATOR 84 help 85 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms. 86 PAMU can authorize memory access, remap the memory address, and remap I/O 87 transaction types. 88 89# MSM IOMMU support 90config MSM_IOMMU 91 bool "MSM IOMMU Support" 92 depends on ARM 93 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST 94 select IOMMU_API 95 select IOMMU_IO_PGTABLE_ARMV7S 96 help 97 Support for the IOMMUs found on certain Qualcomm SOCs. 98 These IOMMUs allow virtualization of the address space used by most 99 cores within the multimedia subsystem. 100 101 If unsure, say N here. 102 103config IOMMU_PGTABLES_L2 104 def_bool y 105 depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n 106 107# AMD IOMMU support 108config AMD_IOMMU 109 bool "AMD IOMMU support" 110 select SWIOTLB 111 select PCI_MSI 112 select PCI_ATS 113 select PCI_PRI 114 select PCI_PASID 115 select IOMMU_API 116 select IOMMU_IOVA 117 depends on X86_64 && PCI && ACPI 118 ---help--- 119 With this option you can enable support for AMD IOMMU hardware in 120 your system. An IOMMU is a hardware component which provides 121 remapping of DMA memory accesses from devices. With an AMD IOMMU you 122 can isolate the DMA memory of different devices and protect the 123 system from misbehaving device drivers or hardware. 124 125 You can find out if your system has an AMD IOMMU if you look into 126 your BIOS for an option to enable it or if you have an IVRS ACPI 127 table. 128 129config AMD_IOMMU_V2 130 tristate "AMD IOMMU Version 2 driver" 131 depends on AMD_IOMMU 132 select MMU_NOTIFIER 133 ---help--- 134 This option enables support for the AMD IOMMUv2 features of the IOMMU 135 hardware. Select this option if you want to use devices that support 136 the PCI PRI and PASID interface. 137 138# Intel IOMMU support 139config DMAR_TABLE 140 bool 141 142config INTEL_IOMMU 143 bool "Support for Intel IOMMU using DMA Remapping Devices" 144 depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC) 145 select IOMMU_API 146 select IOMMU_IOVA 147 select DMAR_TABLE 148 help 149 DMA remapping (DMAR) devices support enables independent address 150 translations for Direct Memory Access (DMA) from devices. 151 These DMA remapping devices are reported via ACPI tables 152 and include PCI device scope covered by these DMA 153 remapping devices. 154 155config INTEL_IOMMU_SVM 156 bool "Support for Shared Virtual Memory with Intel IOMMU" 157 depends on INTEL_IOMMU && X86 158 select PCI_PASID 159 select MMU_NOTIFIER 160 help 161 Shared Virtual Memory (SVM) provides a facility for devices 162 to access DMA resources through process address space by 163 means of a Process Address Space ID (PASID). 164 165config INTEL_IOMMU_DEFAULT_ON 166 def_bool y 167 prompt "Enable Intel DMA Remapping Devices by default" 168 depends on INTEL_IOMMU 169 help 170 Selecting this option will enable a DMAR device at boot time if 171 one is found. If this option is not selected, DMAR support can 172 be enabled by passing intel_iommu=on to the kernel. 173 174config INTEL_IOMMU_BROKEN_GFX_WA 175 bool "Workaround broken graphics drivers (going away soon)" 176 depends on INTEL_IOMMU && BROKEN && X86 177 ---help--- 178 Current Graphics drivers tend to use physical address 179 for DMA and avoid using DMA APIs. Setting this config 180 option permits the IOMMU driver to set a unity map for 181 all the OS-visible memory. Hence the driver can continue 182 to use physical addresses for DMA, at least until this 183 option is removed in the 2.6.32 kernel. 184 185config INTEL_IOMMU_FLOPPY_WA 186 def_bool y 187 depends on INTEL_IOMMU && X86 188 ---help--- 189 Floppy disk drivers are known to bypass DMA API calls 190 thereby failing to work when IOMMU is enabled. This 191 workaround will setup a 1:1 mapping for the first 192 16MiB to make floppy (an ISA device) work. 193 194config IRQ_REMAP 195 bool "Support for Interrupt Remapping" 196 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI 197 select DMAR_TABLE 198 ---help--- 199 Supports Interrupt remapping for IO-APIC and MSI devices. 200 To use x2apic mode in the CPU's which support x2APIC enhancements or 201 to support platforms with CPU's having > 8 bit APIC ID, say Y. 202 203# OMAP IOMMU support 204config OMAP_IOMMU 205 bool "OMAP IOMMU Support" 206 depends on ARM && MMU 207 depends on ARCH_OMAP2PLUS || COMPILE_TEST 208 select IOMMU_API 209 ---help--- 210 The OMAP3 media platform drivers depend on iommu support, 211 if you need them say Y here. 212 213config OMAP_IOMMU_DEBUG 214 bool "Export OMAP IOMMU internals in DebugFS" 215 depends on OMAP_IOMMU && DEBUG_FS 216 ---help--- 217 Select this to see extensive information about 218 the internal state of OMAP IOMMU in debugfs. 219 220 Say N unless you know you need this. 221 222config ROCKCHIP_IOMMU 223 bool "Rockchip IOMMU Support" 224 depends on ARM || ARM64 225 depends on ARCH_ROCKCHIP || COMPILE_TEST 226 select IOMMU_API 227 select ARM_DMA_USE_IOMMU 228 help 229 Support for IOMMUs found on Rockchip rk32xx SOCs. 230 These IOMMUs allow virtualization of the address space used by most 231 cores within the multimedia subsystem. 232 Say Y here if you are using a Rockchip SoC that includes an IOMMU 233 device. 234 235config TEGRA_IOMMU_GART 236 bool "Tegra GART IOMMU Support" 237 depends on ARCH_TEGRA_2x_SOC 238 select IOMMU_API 239 help 240 Enables support for remapping discontiguous physical memory 241 shared with the operating system into contiguous I/O virtual 242 space through the GART (Graphics Address Relocation Table) 243 hardware included on Tegra SoCs. 244 245config TEGRA_IOMMU_SMMU 246 bool "NVIDIA Tegra SMMU Support" 247 depends on ARCH_TEGRA 248 depends on TEGRA_AHB 249 depends on TEGRA_MC 250 select IOMMU_API 251 help 252 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra 253 SoCs (Tegra30 up to Tegra210). 254 255config EXYNOS_IOMMU 256 bool "Exynos IOMMU Support" 257 depends on ARCH_EXYNOS && MMU 258 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes 259 select IOMMU_API 260 select ARM_DMA_USE_IOMMU 261 help 262 Support for the IOMMU (System MMU) of Samsung Exynos application 263 processor family. This enables H/W multimedia accelerators to see 264 non-linear physical memory chunks as linear memory in their 265 address space. 266 267 If unsure, say N here. 268 269config EXYNOS_IOMMU_DEBUG 270 bool "Debugging log for Exynos IOMMU" 271 depends on EXYNOS_IOMMU 272 help 273 Select this to see the detailed log message that shows what 274 happens in the IOMMU driver. 275 276 Say N unless you need kernel log message for IOMMU debugging. 277 278config IPMMU_VMSA 279 bool "Renesas VMSA-compatible IPMMU" 280 depends on ARM || IOMMU_DMA 281 depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64) 282 select IOMMU_API 283 select IOMMU_IO_PGTABLE_LPAE 284 select ARM_DMA_USE_IOMMU 285 help 286 Support for the Renesas VMSA-compatible IPMMU Renesas found in the 287 R-Mobile APE6 and R-Car H2/M2 SoCs. 288 289 If unsure, say N. 290 291config SPAPR_TCE_IOMMU 292 bool "sPAPR TCE IOMMU Support" 293 depends on PPC_POWERNV || PPC_PSERIES 294 select IOMMU_API 295 help 296 Enables bits of IOMMU API required by VFIO. The iommu_ops 297 is not implemented as it is not necessary for VFIO. 298 299# ARM IOMMU support 300config ARM_SMMU 301 bool "ARM Ltd. System MMU (SMMU) Support" 302 depends on (ARM64 || ARM) && MMU 303 select IOMMU_API 304 select IOMMU_IO_PGTABLE_LPAE 305 select ARM_DMA_USE_IOMMU if ARM 306 help 307 Support for implementations of the ARM System MMU architecture 308 versions 1 and 2. 309 310 Say Y here if your SoC includes an IOMMU device implementing 311 the ARM SMMU architecture. 312 313config ARM_SMMU_V3 314 bool "ARM Ltd. System MMU Version 3 (SMMUv3) Support" 315 depends on ARM64 316 select IOMMU_API 317 select IOMMU_IO_PGTABLE_LPAE 318 select GENERIC_MSI_IRQ_DOMAIN 319 help 320 Support for implementations of the ARM System MMU architecture 321 version 3 providing translation support to a PCIe root complex. 322 323 Say Y here if your system includes an IOMMU device implementing 324 the ARM SMMUv3 architecture. 325 326config S390_IOMMU 327 def_bool y if S390 && PCI 328 depends on S390 && PCI 329 select IOMMU_API 330 help 331 Support for the IOMMU API for s390 PCI devices. 332 333config S390_CCW_IOMMU 334 bool "S390 CCW IOMMU Support" 335 depends on S390 && CCW 336 select IOMMU_API 337 help 338 Enables bits of IOMMU API required by VFIO. The iommu_ops 339 is not implemented as it is not necessary for VFIO. 340 341config MTK_IOMMU 342 bool "MTK IOMMU Support" 343 depends on ARM || ARM64 344 depends on ARCH_MEDIATEK || COMPILE_TEST 345 select ARM_DMA_USE_IOMMU 346 select IOMMU_API 347 select IOMMU_DMA 348 select IOMMU_IO_PGTABLE_ARMV7S 349 select MEMORY 350 select MTK_SMI 351 help 352 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia 353 Memory Management Unit. This option enables remapping of DMA memory 354 accesses for the multimedia subsystem. 355 356 If unsure, say N here. 357 358config MTK_IOMMU_V1 359 bool "MTK IOMMU Version 1 (M4U gen1) Support" 360 depends on ARM 361 depends on ARCH_MEDIATEK || COMPILE_TEST 362 select ARM_DMA_USE_IOMMU 363 select IOMMU_API 364 select MEMORY 365 select MTK_SMI 366 help 367 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is 368 Multimedia Memory Managememt Unit. This option enables remapping of 369 DMA memory accesses for the multimedia subsystem. 370 371 if unsure, say N here. 372 373config QCOM_IOMMU 374 # Note: iommu drivers cannot (yet?) be built as modules 375 bool "Qualcomm IOMMU Support" 376 depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64) 377 depends on HAS_DMA 378 select IOMMU_API 379 select IOMMU_IO_PGTABLE_LPAE 380 select ARM_DMA_USE_IOMMU 381 help 382 Support for IOMMU on certain Qualcomm SoCs. 383 384endif # IOMMU_SUPPORT 385