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 70config IOMMU_IO_PGTABLE_DART 71 bool "Apple DART Formats" 72 select IOMMU_IO_PGTABLE 73 depends on ARM64 || (COMPILE_TEST && !GENERIC_ATOMIC64) 74 help 75 Enable support for the Apple DART pagetable formats. These include 76 the t8020 and t6000/t8110 DART formats used in Apple M1/M2 family 77 SoCs. 78 79 If unsure, say N here. 80 81endmenu 82 83config IOMMU_DEBUGFS 84 bool "Export IOMMU internals in DebugFS" 85 depends on DEBUG_FS 86 help 87 Allows exposure of IOMMU device internals. This option enables 88 the use of debugfs by IOMMU drivers as required. Devices can, 89 at initialization time, cause the IOMMU code to create a top-level 90 debug/iommu directory, and then populate a subdirectory with 91 entries as required. 92 93choice 94 prompt "IOMMU default domain type" 95 depends on IOMMU_API 96 default IOMMU_DEFAULT_DMA_LAZY if X86 || IA64 97 default IOMMU_DEFAULT_DMA_STRICT 98 help 99 Choose the type of IOMMU domain used to manage DMA API usage by 100 device drivers. The options here typically represent different 101 levels of tradeoff between robustness/security and performance, 102 depending on the IOMMU driver. Not all IOMMUs support all options. 103 This choice can be overridden at boot via the command line, and for 104 some devices also at runtime via sysfs. 105 106 If unsure, keep the default. 107 108config IOMMU_DEFAULT_DMA_STRICT 109 bool "Translated - Strict" 110 help 111 Trusted devices use translation to restrict their access to only 112 DMA-mapped pages, with strict TLB invalidation on unmap. Equivalent 113 to passing "iommu.passthrough=0 iommu.strict=1" on the command line. 114 115 Untrusted devices always use this mode, with an additional layer of 116 bounce-buffering such that they cannot gain access to any unrelated 117 data within a mapped page. 118 119config IOMMU_DEFAULT_DMA_LAZY 120 bool "Translated - Lazy" 121 help 122 Trusted devices use translation to restrict their access to only 123 DMA-mapped pages, but with "lazy" batched TLB invalidation. This 124 mode allows higher performance with some IOMMUs due to reduced TLB 125 flushing, but at the cost of reduced isolation since devices may be 126 able to access memory for some time after it has been unmapped. 127 Equivalent to passing "iommu.passthrough=0 iommu.strict=0" on the 128 command line. 129 130 If this mode is not supported by the IOMMU driver, the effective 131 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT. 132 133config IOMMU_DEFAULT_PASSTHROUGH 134 bool "Passthrough" 135 help 136 Trusted devices are identity-mapped, giving them unrestricted access 137 to memory with minimal performance overhead. Equivalent to passing 138 "iommu.passthrough=1" (historically "iommu=pt") on the command line. 139 140 If this mode is not supported by the IOMMU driver, the effective 141 runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT. 142 143endchoice 144 145config OF_IOMMU 146 def_bool y 147 depends on OF && IOMMU_API 148 149# IOMMU-agnostic DMA-mapping layer 150config IOMMU_DMA 151 def_bool ARM64 || IA64 || X86 152 select DMA_OPS 153 select IOMMU_API 154 select IOMMU_IOVA 155 select IRQ_MSI_IOMMU 156 select NEED_SG_DMA_LENGTH 157 158# Shared Virtual Addressing 159config IOMMU_SVA 160 bool 161 select IOASID 162 163config FSL_PAMU 164 bool "Freescale IOMMU support" 165 depends on PCI 166 depends on PHYS_64BIT 167 depends on PPC_E500MC || (COMPILE_TEST && PPC) 168 select IOMMU_API 169 select GENERIC_ALLOCATOR 170 help 171 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms. 172 PAMU can authorize memory access, remap the memory address, and remap I/O 173 transaction types. 174 175# MSM IOMMU support 176config MSM_IOMMU 177 bool "MSM IOMMU Support" 178 depends on ARM 179 depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST 180 select IOMMU_API 181 select IOMMU_IO_PGTABLE_ARMV7S 182 help 183 Support for the IOMMUs found on certain Qualcomm SOCs. 184 These IOMMUs allow virtualization of the address space used by most 185 cores within the multimedia subsystem. 186 187 If unsure, say N here. 188 189source "drivers/iommu/amd/Kconfig" 190source "drivers/iommu/intel/Kconfig" 191 192config IRQ_REMAP 193 bool "Support for Interrupt Remapping" 194 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI 195 select DMAR_TABLE 196 help 197 Supports Interrupt remapping for IO-APIC and MSI devices. 198 To use x2apic mode in the CPU's which support x2APIC enhancements or 199 to support platforms with CPU's having > 8 bit APIC ID, say Y. 200 201# OMAP IOMMU support 202config OMAP_IOMMU 203 bool "OMAP IOMMU Support" 204 depends on ARCH_OMAP2PLUS || COMPILE_TEST 205 select IOMMU_API 206 help 207 The OMAP3 media platform drivers depend on iommu support, 208 if you need them say Y here. 209 210config OMAP_IOMMU_DEBUG 211 bool "Export OMAP IOMMU internals in DebugFS" 212 depends on OMAP_IOMMU && DEBUG_FS 213 help 214 Select this to see extensive information about 215 the internal state of OMAP IOMMU in debugfs. 216 217 Say N unless you know you need this. 218 219config ROCKCHIP_IOMMU 220 bool "Rockchip IOMMU Support" 221 depends on ARCH_ROCKCHIP || COMPILE_TEST 222 select IOMMU_API 223 select ARM_DMA_USE_IOMMU 224 help 225 Support for IOMMUs found on Rockchip rk32xx SOCs. 226 These IOMMUs allow virtualization of the address space used by most 227 cores within the multimedia subsystem. 228 Say Y here if you are using a Rockchip SoC that includes an IOMMU 229 device. 230 231config SUN50I_IOMMU 232 bool "Allwinner H6 IOMMU Support" 233 depends on HAS_DMA 234 depends on ARCH_SUNXI || COMPILE_TEST 235 select ARM_DMA_USE_IOMMU 236 select IOMMU_API 237 help 238 Support for the IOMMU introduced in the Allwinner H6 SoCs. 239 240config TEGRA_IOMMU_GART 241 bool "Tegra GART IOMMU Support" 242 depends on ARCH_TEGRA_2x_SOC 243 depends on TEGRA_MC 244 select IOMMU_API 245 help 246 Enables support for remapping discontiguous physical memory 247 shared with the operating system into contiguous I/O virtual 248 space through the GART (Graphics Address Relocation Table) 249 hardware included on Tegra SoCs. 250 251config TEGRA_IOMMU_SMMU 252 bool "NVIDIA Tegra SMMU Support" 253 depends on ARCH_TEGRA 254 depends on TEGRA_AHB 255 depends on TEGRA_MC 256 select IOMMU_API 257 help 258 This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra 259 SoCs (Tegra30 up to Tegra210). 260 261config EXYNOS_IOMMU 262 bool "Exynos IOMMU Support" 263 depends on ARCH_EXYNOS || COMPILE_TEST 264 depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes 265 select IOMMU_API 266 select ARM_DMA_USE_IOMMU 267 help 268 Support for the IOMMU (System MMU) of Samsung Exynos application 269 processor family. This enables H/W multimedia accelerators to see 270 non-linear physical memory chunks as linear memory in their 271 address space. 272 273 If unsure, say N here. 274 275config EXYNOS_IOMMU_DEBUG 276 bool "Debugging log for Exynos IOMMU" 277 depends on EXYNOS_IOMMU 278 help 279 Select this to see the detailed log message that shows what 280 happens in the IOMMU driver. 281 282 Say N unless you need kernel log message for IOMMU debugging. 283 284config IPMMU_VMSA 285 bool "Renesas VMSA-compatible IPMMU" 286 depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64) 287 select IOMMU_API 288 select IOMMU_IO_PGTABLE_LPAE 289 select ARM_DMA_USE_IOMMU 290 help 291 Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile 292 APE6, R-Car Gen{2,3} and RZ/G{1,2} SoCs. 293 294 If unsure, say N. 295 296config SPAPR_TCE_IOMMU 297 bool "sPAPR TCE IOMMU Support" 298 depends on PPC_POWERNV || PPC_PSERIES 299 select IOMMU_API 300 help 301 Enables bits of IOMMU API required by VFIO. The iommu_ops 302 is not implemented as it is not necessary for VFIO. 303 304config APPLE_DART 305 tristate "Apple DART IOMMU Support" 306 depends on ARCH_APPLE || (COMPILE_TEST && !GENERIC_ATOMIC64) 307 select IOMMU_API 308 select IOMMU_IO_PGTABLE_DART 309 default ARCH_APPLE 310 help 311 Support for Apple DART (Device Address Resolution Table) IOMMUs 312 found in Apple ARM SoCs like the M1. 313 This IOMMU is required for most peripherals using DMA to access 314 the main memory. 315 316 Say Y here if you are using an Apple SoC. 317 318# ARM IOMMU support 319config ARM_SMMU 320 tristate "ARM Ltd. System MMU (SMMU) Support" 321 depends on ARM64 || ARM || (COMPILE_TEST && !GENERIC_ATOMIC64) 322 select IOMMU_API 323 select IOMMU_IO_PGTABLE_LPAE 324 select ARM_DMA_USE_IOMMU if ARM 325 help 326 Support for implementations of the ARM System MMU architecture 327 versions 1 and 2. 328 329 Say Y here if your SoC includes an IOMMU device implementing 330 the ARM SMMU architecture. 331 332config ARM_SMMU_LEGACY_DT_BINDINGS 333 bool "Support the legacy \"mmu-masters\" devicetree bindings" 334 depends on ARM_SMMU=y && OF 335 help 336 Support for the badly designed and deprecated "mmu-masters" 337 devicetree bindings. This allows some DMA masters to attach 338 to the SMMU but does not provide any support via the DMA API. 339 If you're lucky, you might be able to get VFIO up and running. 340 341 If you say Y here then you'll make me very sad. Instead, say N 342 and move your firmware to the utopian future that was 2016. 343 344config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT 345 bool "Default to disabling bypass on ARM SMMU v1 and v2" 346 depends on ARM_SMMU 347 default y 348 help 349 Say Y here to (by default) disable bypass streams such that 350 incoming transactions from devices that are not attached to 351 an iommu domain will report an abort back to the device and 352 will not be allowed to pass through the SMMU. 353 354 Any old kernels that existed before this KConfig was 355 introduced would default to _allowing_ bypass (AKA the 356 equivalent of NO for this config). However the default for 357 this option is YES because the old behavior is insecure. 358 359 There are few reasons to allow unmatched stream bypass, and 360 even fewer good ones. If saying YES here breaks your board 361 you should work on fixing your board. This KConfig option 362 is expected to be removed in the future and we'll simply 363 hardcode the bypass disable in the code. 364 365 NOTE: the kernel command line parameter 366 'arm-smmu.disable_bypass' will continue to override this 367 config. 368 369config ARM_SMMU_QCOM 370 def_tristate y 371 depends on ARM_SMMU && ARCH_QCOM 372 select QCOM_SCM 373 help 374 When running on a Qualcomm platform that has the custom variant 375 of the ARM SMMU, this needs to be built into the SMMU driver. 376 377config ARM_SMMU_QCOM_DEBUG 378 bool "ARM SMMU QCOM implementation defined debug support" 379 depends on ARM_SMMU_QCOM 380 help 381 Support for implementation specific debug features in ARM SMMU 382 hardware found in QTI platforms. 383 384 Say Y here to enable debug for issues such as TLB sync timeouts 385 which requires implementation defined register dumps. 386 387config ARM_SMMU_V3 388 tristate "ARM Ltd. System MMU Version 3 (SMMUv3) Support" 389 depends on ARM64 390 select IOMMU_API 391 select IOMMU_IO_PGTABLE_LPAE 392 select GENERIC_MSI_IRQ_DOMAIN 393 help 394 Support for implementations of the ARM System MMU architecture 395 version 3 providing translation support to a PCIe root complex. 396 397 Say Y here if your system includes an IOMMU device implementing 398 the ARM SMMUv3 architecture. 399 400config ARM_SMMU_V3_SVA 401 bool "Shared Virtual Addressing support for the ARM SMMUv3" 402 depends on ARM_SMMU_V3 403 select IOMMU_SVA 404 select MMU_NOTIFIER 405 help 406 Support for sharing process address spaces with devices using the 407 SMMUv3. 408 409 Say Y here if your system supports SVA extensions such as PCIe PASID 410 and PRI. 411 412config S390_IOMMU 413 def_bool y if S390 && PCI 414 depends on S390 && PCI 415 select IOMMU_API 416 help 417 Support for the IOMMU API for s390 PCI devices. 418 419config S390_CCW_IOMMU 420 bool "S390 CCW IOMMU Support" 421 depends on S390 && CCW || COMPILE_TEST 422 select IOMMU_API 423 help 424 Enables bits of IOMMU API required by VFIO. The iommu_ops 425 is not implemented as it is not necessary for VFIO. 426 427config S390_AP_IOMMU 428 bool "S390 AP IOMMU Support" 429 depends on S390 && ZCRYPT || COMPILE_TEST 430 select IOMMU_API 431 help 432 Enables bits of IOMMU API required by VFIO. The iommu_ops 433 is not implemented as it is not necessary for VFIO. 434 435config MTK_IOMMU 436 tristate "MediaTek IOMMU Support" 437 depends on ARCH_MEDIATEK || COMPILE_TEST 438 select ARM_DMA_USE_IOMMU 439 select IOMMU_API 440 select IOMMU_IO_PGTABLE_ARMV7S 441 select MEMORY 442 select MTK_SMI 443 help 444 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia 445 Memory Management Unit. This option enables remapping of DMA memory 446 accesses for the multimedia subsystem. 447 448 If unsure, say N here. 449 450config MTK_IOMMU_V1 451 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support" 452 depends on ARM 453 depends on ARCH_MEDIATEK || COMPILE_TEST 454 select ARM_DMA_USE_IOMMU 455 select IOMMU_API 456 select MEMORY 457 select MTK_SMI 458 help 459 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is 460 Multimedia Memory Managememt Unit. This option enables remapping of 461 DMA memory accesses for the multimedia subsystem. 462 463 if unsure, say N here. 464 465config QCOM_IOMMU 466 # Note: iommu drivers cannot (yet?) be built as modules 467 bool "Qualcomm IOMMU Support" 468 depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64) 469 select QCOM_SCM 470 select IOMMU_API 471 select IOMMU_IO_PGTABLE_LPAE 472 select ARM_DMA_USE_IOMMU 473 help 474 Support for IOMMU on certain Qualcomm SoCs. 475 476config HYPERV_IOMMU 477 bool "Hyper-V x2APIC IRQ Handling" 478 depends on HYPERV && X86 479 select IOMMU_API 480 default HYPERV 481 help 482 Stub IOMMU driver to handle IRQs as to allow Hyper-V Linux 483 guests to run with x2APIC mode enabled. 484 485config VIRTIO_IOMMU 486 tristate "Virtio IOMMU driver" 487 depends on VIRTIO 488 depends on (ARM64 || X86) 489 select IOMMU_API 490 select INTERVAL_TREE 491 select ACPI_VIOT if ACPI 492 help 493 Para-virtualised IOMMU driver with virtio. 494 495 Say Y here if you intend to run this kernel as a guest. 496 497config SPRD_IOMMU 498 tristate "Unisoc IOMMU Support" 499 depends on ARCH_SPRD || COMPILE_TEST 500 select IOMMU_API 501 help 502 Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by 503 Unisoc's multimedia devices, such as display, Image codec(jpeg) 504 and a few signal processors, including VSP(video), GSP(graphic), 505 ISP(image), and CPP(camera pixel processor), etc. 506 507 Say Y here if you want to use the multimedia devices listed above. 508 509endif # IOMMU_SUPPORT 510