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