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 default y
8 ---help---
9 Say Y here if you want to compile device drivers for IO Memory
10 Management Units into the kernel. These devices usually allow to
11 remap DMA requests and/or remap interrupts from other devices on the
12 system.
13
14if IOMMU_SUPPORT
15
16config OF_IOMMU
17 def_bool y
18 depends on OF
19
20config FSL_PAMU
21 bool "Freescale IOMMU support"
22 depends on PPC_E500MC
23 select IOMMU_API
24 select GENERIC_ALLOCATOR
25 help
26 Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
27 PAMU can authorize memory access, remap the memory address, and remap I/O
28 transaction types.
29
30# MSM IOMMU support
31config MSM_IOMMU
32 bool "MSM IOMMU Support"
33 depends on ARCH_MSM8X60 || ARCH_MSM8960
34 select IOMMU_API
35 help
36 Support for the IOMMUs found on certain Qualcomm SOCs.
37 These IOMMUs allow virtualization of the address space used by most
38 cores within the multimedia subsystem.
39
40 If unsure, say N here.
41
42config IOMMU_PGTABLES_L2
43 def_bool y
44 depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
45
46# AMD IOMMU support
47config AMD_IOMMU
48 bool "AMD IOMMU support"
49 select SWIOTLB
50 select PCI_MSI
51 select PCI_ATS
52 select PCI_PRI
53 select PCI_PASID
54 select IOMMU_API
55 depends on X86_64 && PCI && ACPI
56 ---help---
57 With this option you can enable support for AMD IOMMU hardware in
58 your system. An IOMMU is a hardware component which provides
59 remapping of DMA memory accesses from devices. With an AMD IOMMU you
60 can isolate the DMA memory of different devices and protect the
61 system from misbehaving device drivers or hardware.
62
63 You can find out if your system has an AMD IOMMU if you look into
64 your BIOS for an option to enable it or if you have an IVRS ACPI
65 table.
66
67config AMD_IOMMU_STATS
68 bool "Export AMD IOMMU statistics to debugfs"
69 depends on AMD_IOMMU
70 select DEBUG_FS
71 ---help---
72 This option enables code in the AMD IOMMU driver to collect various
73 statistics about whats happening in the driver and exports that
74 information to userspace via debugfs.
75 If unsure, say N.
76
77config AMD_IOMMU_V2
78 tristate "AMD IOMMU Version 2 driver"
79 depends on AMD_IOMMU && PROFILING
80 select MMU_NOTIFIER
81 ---help---
82 This option enables support for the AMD IOMMUv2 features of the IOMMU
83 hardware. Select this option if you want to use devices that support
84 the PCI PRI and PASID interface.
85
86# Intel IOMMU support
87config DMAR_TABLE
88 bool
89
90config INTEL_IOMMU
91 bool "Support for Intel IOMMU using DMA Remapping Devices"
92 depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC)
93 select IOMMU_API
94 select DMAR_TABLE
95 help
96 DMA remapping (DMAR) devices support enables independent address
97 translations for Direct Memory Access (DMA) from devices.
98 These DMA remapping devices are reported via ACPI tables
99 and include PCI device scope covered by these DMA
100 remapping devices.
101
102config INTEL_IOMMU_DEFAULT_ON
103 def_bool y
104 prompt "Enable Intel DMA Remapping Devices by default"
105 depends on INTEL_IOMMU
106 help
107 Selecting this option will enable a DMAR device at boot time if
108 one is found. If this option is not selected, DMAR support can
109 be enabled by passing intel_iommu=on to the kernel.
110
111config INTEL_IOMMU_BROKEN_GFX_WA
112 bool "Workaround broken graphics drivers (going away soon)"
113 depends on INTEL_IOMMU && BROKEN && X86
114 ---help---
115 Current Graphics drivers tend to use physical address
116 for DMA and avoid using DMA APIs. Setting this config
117 option permits the IOMMU driver to set a unity map for
118 all the OS-visible memory. Hence the driver can continue
119 to use physical addresses for DMA, at least until this
120 option is removed in the 2.6.32 kernel.
121
122config INTEL_IOMMU_FLOPPY_WA
123 def_bool y
124 depends on INTEL_IOMMU && X86
125 ---help---
126 Floppy disk drivers are known to bypass DMA API calls
127 thereby failing to work when IOMMU is enabled. This
128 workaround will setup a 1:1 mapping for the first
129 16MiB to make floppy (an ISA device) work.
130
131config IRQ_REMAP
132 bool "Support for Interrupt Remapping"
133 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
134 select DMAR_TABLE
135 ---help---
136 Supports Interrupt remapping for IO-APIC and MSI devices.
137 To use x2apic mode in the CPU's which support x2APIC enhancements or
138 to support platforms with CPU's having > 8 bit APIC ID, say Y.
139
140# OMAP IOMMU support
141config OMAP_IOMMU
142 bool "OMAP IOMMU Support"
143 depends on ARCH_OMAP2PLUS
144 select IOMMU_API
145
146config OMAP_IOVMM
147 tristate "OMAP IO Virtual Memory Manager Support"
148 depends on OMAP_IOMMU
149
150config OMAP_IOMMU_DEBUG
151 tristate "Export OMAP IOMMU/IOVMM internals in DebugFS"
152 depends on OMAP_IOVMM && DEBUG_FS
153 help
154 Select this to see extensive information about
155 the internal state of OMAP IOMMU/IOVMM in debugfs.
156
157 Say N unless you know you need this.
158
159config TEGRA_IOMMU_GART
160 bool "Tegra GART IOMMU Support"
161 depends on ARCH_TEGRA_2x_SOC
162 select IOMMU_API
163 help
164 Enables support for remapping discontiguous physical memory
165 shared with the operating system into contiguous I/O virtual
166 space through the GART (Graphics Address Relocation Table)
167 hardware included on Tegra SoCs.
168
169config TEGRA_IOMMU_SMMU
170 bool "Tegra SMMU IOMMU Support"
171 depends on ARCH_TEGRA && TEGRA_AHB
172 select IOMMU_API
173 help
174 Enables support for remapping discontiguous physical memory
175 shared with the operating system into contiguous I/O virtual
176 space through the SMMU (System Memory Management Unit)
177 hardware included on Tegra SoCs.
178
179config EXYNOS_IOMMU
180 bool "Exynos IOMMU Support"
181 depends on ARCH_EXYNOS && EXYNOS_DEV_SYSMMU
182 select IOMMU_API
183 help
184 Support for the IOMMU(System MMU) of Samsung Exynos application
185 processor family. This enables H/W multimedia accellerators to see
186 non-linear physical memory chunks as a linear memory in their
187 address spaces
188
189 If unsure, say N here.
190
191config EXYNOS_IOMMU_DEBUG
192 bool "Debugging log for Exynos IOMMU"
193 depends on EXYNOS_IOMMU
194 help
195 Select this to see the detailed log message that shows what
196 happens in the IOMMU driver
197
198 Say N unless you need kernel log message for IOMMU debugging
199
200config SHMOBILE_IPMMU
201 bool
202
203config SHMOBILE_IPMMU_TLB
204 bool
205
206config SHMOBILE_IOMMU
207 bool "IOMMU for Renesas IPMMU/IPMMUI"
208 default n
209 depends on ARM
210 depends on ARCH_SHMOBILE || COMPILE_TEST
211 select IOMMU_API
212 select ARM_DMA_USE_IOMMU
213 select SHMOBILE_IPMMU
214 select SHMOBILE_IPMMU_TLB
215 help
216 Support for Renesas IPMMU/IPMMUI. This option enables
217 remapping of DMA memory accesses from all of the IP blocks
218 on the ICB.
219
220 Warning: Drivers (including userspace drivers of UIO
221 devices) of the IP blocks on the ICB *must* use addresses
222 allocated from the IPMMU (iova) for DMA with this option
223 enabled.
224
225 If unsure, say N.
226
227choice
228 prompt "IPMMU/IPMMUI address space size"
229 default SHMOBILE_IOMMU_ADDRSIZE_2048MB
230 depends on SHMOBILE_IOMMU
231 help
232 This option sets IPMMU/IPMMUI address space size by
233 adjusting the 1st level page table size. The page table size
234 is calculated as follows:
235
236 page table size = number of page table entries * 4 bytes
237 number of page table entries = address space size / 1 MiB
238
239 For example, when the address space size is 2048 MiB, the
240 1st level page table size is 8192 bytes.
241
242 config SHMOBILE_IOMMU_ADDRSIZE_2048MB
243 bool "2 GiB"
244
245 config SHMOBILE_IOMMU_ADDRSIZE_1024MB
246 bool "1 GiB"
247
248 config SHMOBILE_IOMMU_ADDRSIZE_512MB
249 bool "512 MiB"
250
251 config SHMOBILE_IOMMU_ADDRSIZE_256MB
252 bool "256 MiB"
253
254 config SHMOBILE_IOMMU_ADDRSIZE_128MB
255 bool "128 MiB"
256
257 config SHMOBILE_IOMMU_ADDRSIZE_64MB
258 bool "64 MiB"
259
260 config SHMOBILE_IOMMU_ADDRSIZE_32MB
261 bool "32 MiB"
262
263endchoice
264
265config SHMOBILE_IOMMU_L1SIZE
266 int
267 default 8192 if SHMOBILE_IOMMU_ADDRSIZE_2048MB
268 default 4096 if SHMOBILE_IOMMU_ADDRSIZE_1024MB
269 default 2048 if SHMOBILE_IOMMU_ADDRSIZE_512MB
270 default 1024 if SHMOBILE_IOMMU_ADDRSIZE_256MB
271 default 512 if SHMOBILE_IOMMU_ADDRSIZE_128MB
272 default 256 if SHMOBILE_IOMMU_ADDRSIZE_64MB
273 default 128 if SHMOBILE_IOMMU_ADDRSIZE_32MB
274
275config SPAPR_TCE_IOMMU
276 bool "sPAPR TCE IOMMU Support"
277 depends on PPC_POWERNV || PPC_PSERIES
278 select IOMMU_API
279 help
280 Enables bits of IOMMU API required by VFIO. The iommu_ops
281 is not implemented as it is not necessary for VFIO.
282
283config ARM_SMMU
284 bool "ARM Ltd. System MMU (SMMU) Support"
285 depends on ARM64 || (ARM_LPAE && OF)
286 select IOMMU_API
287 select ARM_DMA_USE_IOMMU if ARM
288 help
289 Support for implementations of the ARM System MMU architecture
290 versions 1 and 2. The driver supports both v7l and v8l table
291 formats with 4k and 64k page sizes.
292
293 Say Y here if your SoC includes an IOMMU device implementing
294 the ARM SMMU architecture.
295
296endif # IOMMU_SUPPORT