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 help 192 DMA remapping (DMAR) devices support enables independent address 193 translations for Direct Memory Access (DMA) from devices. 194 These DMA remapping devices are reported via ACPI tables 195 and include PCI device scope covered by these DMA 196 remapping devices. 197 198config INTEL_IOMMU_DEBUGFS 199 bool "Export Intel IOMMU internals in Debugfs" 200 depends on INTEL_IOMMU && IOMMU_DEBUGFS 201 help 202 !!!WARNING!!! 203 204 DO NOT ENABLE THIS OPTION UNLESS YOU REALLY KNOW WHAT YOU ARE DOING!!! 205 206 Expose Intel IOMMU internals in Debugfs. 207 208 This option is -NOT- intended for production environments, and should 209 only be enabled for debugging Intel IOMMU. 210 211config INTEL_IOMMU_SVM 212 bool "Support for Shared Virtual Memory with Intel IOMMU" 213 depends on INTEL_IOMMU && X86 214 select PCI_PASID 215 select PCI_PRI 216 select MMU_NOTIFIER 217 select IOASID 218 help 219 Shared Virtual Memory (SVM) provides a facility for devices 220 to access DMA resources through process address space by 221 means of a Process Address Space ID (PASID). 222 223config INTEL_IOMMU_DEFAULT_ON 224 def_bool y 225 prompt "Enable Intel DMA Remapping Devices by default" 226 depends on INTEL_IOMMU 227 help 228 Selecting this option will enable a DMAR device at boot time if 229 one is found. If this option is not selected, DMAR support can 230 be enabled by passing intel_iommu=on to the kernel. 231 232config INTEL_IOMMU_BROKEN_GFX_WA 233 bool "Workaround broken graphics drivers (going away soon)" 234 depends on INTEL_IOMMU && BROKEN && X86 235 ---help--- 236 Current Graphics drivers tend to use physical address 237 for DMA and avoid using DMA APIs. Setting this config 238 option permits the IOMMU driver to set a unity map for 239 all the OS-visible memory. Hence the driver can continue 240 to use physical addresses for DMA, at least until this 241 option is removed in the 2.6.32 kernel. 242 243config INTEL_IOMMU_FLOPPY_WA 244 def_bool y 245 depends on INTEL_IOMMU && X86 246 ---help--- 247 Floppy disk drivers are known to bypass DMA API calls 248 thereby failing to work when IOMMU is enabled. This 249 workaround will setup a 1:1 mapping for the first 250 16MiB to make floppy (an ISA device) work. 251 252config INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON 253 bool "Enable Intel IOMMU scalable mode by default" 254 depends on INTEL_IOMMU 255 help 256 Selecting this option will enable by default the scalable mode if 257 hardware presents the capability. The scalable mode is defined in 258 VT-d 3.0. The scalable mode capability could be checked by reading 259 /sys/devices/virtual/iommu/dmar*/intel-iommu/ecap. If this option 260 is not selected, scalable mode support could also be enabled by 261 passing intel_iommu=sm_on to the kernel. If not sure, please use 262 the default value. 263 264config IRQ_REMAP 265 bool "Support for Interrupt Remapping" 266 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI 267 select DMAR_TABLE 268 ---help--- 269 Supports Interrupt remapping for IO-APIC and MSI devices. 270 To use x2apic mode in the CPU's which support x2APIC enhancements or 271 to support platforms with CPU's having > 8 bit APIC ID, say Y. 272 273# OMAP IOMMU support 274config OMAP_IOMMU 275 bool "OMAP IOMMU Support" 276 depends on ARM && MMU 277 depends on ARCH_OMAP2PLUS || COMPILE_TEST 278 select IOMMU_API 279 ---help--- 280 The OMAP3 media platform drivers depend on iommu support, 281 if you need them say Y here. 282 283config OMAP_IOMMU_DEBUG 284 bool "Export OMAP IOMMU internals in DebugFS" 285 depends on OMAP_IOMMU && DEBUG_FS 286 ---help--- 287 Select this to see extensive information about 288 the internal state of OMAP IOMMU in debugfs. 289 290 Say N unless you know you need this. 291 292config ROCKCHIP_IOMMU 293 bool "Rockchip IOMMU Support" 294 depends on ARM || ARM64 295 depends on ARCH_ROCKCHIP || COMPILE_TEST 296 select IOMMU_API 297 select ARM_DMA_USE_IOMMU 298 help 299 Support for IOMMUs found on Rockchip rk32xx SOCs. 300 These IOMMUs allow virtualization of the address space used by most 301 cores within the multimedia subsystem. 302 Say Y here if you are using a Rockchip SoC that includes an IOMMU 303 device. 304 305config TEGRA_IOMMU_GART 306 bool "Tegra GART IOMMU Support" 307 depends on ARCH_TEGRA_2x_SOC 308 depends on TEGRA_MC 309 select IOMMU_API 310 help 311 Enables support for remapping discontiguous physical memory 312 shared with the operating system into contiguous I/O virtual 313 space through the GART (Graphics Address Relocation Table) 314 hardware included on Tegra SoCs. 315 316config TEGRA_IOMMU_SMMU 317 bool "NVIDIA Tegra SMMU Support" 318 depends on ARCH_TEGRA 319 depends on TEGRA_AHB 320 depends on TEGRA_MC 321 select IOMMU_API 322 help 323 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra 324 SoCs (Tegra30 up to Tegra210). 325 326config EXYNOS_IOMMU 327 bool "Exynos IOMMU Support" 328 depends on ARCH_EXYNOS && MMU 329 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes 330 select IOMMU_API 331 select ARM_DMA_USE_IOMMU 332 help 333 Support for the IOMMU (System MMU) of Samsung Exynos application 334 processor family. This enables H/W multimedia accelerators to see 335 non-linear physical memory chunks as linear memory in their 336 address space. 337 338 If unsure, say N here. 339 340config EXYNOS_IOMMU_DEBUG 341 bool "Debugging log for Exynos IOMMU" 342 depends on EXYNOS_IOMMU 343 help 344 Select this to see the detailed log message that shows what 345 happens in the IOMMU driver. 346 347 Say N unless you need kernel log message for IOMMU debugging. 348 349config IPMMU_VMSA 350 bool "Renesas VMSA-compatible IPMMU" 351 depends on ARM || IOMMU_DMA 352 depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64) 353 select IOMMU_API 354 select IOMMU_IO_PGTABLE_LPAE 355 select ARM_DMA_USE_IOMMU 356 help 357 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile 358 APE6, R-Car Gen2, and R-Car Gen3 SoCs. 359 360 If unsure, say N. 361 362config SPAPR_TCE_IOMMU 363 bool "sPAPR TCE IOMMU Support" 364 depends on PPC_POWERNV || PPC_PSERIES 365 select IOMMU_API 366 help 367 Enables bits of IOMMU API required by VFIO. The iommu_ops 368 is not implemented as it is not necessary for VFIO. 369 370# ARM IOMMU support 371config ARM_SMMU 372 tristate "ARM Ltd. System MMU (SMMU) Support" 373 depends on (ARM64 || ARM) && MMU 374 select IOMMU_API 375 select IOMMU_IO_PGTABLE_LPAE 376 select ARM_DMA_USE_IOMMU if ARM 377 help 378 Support for implementations of the ARM System MMU architecture 379 versions 1 and 2. 380 381 Say Y here if your SoC includes an IOMMU device implementing 382 the ARM SMMU architecture. 383 384config ARM_SMMU_LEGACY_DT_BINDINGS 385 bool "Support the legacy \"mmu-masters\" devicetree bindings" 386 depends on ARM_SMMU=y && OF 387 help 388 Support for the badly designed and deprecated "mmu-masters" 389 devicetree bindings. This allows some DMA masters to attach 390 to the SMMU but does not provide any support via the DMA API. 391 If you're lucky, you might be able to get VFIO up and running. 392 393 If you say Y here then you'll make me very sad. Instead, say N 394 and move your firmware to the utopian future that was 2016. 395 396config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT 397 bool "Default to disabling bypass on ARM SMMU v1 and v2" 398 depends on ARM_SMMU 399 default y 400 help 401 Say Y here to (by default) disable bypass streams such that 402 incoming transactions from devices that are not attached to 403 an iommu domain will report an abort back to the device and 404 will not be allowed to pass through the SMMU. 405 406 Any old kernels that existed before this KConfig was 407 introduced would default to _allowing_ bypass (AKA the 408 equivalent of NO for this config). However the default for 409 this option is YES because the old behavior is insecure. 410 411 There are few reasons to allow unmatched stream bypass, and 412 even fewer good ones. If saying YES here breaks your board 413 you should work on fixing your board. This KConfig option 414 is expected to be removed in the future and we'll simply 415 hardcode the bypass disable in the code. 416 417 NOTE: the kernel command line parameter 418 'arm-smmu.disable_bypass' will continue to override this 419 config. 420 421config ARM_SMMU_V3 422 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support" 423 depends on ARM64 424 select IOMMU_API 425 select IOMMU_IO_PGTABLE_LPAE 426 select GENERIC_MSI_IRQ_DOMAIN 427 help 428 Support for implementations of the ARM System MMU architecture 429 version 3 providing translation support to a PCIe root complex. 430 431 Say Y here if your system includes an IOMMU device implementing 432 the ARM SMMUv3 architecture. 433 434config S390_IOMMU 435 def_bool y if S390 && PCI 436 depends on S390 && PCI 437 select IOMMU_API 438 help 439 Support for the IOMMU API for s390 PCI devices. 440 441config S390_CCW_IOMMU 442 bool "S390 CCW IOMMU Support" 443 depends on S390 && CCW 444 select IOMMU_API 445 help 446 Enables bits of IOMMU API required by VFIO. The iommu_ops 447 is not implemented as it is not necessary for VFIO. 448 449config S390_AP_IOMMU 450 bool "S390 AP IOMMU Support" 451 depends on S390 && ZCRYPT 452 select IOMMU_API 453 help 454 Enables bits of IOMMU API required by VFIO. The iommu_ops 455 is not implemented as it is not necessary for VFIO. 456 457config MTK_IOMMU 458 bool "MTK IOMMU Support" 459 depends on ARM || ARM64 460 depends on ARCH_MEDIATEK || COMPILE_TEST 461 select ARM_DMA_USE_IOMMU 462 select IOMMU_API 463 select IOMMU_DMA 464 select IOMMU_IO_PGTABLE_ARMV7S 465 select MEMORY 466 select MTK_SMI 467 help 468 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia 469 Memory Management Unit. This option enables remapping of DMA memory 470 accesses for the multimedia subsystem. 471 472 If unsure, say N here. 473 474config MTK_IOMMU_V1 475 bool "MTK IOMMU Version 1 (M4U gen1) Support" 476 depends on ARM 477 depends on ARCH_MEDIATEK || COMPILE_TEST 478 select ARM_DMA_USE_IOMMU 479 select IOMMU_API 480 select MEMORY 481 select MTK_SMI 482 help 483 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is 484 Multimedia Memory Managememt Unit. This option enables remapping of 485 DMA memory accesses for the multimedia subsystem. 486 487 if unsure, say N here. 488 489config QCOM_IOMMU 490 # Note: iommu drivers cannot (yet?) be built as modules 491 bool "Qualcomm IOMMU Support" 492 depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64) 493 select IOMMU_API 494 select IOMMU_IO_PGTABLE_LPAE 495 select ARM_DMA_USE_IOMMU 496 help 497 Support for IOMMU on certain Qualcomm SoCs. 498 499config HYPERV_IOMMU 500 bool "Hyper-V x2APIC IRQ Handling" 501 depends on HYPERV && X86 502 select IOMMU_API 503 default HYPERV 504 help 505 Stub IOMMU driver to handle IRQs as to allow Hyper-V Linux 506 guests to run with x2APIC mode enabled. 507 508config VIRTIO_IOMMU 509 bool "Virtio IOMMU driver" 510 depends on VIRTIO=y 511 depends on ARM64 512 select IOMMU_API 513 select INTERVAL_TREE 514 help 515 Para-virtualised IOMMU driver with virtio. 516 517 Say Y here if you intend to run this kernel as a guest. 518 519endif # IOMMU_SUPPORT 520