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