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 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 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 NEED_DMA_MAP_STATE 148 select DMAR_TABLE 149 help 150 DMA remapping (DMAR) devices support enables independent address 151 translations for Direct Memory Access (DMA) from devices. 152 These DMA remapping devices are reported via ACPI tables 153 and include PCI device scope covered by these DMA 154 remapping devices. 155 156config INTEL_IOMMU_SVM 157 bool "Support for Shared Virtual Memory with Intel IOMMU" 158 depends on INTEL_IOMMU && X86 159 select PCI_PASID 160 select MMU_NOTIFIER 161 help 162 Shared Virtual Memory (SVM) provides a facility for devices 163 to access DMA resources through process address space by 164 means of a Process Address Space ID (PASID). 165 166config INTEL_IOMMU_DEFAULT_ON 167 def_bool y 168 prompt "Enable Intel DMA Remapping Devices by default" 169 depends on INTEL_IOMMU 170 help 171 Selecting this option will enable a DMAR device at boot time if 172 one is found. If this option is not selected, DMAR support can 173 be enabled by passing intel_iommu=on to the kernel. 174 175config INTEL_IOMMU_BROKEN_GFX_WA 176 bool "Workaround broken graphics drivers (going away soon)" 177 depends on INTEL_IOMMU && BROKEN && X86 178 ---help--- 179 Current Graphics drivers tend to use physical address 180 for DMA and avoid using DMA APIs. Setting this config 181 option permits the IOMMU driver to set a unity map for 182 all the OS-visible memory. Hence the driver can continue 183 to use physical addresses for DMA, at least until this 184 option is removed in the 2.6.32 kernel. 185 186config INTEL_IOMMU_FLOPPY_WA 187 def_bool y 188 depends on INTEL_IOMMU && X86 189 ---help--- 190 Floppy disk drivers are known to bypass DMA API calls 191 thereby failing to work when IOMMU is enabled. This 192 workaround will setup a 1:1 mapping for the first 193 16MiB to make floppy (an ISA device) work. 194 195config IRQ_REMAP 196 bool "Support for Interrupt Remapping" 197 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI 198 select DMAR_TABLE 199 ---help--- 200 Supports Interrupt remapping for IO-APIC and MSI devices. 201 To use x2apic mode in the CPU's which support x2APIC enhancements or 202 to support platforms with CPU's having > 8 bit APIC ID, say Y. 203 204# OMAP IOMMU support 205config OMAP_IOMMU 206 bool "OMAP IOMMU Support" 207 depends on ARM && MMU 208 depends on ARCH_OMAP2PLUS || COMPILE_TEST 209 select IOMMU_API 210 ---help--- 211 The OMAP3 media platform drivers depend on iommu support, 212 if you need them say Y here. 213 214config OMAP_IOMMU_DEBUG 215 bool "Export OMAP IOMMU internals in DebugFS" 216 depends on OMAP_IOMMU && DEBUG_FS 217 ---help--- 218 Select this to see extensive information about 219 the internal state of OMAP IOMMU in debugfs. 220 221 Say N unless you know you need this. 222 223config ROCKCHIP_IOMMU 224 bool "Rockchip IOMMU Support" 225 depends on ARM || ARM64 226 depends on ARCH_ROCKCHIP || COMPILE_TEST 227 select IOMMU_API 228 select ARM_DMA_USE_IOMMU 229 help 230 Support for IOMMUs found on Rockchip rk32xx SOCs. 231 These IOMMUs allow virtualization of the address space used by most 232 cores within the multimedia subsystem. 233 Say Y here if you are using a Rockchip SoC that includes an IOMMU 234 device. 235 236config TEGRA_IOMMU_GART 237 bool "Tegra GART IOMMU Support" 238 depends on ARCH_TEGRA_2x_SOC 239 select IOMMU_API 240 help 241 Enables support for remapping discontiguous physical memory 242 shared with the operating system into contiguous I/O virtual 243 space through the GART (Graphics Address Relocation Table) 244 hardware included on Tegra SoCs. 245 246config TEGRA_IOMMU_SMMU 247 bool "NVIDIA Tegra SMMU Support" 248 depends on ARCH_TEGRA 249 depends on TEGRA_AHB 250 depends on TEGRA_MC 251 select IOMMU_API 252 help 253 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra 254 SoCs (Tegra30 up to Tegra210). 255 256config EXYNOS_IOMMU 257 bool "Exynos IOMMU Support" 258 depends on ARCH_EXYNOS && MMU 259 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes 260 select IOMMU_API 261 select ARM_DMA_USE_IOMMU 262 help 263 Support for the IOMMU (System MMU) of Samsung Exynos application 264 processor family. This enables H/W multimedia accelerators to see 265 non-linear physical memory chunks as linear memory in their 266 address space. 267 268 If unsure, say N here. 269 270config EXYNOS_IOMMU_DEBUG 271 bool "Debugging log for Exynos IOMMU" 272 depends on EXYNOS_IOMMU 273 help 274 Select this to see the detailed log message that shows what 275 happens in the IOMMU driver. 276 277 Say N unless you need kernel log message for IOMMU debugging. 278 279config IPMMU_VMSA 280 bool "Renesas VMSA-compatible IPMMU" 281 depends on ARM || IOMMU_DMA 282 depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64) 283 select IOMMU_API 284 select IOMMU_IO_PGTABLE_LPAE 285 select ARM_DMA_USE_IOMMU 286 help 287 Support for the Renesas VMSA-compatible IPMMU Renesas found in the 288 R-Mobile APE6 and R-Car H2/M2 SoCs. 289 290 If unsure, say N. 291 292config SPAPR_TCE_IOMMU 293 bool "sPAPR TCE IOMMU Support" 294 depends on PPC_POWERNV || PPC_PSERIES 295 select IOMMU_API 296 help 297 Enables bits of IOMMU API required by VFIO. The iommu_ops 298 is not implemented as it is not necessary for VFIO. 299 300# ARM IOMMU support 301config ARM_SMMU 302 bool "ARM Ltd. System MMU (SMMU) Support" 303 depends on (ARM64 || ARM) && MMU 304 select IOMMU_API 305 select IOMMU_IO_PGTABLE_LPAE 306 select ARM_DMA_USE_IOMMU if ARM 307 help 308 Support for implementations of the ARM System MMU architecture 309 versions 1 and 2. 310 311 Say Y here if your SoC includes an IOMMU device implementing 312 the ARM SMMU architecture. 313 314config ARM_SMMU_V3 315 bool "ARM Ltd. System MMU Version 3 (SMMUv3) Support" 316 depends on ARM64 317 select IOMMU_API 318 select IOMMU_IO_PGTABLE_LPAE 319 select GENERIC_MSI_IRQ_DOMAIN 320 help 321 Support for implementations of the ARM System MMU architecture 322 version 3 providing translation support to a PCIe root complex. 323 324 Say Y here if your system includes an IOMMU device implementing 325 the ARM SMMUv3 architecture. 326 327config S390_IOMMU 328 def_bool y if S390 && PCI 329 depends on S390 && PCI 330 select IOMMU_API 331 help 332 Support for the IOMMU API for s390 PCI devices. 333 334config S390_CCW_IOMMU 335 bool "S390 CCW IOMMU Support" 336 depends on S390 && CCW 337 select IOMMU_API 338 help 339 Enables bits of IOMMU API required by VFIO. The iommu_ops 340 is not implemented as it is not necessary for VFIO. 341 342config MTK_IOMMU 343 bool "MTK IOMMU Support" 344 depends on ARM || ARM64 345 depends on ARCH_MEDIATEK || COMPILE_TEST 346 select ARM_DMA_USE_IOMMU 347 select IOMMU_API 348 select IOMMU_DMA 349 select IOMMU_IO_PGTABLE_ARMV7S 350 select MEMORY 351 select MTK_SMI 352 help 353 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia 354 Memory Management Unit. This option enables remapping of DMA memory 355 accesses for the multimedia subsystem. 356 357 If unsure, say N here. 358 359config MTK_IOMMU_V1 360 bool "MTK IOMMU Version 1 (M4U gen1) Support" 361 depends on ARM 362 depends on ARCH_MEDIATEK || COMPILE_TEST 363 select ARM_DMA_USE_IOMMU 364 select IOMMU_API 365 select MEMORY 366 select MTK_SMI 367 help 368 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is 369 Multimedia Memory Managememt Unit. This option enables remapping of 370 DMA memory accesses for the multimedia subsystem. 371 372 if unsure, say N here. 373 374config QCOM_IOMMU 375 # Note: iommu drivers cannot (yet?) be built as modules 376 bool "Qualcomm IOMMU Support" 377 depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64) 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