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