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