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) 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 42endmenu 43 44config IOMMU_IOVA 45 tristate 46 47config OF_IOMMU 48 def_bool y 49 depends on OF && IOMMU_API 50 51# IOMMU-agnostic DMA-mapping layer 52config IOMMU_DMA 53 bool 54 depends on NEED_SG_DMA_LENGTH 55 select IOMMU_API 56 select IOMMU_IOVA 57 58config FSL_PAMU 59 bool "Freescale IOMMU support" 60 depends on PPC32 61 depends on PPC_E500MC || COMPILE_TEST 62 select IOMMU_API 63 select GENERIC_ALLOCATOR 64 help 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 67 transaction types. 68 69# MSM IOMMU support 70config MSM_IOMMU 71 bool "MSM IOMMU Support" 72 depends on ARM 73 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST 74 depends on BROKEN 75 select IOMMU_API 76 help 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. 80 81 If unsure, say N here. 82 83config IOMMU_PGTABLES_L2 84 def_bool y 85 depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n 86 87# AMD IOMMU support 88config AMD_IOMMU 89 bool "AMD IOMMU support" 90 select SWIOTLB 91 select PCI_MSI 92 select PCI_ATS 93 select PCI_PRI 94 select PCI_PASID 95 select IOMMU_API 96 depends on X86_64 && PCI && ACPI 97 ---help--- 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. 103 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 106 table. 107 108config AMD_IOMMU_STATS 109 bool "Export AMD IOMMU statistics to debugfs" 110 depends on AMD_IOMMU 111 select DEBUG_FS 112 ---help--- 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. 116 If unsure, say N. 117 118config AMD_IOMMU_V2 119 tristate "AMD IOMMU Version 2 driver" 120 depends on AMD_IOMMU 121 select MMU_NOTIFIER 122 ---help--- 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. 126 127# Intel IOMMU support 128config DMAR_TABLE 129 bool 130 131config INTEL_IOMMU 132 bool "Support for Intel IOMMU using DMA Remapping Devices" 133 depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC) 134 select IOMMU_API 135 select IOMMU_IOVA 136 select DMAR_TABLE 137 help 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 142 remapping devices. 143 144config INTEL_IOMMU_SVM 145 bool "Support for Shared Virtual Memory with Intel IOMMU" 146 depends on INTEL_IOMMU && X86 147 select PCI_PASID 148 select MMU_NOTIFIER 149 help 150 Shared Virtual Memory (SVM) provides a facility for devices 151 to access DMA resources through process address space by 152 means of a Process Address Space ID (PASID). 153 154config INTEL_IOMMU_DEFAULT_ON 155 def_bool y 156 prompt "Enable Intel DMA Remapping Devices by default" 157 depends on INTEL_IOMMU 158 help 159 Selecting this option will enable a DMAR device at boot time if 160 one is found. If this option is not selected, DMAR support can 161 be enabled by passing intel_iommu=on to the kernel. 162 163config INTEL_IOMMU_BROKEN_GFX_WA 164 bool "Workaround broken graphics drivers (going away soon)" 165 depends on INTEL_IOMMU && BROKEN && X86 166 ---help--- 167 Current Graphics drivers tend to use physical address 168 for DMA and avoid using DMA APIs. Setting this config 169 option permits the IOMMU driver to set a unity map for 170 all the OS-visible memory. Hence the driver can continue 171 to use physical addresses for DMA, at least until this 172 option is removed in the 2.6.32 kernel. 173 174config INTEL_IOMMU_FLOPPY_WA 175 def_bool y 176 depends on INTEL_IOMMU && X86 177 ---help--- 178 Floppy disk drivers are known to bypass DMA API calls 179 thereby failing to work when IOMMU is enabled. This 180 workaround will setup a 1:1 mapping for the first 181 16MiB to make floppy (an ISA device) work. 182 183config IRQ_REMAP 184 bool "Support for Interrupt Remapping" 185 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI 186 select DMAR_TABLE 187 ---help--- 188 Supports Interrupt remapping for IO-APIC and MSI devices. 189 To use x2apic mode in the CPU's which support x2APIC enhancements or 190 to support platforms with CPU's having > 8 bit APIC ID, say Y. 191 192# OMAP IOMMU support 193config OMAP_IOMMU 194 bool "OMAP IOMMU Support" 195 depends on ARM && MMU 196 depends on ARCH_OMAP2PLUS || COMPILE_TEST 197 select IOMMU_API 198 ---help--- 199 The OMAP3 media platform drivers depend on iommu support, 200 if you need them say Y here. 201 202config OMAP_IOMMU_DEBUG 203 bool "Export OMAP IOMMU internals in DebugFS" 204 depends on OMAP_IOMMU && DEBUG_FS 205 ---help--- 206 Select this to see extensive information about 207 the internal state of OMAP IOMMU in debugfs. 208 209 Say N unless you know you need this. 210 211config ROCKCHIP_IOMMU 212 bool "Rockchip IOMMU Support" 213 depends on ARM 214 depends on ARCH_ROCKCHIP || COMPILE_TEST 215 select IOMMU_API 216 select ARM_DMA_USE_IOMMU 217 help 218 Support for IOMMUs found on Rockchip rk32xx SOCs. 219 These IOMMUs allow virtualization of the address space used by most 220 cores within the multimedia subsystem. 221 Say Y here if you are using a Rockchip SoC that includes an IOMMU 222 device. 223 224config TEGRA_IOMMU_GART 225 bool "Tegra GART IOMMU Support" 226 depends on ARCH_TEGRA_2x_SOC 227 select IOMMU_API 228 help 229 Enables support for remapping discontiguous physical memory 230 shared with the operating system into contiguous I/O virtual 231 space through the GART (Graphics Address Relocation Table) 232 hardware included on Tegra SoCs. 233 234config TEGRA_IOMMU_SMMU 235 bool "NVIDIA Tegra SMMU Support" 236 depends on ARCH_TEGRA 237 depends on TEGRA_AHB 238 depends on TEGRA_MC 239 select IOMMU_API 240 help 241 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra 242 SoCs (Tegra30 up to Tegra210). 243 244config EXYNOS_IOMMU 245 bool "Exynos IOMMU Support" 246 depends on ARCH_EXYNOS && ARM && MMU 247 select IOMMU_API 248 select ARM_DMA_USE_IOMMU 249 help 250 Support for the IOMMU (System MMU) of Samsung Exynos application 251 processor family. This enables H/W multimedia accelerators to see 252 non-linear physical memory chunks as linear memory in their 253 address space. 254 255 If unsure, say N here. 256 257config EXYNOS_IOMMU_DEBUG 258 bool "Debugging log for Exynos IOMMU" 259 depends on EXYNOS_IOMMU 260 help 261 Select this to see the detailed log message that shows what 262 happens in the IOMMU driver. 263 264 Say N unless you need kernel log message for IOMMU debugging. 265 266config SHMOBILE_IPMMU 267 bool 268 269config SHMOBILE_IPMMU_TLB 270 bool 271 272config SHMOBILE_IOMMU 273 bool "IOMMU for Renesas IPMMU/IPMMUI" 274 default n 275 depends on ARM && MMU 276 depends on ARCH_SHMOBILE || COMPILE_TEST 277 select IOMMU_API 278 select ARM_DMA_USE_IOMMU 279 select SHMOBILE_IPMMU 280 select SHMOBILE_IPMMU_TLB 281 help 282 Support for Renesas IPMMU/IPMMUI. This option enables 283 remapping of DMA memory accesses from all of the IP blocks 284 on the ICB. 285 286 Warning: Drivers (including userspace drivers of UIO 287 devices) of the IP blocks on the ICB *must* use addresses 288 allocated from the IPMMU (iova) for DMA with this option 289 enabled. 290 291 If unsure, say N. 292 293choice 294 prompt "IPMMU/IPMMUI address space size" 295 default SHMOBILE_IOMMU_ADDRSIZE_2048MB 296 depends on SHMOBILE_IOMMU 297 help 298 This option sets IPMMU/IPMMUI address space size by 299 adjusting the 1st level page table size. The page table size 300 is calculated as follows: 301 302 page table size = number of page table entries * 4 bytes 303 number of page table entries = address space size / 1 MiB 304 305 For example, when the address space size is 2048 MiB, the 306 1st level page table size is 8192 bytes. 307 308 config SHMOBILE_IOMMU_ADDRSIZE_2048MB 309 bool "2 GiB" 310 311 config SHMOBILE_IOMMU_ADDRSIZE_1024MB 312 bool "1 GiB" 313 314 config SHMOBILE_IOMMU_ADDRSIZE_512MB 315 bool "512 MiB" 316 317 config SHMOBILE_IOMMU_ADDRSIZE_256MB 318 bool "256 MiB" 319 320 config SHMOBILE_IOMMU_ADDRSIZE_128MB 321 bool "128 MiB" 322 323 config SHMOBILE_IOMMU_ADDRSIZE_64MB 324 bool "64 MiB" 325 326 config SHMOBILE_IOMMU_ADDRSIZE_32MB 327 bool "32 MiB" 328 329endchoice 330 331config SHMOBILE_IOMMU_L1SIZE 332 int 333 default 8192 if SHMOBILE_IOMMU_ADDRSIZE_2048MB 334 default 4096 if SHMOBILE_IOMMU_ADDRSIZE_1024MB 335 default 2048 if SHMOBILE_IOMMU_ADDRSIZE_512MB 336 default 1024 if SHMOBILE_IOMMU_ADDRSIZE_256MB 337 default 512 if SHMOBILE_IOMMU_ADDRSIZE_128MB 338 default 256 if SHMOBILE_IOMMU_ADDRSIZE_64MB 339 default 128 if SHMOBILE_IOMMU_ADDRSIZE_32MB 340 341config IPMMU_VMSA 342 bool "Renesas VMSA-compatible IPMMU" 343 depends on ARM_LPAE 344 depends on ARCH_SHMOBILE || COMPILE_TEST 345 select IOMMU_API 346 select IOMMU_IO_PGTABLE_LPAE 347 select ARM_DMA_USE_IOMMU 348 help 349 Support for the Renesas VMSA-compatible IPMMU Renesas found in the 350 R-Mobile APE6 and R-Car H2/M2 SoCs. 351 352 If unsure, say N. 353 354config SPAPR_TCE_IOMMU 355 bool "sPAPR TCE IOMMU Support" 356 depends on PPC_POWERNV || PPC_PSERIES 357 select IOMMU_API 358 help 359 Enables bits of IOMMU API required by VFIO. The iommu_ops 360 is not implemented as it is not necessary for VFIO. 361 362# ARM IOMMU support 363config ARM_SMMU 364 bool "ARM Ltd. System MMU (SMMU) Support" 365 depends on (ARM64 || ARM) && MMU 366 select IOMMU_API 367 select IOMMU_IO_PGTABLE_LPAE 368 select ARM_DMA_USE_IOMMU if ARM 369 help 370 Support for implementations of the ARM System MMU architecture 371 versions 1 and 2. 372 373 Say Y here if your SoC includes an IOMMU device implementing 374 the ARM SMMU architecture. 375 376config ARM_SMMU_V3 377 bool "ARM Ltd. System MMU Version 3 (SMMUv3) Support" 378 depends on ARM64 && PCI 379 select IOMMU_API 380 select IOMMU_IO_PGTABLE_LPAE 381 select GENERIC_MSI_IRQ_DOMAIN 382 help 383 Support for implementations of the ARM System MMU architecture 384 version 3 providing translation support to a PCIe root complex. 385 386 Say Y here if your system includes an IOMMU device implementing 387 the ARM SMMUv3 architecture. 388 389config S390_IOMMU 390 def_bool y if S390 && PCI 391 depends on S390 && PCI 392 select IOMMU_API 393 help 394 Support for the IOMMU API for s390 PCI devices. 395 396endif # IOMMU_SUPPORT 397