1# SPDX-License-Identifier: GPL-2.0-only 2# The IOVA library may also be used by non-IOMMU_API users 3config IOMMU_IOVA 4 tristate 5 6# The IOASID library may also be used by non-IOMMU_API users 7config IOASID 8 tristate 9 10# IOMMU_API always gets selected by whoever wants it. 11config IOMMU_API 12 bool 13 14menuconfig IOMMU_SUPPORT 15 bool "IOMMU Hardware Support" 16 depends on MMU 17 default y 18 ---help--- 19 Say Y here if you want to compile device drivers for IO Memory 20 Management Units into the kernel. These devices usually allow to 21 remap DMA requests and/or remap interrupts from other devices on the 22 system. 23 24if IOMMU_SUPPORT 25 26menu "Generic IOMMU Pagetable Support" 27 28# Selected by the actual pagetable implementations 29config IOMMU_IO_PGTABLE 30 bool 31 32config IOMMU_IO_PGTABLE_LPAE 33 bool "ARMv7/v8 Long Descriptor Format" 34 select IOMMU_IO_PGTABLE 35 depends on ARM || ARM64 || (COMPILE_TEST && !GENERIC_ATOMIC64) 36 help 37 Enable support for the ARM long descriptor pagetable format. 38 This allocator supports 4K/2M/1G, 16K/32M and 64K/512M page 39 sizes at both stage-1 and stage-2, as well as address spaces 40 up to 48-bits in size. 41 42config IOMMU_IO_PGTABLE_LPAE_SELFTEST 43 bool "LPAE selftests" 44 depends on IOMMU_IO_PGTABLE_LPAE 45 help 46 Enable self-tests for LPAE page table allocator. This performs 47 a series of page-table consistency checks during boot. 48 49 If unsure, say N here. 50 51config IOMMU_IO_PGTABLE_ARMV7S 52 bool "ARMv7/v8 Short Descriptor Format" 53 select IOMMU_IO_PGTABLE 54 depends on ARM || ARM64 || COMPILE_TEST 55 help 56 Enable support for the ARM Short-descriptor pagetable format. 57 This supports 32-bit virtual and physical addresses mapped using 58 2-level tables with 4KB pages/1MB sections, and contiguous entries 59 for 64KB pages/16MB supersections if indicated by the IOMMU driver. 60 61config IOMMU_IO_PGTABLE_ARMV7S_SELFTEST 62 bool "ARMv7s selftests" 63 depends on IOMMU_IO_PGTABLE_ARMV7S 64 help 65 Enable self-tests for ARMv7s page table allocator. This performs 66 a series of page-table consistency checks during boot. 67 68 If unsure, say N here. 69 70endmenu 71 72config IOMMU_DEBUGFS 73 bool "Export IOMMU internals in DebugFS" 74 depends on DEBUG_FS 75 help 76 Allows exposure of IOMMU device internals. This option enables 77 the use of debugfs by IOMMU drivers as required. Devices can, 78 at initialization time, cause the IOMMU code to create a top-level 79 debug/iommu directory, and then populate a subdirectory with 80 entries as required. 81 82config IOMMU_DEFAULT_PASSTHROUGH 83 bool "IOMMU passthrough by default" 84 depends on IOMMU_API 85 help 86 Enable passthrough by default, removing the need to pass in 87 iommu.passthrough=on or iommu=pt through command line. If this 88 is enabled, you can still disable with iommu.passthrough=off 89 or iommu=nopt depending on the architecture. 90 91 If unsure, say N here. 92 93config OF_IOMMU 94 def_bool y 95 depends on OF && IOMMU_API 96 97# IOMMU-agnostic DMA-mapping layer 98config IOMMU_DMA 99 bool 100 select IOMMU_API 101 select IOMMU_IOVA 102 select IRQ_MSI_IOMMU 103 select NEED_SG_DMA_LENGTH 104 105config FSL_PAMU 106 bool "Freescale IOMMU support" 107 depends on PCI 108 depends on PHYS_64BIT 109 depends on PPC_E500MC || (COMPILE_TEST && PPC) 110 select IOMMU_API 111 select GENERIC_ALLOCATOR 112 help 113 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms. 114 PAMU can authorize memory access, remap the memory address, and remap I/O 115 transaction types. 116 117# MSM IOMMU support 118config MSM_IOMMU 119 bool "MSM IOMMU Support" 120 depends on ARM 121 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST 122 select IOMMU_API 123 select IOMMU_IO_PGTABLE_ARMV7S 124 help 125 Support for the IOMMUs found on certain Qualcomm SOCs. 126 These IOMMUs allow virtualization of the address space used by most 127 cores within the multimedia subsystem. 128 129 If unsure, say N here. 130 131config IOMMU_PGTABLES_L2 132 def_bool y 133 depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n 134 135# AMD IOMMU support 136config AMD_IOMMU 137 bool "AMD IOMMU support" 138 select SWIOTLB 139 select PCI_MSI 140 select PCI_ATS 141 select PCI_PRI 142 select PCI_PASID 143 select IOMMU_API 144 select IOMMU_IOVA 145 select IOMMU_DMA 146 depends on X86_64 && PCI && ACPI 147 ---help--- 148 With this option you can enable support for AMD IOMMU hardware in 149 your system. An IOMMU is a hardware component which provides 150 remapping of DMA memory accesses from devices. With an AMD IOMMU you 151 can isolate the DMA memory of different devices and protect the 152 system from misbehaving device drivers or hardware. 153 154 You can find out if your system has an AMD IOMMU if you look into 155 your BIOS for an option to enable it or if you have an IVRS ACPI 156 table. 157 158config AMD_IOMMU_V2 159 tristate "AMD IOMMU Version 2 driver" 160 depends on AMD_IOMMU 161 select MMU_NOTIFIER 162 ---help--- 163 This option enables support for the AMD IOMMUv2 features of the IOMMU 164 hardware. Select this option if you want to use devices that support 165 the PCI PRI and PASID interface. 166 167config AMD_IOMMU_DEBUGFS 168 bool "Enable AMD IOMMU internals in DebugFS" 169 depends on AMD_IOMMU && IOMMU_DEBUGFS 170 ---help--- 171 !!!WARNING!!! !!!WARNING!!! !!!WARNING!!! !!!WARNING!!! 172 173 DO NOT ENABLE THIS OPTION UNLESS YOU REALLY, -REALLY- KNOW WHAT YOU ARE DOING!!! 174 Exposes AMD IOMMU device internals in DebugFS. 175 176 This option is -NOT- intended for production environments, and should 177 not generally be enabled. 178 179# Intel IOMMU support 180config DMAR_TABLE 181 bool 182 183config INTEL_IOMMU 184 bool "Support for Intel IOMMU using DMA Remapping Devices" 185 depends on PCI_MSI && ACPI && (X86 || IA64) 186 select IOMMU_API 187 select IOMMU_IOVA 188 select NEED_DMA_MAP_STATE 189 select DMAR_TABLE 190 select SWIOTLB 191 select IOASID 192 help 193 DMA remapping (DMAR) devices support enables independent address 194 translations for Direct Memory Access (DMA) from devices. 195 These DMA remapping devices are reported via ACPI tables 196 and include PCI device scope covered by these DMA 197 remapping devices. 198 199config INTEL_IOMMU_DEBUGFS 200 bool "Export Intel IOMMU internals in Debugfs" 201 depends on INTEL_IOMMU && IOMMU_DEBUGFS 202 help 203 !!!WARNING!!! 204 205 DO NOT ENABLE THIS OPTION UNLESS YOU REALLY KNOW WHAT YOU ARE DOING!!! 206 207 Expose Intel IOMMU internals in Debugfs. 208 209 This option is -NOT- intended for production environments, and should 210 only be enabled for debugging Intel IOMMU. 211 212config INTEL_IOMMU_SVM 213 bool "Support for Shared Virtual Memory with Intel IOMMU" 214 depends on INTEL_IOMMU && X86 215 select PCI_PASID 216 select PCI_PRI 217 select MMU_NOTIFIER 218 select IOASID 219 help 220 Shared Virtual Memory (SVM) provides a facility for devices 221 to access DMA resources through process address space by 222 means of a Process Address Space ID (PASID). 223 224config INTEL_IOMMU_DEFAULT_ON 225 def_bool y 226 prompt "Enable Intel DMA Remapping Devices by default" 227 depends on INTEL_IOMMU 228 help 229 Selecting this option will enable a DMAR device at boot time if 230 one is found. If this option is not selected, DMAR support can 231 be enabled by passing intel_iommu=on to the kernel. 232 233config INTEL_IOMMU_BROKEN_GFX_WA 234 bool "Workaround broken graphics drivers (going away soon)" 235 depends on INTEL_IOMMU && BROKEN && X86 236 ---help--- 237 Current Graphics drivers tend to use physical address 238 for DMA and avoid using DMA APIs. Setting this config 239 option permits the IOMMU driver to set a unity map for 240 all the OS-visible memory. Hence the driver can continue 241 to use physical addresses for DMA, at least until this 242 option is removed in the 2.6.32 kernel. 243 244config INTEL_IOMMU_FLOPPY_WA 245 def_bool y 246 depends on INTEL_IOMMU && X86 247 ---help--- 248 Floppy disk drivers are known to bypass DMA API calls 249 thereby failing to work when IOMMU is enabled. This 250 workaround will setup a 1:1 mapping for the first 251 16MiB to make floppy (an ISA device) work. 252 253config INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON 254 bool "Enable Intel IOMMU scalable mode by default" 255 depends on INTEL_IOMMU 256 help 257 Selecting this option will enable by default the scalable mode if 258 hardware presents the capability. The scalable mode is defined in 259 VT-d 3.0. The scalable mode capability could be checked by reading 260 /sys/devices/virtual/iommu/dmar*/intel-iommu/ecap. If this option 261 is not selected, scalable mode support could also be enabled by 262 passing intel_iommu=sm_on to the kernel. If not sure, please use 263 the default value. 264 265config IRQ_REMAP 266 bool "Support for Interrupt Remapping" 267 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI 268 select DMAR_TABLE 269 ---help--- 270 Supports Interrupt remapping for IO-APIC and MSI devices. 271 To use x2apic mode in the CPU's which support x2APIC enhancements or 272 to support platforms with CPU's having > 8 bit APIC ID, say Y. 273 274# OMAP IOMMU support 275config OMAP_IOMMU 276 bool "OMAP IOMMU Support" 277 depends on ARM && MMU || (COMPILE_TEST && (ARM || ARM64 || IA64 || SPARC)) 278 depends on ARCH_OMAP2PLUS || COMPILE_TEST 279 select IOMMU_API 280 ---help--- 281 The OMAP3 media platform drivers depend on iommu support, 282 if you need them say Y here. 283 284config OMAP_IOMMU_DEBUG 285 bool "Export OMAP IOMMU internals in DebugFS" 286 depends on OMAP_IOMMU && DEBUG_FS 287 ---help--- 288 Select this to see extensive information about 289 the internal state of OMAP IOMMU in debugfs. 290 291 Say N unless you know you need this. 292 293config ROCKCHIP_IOMMU 294 bool "Rockchip IOMMU Support" 295 depends on ARM || ARM64 || (COMPILE_TEST && (ARM64 || IA64 || SPARC)) 296 depends on ARCH_ROCKCHIP || COMPILE_TEST 297 select IOMMU_API 298 select ARM_DMA_USE_IOMMU 299 help 300 Support for IOMMUs found on Rockchip rk32xx SOCs. 301 These IOMMUs allow virtualization of the address space used by most 302 cores within the multimedia subsystem. 303 Say Y here if you are using a Rockchip SoC that includes an IOMMU 304 device. 305 306config TEGRA_IOMMU_GART 307 bool "Tegra GART IOMMU Support" 308 depends on ARCH_TEGRA_2x_SOC 309 depends on TEGRA_MC 310 select IOMMU_API 311 help 312 Enables support for remapping discontiguous physical memory 313 shared with the operating system into contiguous I/O virtual 314 space through the GART (Graphics Address Relocation Table) 315 hardware included on Tegra SoCs. 316 317config TEGRA_IOMMU_SMMU 318 bool "NVIDIA Tegra SMMU Support" 319 depends on ARCH_TEGRA 320 depends on TEGRA_AHB 321 depends on TEGRA_MC 322 select IOMMU_API 323 help 324 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra 325 SoCs (Tegra30 up to Tegra210). 326 327config EXYNOS_IOMMU 328 bool "Exynos IOMMU Support" 329 depends on ARCH_EXYNOS && MMU || (COMPILE_TEST && (ARM || ARM64 || IA64 || SPARC)) 330 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes 331 select IOMMU_API 332 select ARM_DMA_USE_IOMMU 333 help 334 Support for the IOMMU (System MMU) of Samsung Exynos application 335 processor family. This enables H/W multimedia accelerators to see 336 non-linear physical memory chunks as linear memory in their 337 address space. 338 339 If unsure, say N here. 340 341config EXYNOS_IOMMU_DEBUG 342 bool "Debugging log for Exynos IOMMU" 343 depends on EXYNOS_IOMMU 344 help 345 Select this to see the detailed log message that shows what 346 happens in the IOMMU driver. 347 348 Say N unless you need kernel log message for IOMMU debugging. 349 350config IPMMU_VMSA 351 bool "Renesas VMSA-compatible IPMMU" 352 depends on ARM || IOMMU_DMA 353 depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64) 354 select IOMMU_API 355 select IOMMU_IO_PGTABLE_LPAE 356 select ARM_DMA_USE_IOMMU 357 help 358 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile 359 APE6, R-Car Gen2, and R-Car Gen3 SoCs. 360 361 If unsure, say N. 362 363config SPAPR_TCE_IOMMU 364 bool "sPAPR TCE IOMMU Support" 365 depends on PPC_POWERNV || PPC_PSERIES 366 select IOMMU_API 367 help 368 Enables bits of IOMMU API required by VFIO. The iommu_ops 369 is not implemented as it is not necessary for VFIO. 370 371# ARM IOMMU support 372config ARM_SMMU 373 tristate "ARM Ltd. System MMU (SMMU) Support" 374 depends on (ARM64 || ARM || (COMPILE_TEST && !GENERIC_ATOMIC64)) && MMU 375 select IOMMU_API 376 select IOMMU_IO_PGTABLE_LPAE 377 select ARM_DMA_USE_IOMMU if ARM 378 help 379 Support for implementations of the ARM System MMU architecture 380 versions 1 and 2. 381 382 Say Y here if your SoC includes an IOMMU device implementing 383 the ARM SMMU architecture. 384 385config ARM_SMMU_LEGACY_DT_BINDINGS 386 bool "Support the legacy \"mmu-masters\" devicetree bindings" 387 depends on ARM_SMMU=y && OF 388 help 389 Support for the badly designed and deprecated "mmu-masters" 390 devicetree bindings. This allows some DMA masters to attach 391 to the SMMU but does not provide any support via the DMA API. 392 If you're lucky, you might be able to get VFIO up and running. 393 394 If you say Y here then you'll make me very sad. Instead, say N 395 and move your firmware to the utopian future that was 2016. 396 397config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT 398 bool "Default to disabling bypass on ARM SMMU v1 and v2" 399 depends on ARM_SMMU 400 default y 401 help 402 Say Y here to (by default) disable bypass streams such that 403 incoming transactions from devices that are not attached to 404 an iommu domain will report an abort back to the device and 405 will not be allowed to pass through the SMMU. 406 407 Any old kernels that existed before this KConfig was 408 introduced would default to _allowing_ bypass (AKA the 409 equivalent of NO for this config). However the default for 410 this option is YES because the old behavior is insecure. 411 412 There are few reasons to allow unmatched stream bypass, and 413 even fewer good ones. If saying YES here breaks your board 414 you should work on fixing your board. This KConfig option 415 is expected to be removed in the future and we'll simply 416 hardcode the bypass disable in the code. 417 418 NOTE: the kernel command line parameter 419 'arm-smmu.disable_bypass' will continue to override this 420 config. 421 422config ARM_SMMU_V3 423 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support" 424 depends on ARM64 425 select IOMMU_API 426 select IOMMU_IO_PGTABLE_LPAE 427 select GENERIC_MSI_IRQ_DOMAIN 428 help 429 Support for implementations of the ARM System MMU architecture 430 version 3 providing translation support to a PCIe root complex. 431 432 Say Y here if your system includes an IOMMU device implementing 433 the ARM SMMUv3 architecture. 434 435config S390_IOMMU 436 def_bool y if S390 && PCI 437 depends on S390 && PCI 438 select IOMMU_API 439 help 440 Support for the IOMMU API for s390 PCI devices. 441 442config S390_CCW_IOMMU 443 bool "S390 CCW IOMMU Support" 444 depends on S390 && CCW || COMPILE_TEST 445 select IOMMU_API 446 help 447 Enables bits of IOMMU API required by VFIO. The iommu_ops 448 is not implemented as it is not necessary for VFIO. 449 450config S390_AP_IOMMU 451 bool "S390 AP IOMMU Support" 452 depends on S390 && ZCRYPT || COMPILE_TEST 453 select IOMMU_API 454 help 455 Enables bits of IOMMU API required by VFIO. The iommu_ops 456 is not implemented as it is not necessary for VFIO. 457 458config MTK_IOMMU 459 bool "MTK IOMMU Support" 460 depends on HAS_DMA 461 depends on ARCH_MEDIATEK || COMPILE_TEST 462 select ARM_DMA_USE_IOMMU 463 select IOMMU_API 464 select IOMMU_DMA 465 select IOMMU_IO_PGTABLE_ARMV7S 466 select MEMORY 467 select MTK_SMI 468 help 469 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia 470 Memory Management Unit. This option enables remapping of DMA memory 471 accesses for the multimedia subsystem. 472 473 If unsure, say N here. 474 475config MTK_IOMMU_V1 476 bool "MTK IOMMU Version 1 (M4U gen1) Support" 477 depends on ARM 478 depends on ARCH_MEDIATEK || COMPILE_TEST 479 select ARM_DMA_USE_IOMMU 480 select IOMMU_API 481 select MEMORY 482 select MTK_SMI 483 help 484 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is 485 Multimedia Memory Managememt Unit. This option enables remapping of 486 DMA memory accesses for the multimedia subsystem. 487 488 if unsure, say N here. 489 490config QCOM_IOMMU 491 # Note: iommu drivers cannot (yet?) be built as modules 492 bool "Qualcomm IOMMU Support" 493 depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64) 494 select IOMMU_API 495 select IOMMU_IO_PGTABLE_LPAE 496 select ARM_DMA_USE_IOMMU 497 help 498 Support for IOMMU on certain Qualcomm SoCs. 499 500config HYPERV_IOMMU 501 bool "Hyper-V x2APIC IRQ Handling" 502 depends on HYPERV && X86 503 select IOMMU_API 504 default HYPERV 505 help 506 Stub IOMMU driver to handle IRQs as to allow Hyper-V Linux 507 guests to run with x2APIC mode enabled. 508 509config VIRTIO_IOMMU 510 tristate "Virtio IOMMU driver" 511 depends on VIRTIO 512 depends on ARM64 513 select IOMMU_API 514 select INTERVAL_TREE 515 help 516 Para-virtualised IOMMU driver with virtio. 517 518 Say Y here if you intend to run this kernel as a guest. 519 520endif # IOMMU_SUPPORT 521