xref: /openbmc/linux/drivers/iommu/Kconfig (revision 56b77ba1)
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
156# Shared Virtual Addressing
157config IOMMU_SVA
158	bool
159
160config FSL_PAMU
161	bool "Freescale IOMMU support"
162	depends on PCI
163	depends on PHYS_64BIT
164	depends on PPC_E500MC || (COMPILE_TEST && PPC)
165	select IOMMU_API
166	select GENERIC_ALLOCATOR
167	help
168	  Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
169	  PAMU can authorize memory access, remap the memory address, and remap I/O
170	  transaction types.
171
172# MSM IOMMU support
173config MSM_IOMMU
174	bool "MSM IOMMU Support"
175	depends on ARM
176	depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
177	select IOMMU_API
178	select IOMMU_IO_PGTABLE_ARMV7S
179	help
180	  Support for the IOMMUs found on certain Qualcomm SOCs.
181	  These IOMMUs allow virtualization of the address space used by most
182	  cores within the multimedia subsystem.
183
184	  If unsure, say N here.
185
186source "drivers/iommu/amd/Kconfig"
187source "drivers/iommu/intel/Kconfig"
188source "drivers/iommu/iommufd/Kconfig"
189
190config IRQ_REMAP
191	bool "Support for Interrupt Remapping"
192	depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
193	select DMAR_TABLE
194	help
195	  Supports Interrupt remapping for IO-APIC and MSI devices.
196	  To use x2apic mode in the CPU's which support x2APIC enhancements or
197	  to support platforms with CPU's having > 8 bit APIC ID, say Y.
198
199# OMAP IOMMU support
200config OMAP_IOMMU
201	bool "OMAP IOMMU Support"
202	depends on ARCH_OMAP2PLUS || COMPILE_TEST
203	select IOMMU_API
204	help
205	  The OMAP3 media platform drivers depend on iommu support,
206	  if you need them say Y here.
207
208config OMAP_IOMMU_DEBUG
209	bool "Export OMAP IOMMU internals in DebugFS"
210	depends on OMAP_IOMMU && DEBUG_FS
211	help
212	  Select this to see extensive information about
213	  the internal state of OMAP IOMMU in debugfs.
214
215	  Say N unless you know you need this.
216
217config ROCKCHIP_IOMMU
218	bool "Rockchip IOMMU Support"
219	depends on ARCH_ROCKCHIP || COMPILE_TEST
220	select IOMMU_API
221	select ARM_DMA_USE_IOMMU
222	help
223	  Support for IOMMUs found on Rockchip rk32xx SOCs.
224	  These IOMMUs allow virtualization of the address space used by most
225	  cores within the multimedia subsystem.
226	  Say Y here if you are using a Rockchip SoC that includes an IOMMU
227	  device.
228
229config SUN50I_IOMMU
230	bool "Allwinner H6 IOMMU Support"
231	depends on HAS_DMA
232	depends on ARCH_SUNXI || COMPILE_TEST
233	select ARM_DMA_USE_IOMMU
234	select IOMMU_API
235	help
236	  Support for the IOMMU introduced in the Allwinner H6 SoCs.
237
238config TEGRA_IOMMU_GART
239	bool "Tegra GART IOMMU Support"
240	depends on ARCH_TEGRA_2x_SOC
241	depends on TEGRA_MC
242	select IOMMU_API
243	help
244	  Enables support for remapping discontiguous physical memory
245	  shared with the operating system into contiguous I/O virtual
246	  space through the GART (Graphics Address Relocation Table)
247	  hardware included on Tegra SoCs.
248
249config TEGRA_IOMMU_SMMU
250	bool "NVIDIA Tegra SMMU Support"
251	depends on ARCH_TEGRA
252	depends on TEGRA_AHB
253	depends on TEGRA_MC
254	select IOMMU_API
255	help
256	  This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
257	  SoCs (Tegra30 up to Tegra210).
258
259config EXYNOS_IOMMU
260	bool "Exynos IOMMU Support"
261	depends on ARCH_EXYNOS || COMPILE_TEST
262	depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
263	select IOMMU_API
264	select ARM_DMA_USE_IOMMU
265	help
266	  Support for the IOMMU (System MMU) of Samsung Exynos application
267	  processor family. This enables H/W multimedia accelerators to see
268	  non-linear physical memory chunks as linear memory in their
269	  address space.
270
271	  If unsure, say N here.
272
273config EXYNOS_IOMMU_DEBUG
274	bool "Debugging log for Exynos IOMMU"
275	depends on EXYNOS_IOMMU
276	help
277	  Select this to see the detailed log message that shows what
278	  happens in the IOMMU driver.
279
280	  Say N unless you need kernel log message for IOMMU debugging.
281
282config IPMMU_VMSA
283	bool "Renesas VMSA-compatible IPMMU"
284	depends on ARCH_RENESAS || COMPILE_TEST
285	depends on !GENERIC_ATOMIC64	# for IOMMU_IO_PGTABLE_LPAE
286	select IOMMU_API
287	select IOMMU_IO_PGTABLE_LPAE
288	select ARM_DMA_USE_IOMMU
289	help
290	  Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
291	  APE6, R-Car Gen{2,3} and RZ/G{1,2} SoCs.
292
293	  If unsure, say N.
294
295config SPAPR_TCE_IOMMU
296	bool "sPAPR TCE IOMMU Support"
297	depends on PPC_POWERNV || PPC_PSERIES
298	select IOMMU_API
299	help
300	  Enables bits of IOMMU API required by VFIO. The iommu_ops
301	  is not implemented as it is not necessary for VFIO.
302
303config APPLE_DART
304	tristate "Apple DART IOMMU Support"
305	depends on ARCH_APPLE || COMPILE_TEST
306	depends on !GENERIC_ATOMIC64	# for IOMMU_IO_PGTABLE_DART
307	select IOMMU_API
308	select IOMMU_IO_PGTABLE_DART
309	default ARCH_APPLE
310	help
311	  Support for Apple DART (Device Address Resolution Table) IOMMUs
312	  found in Apple ARM SoCs like the M1.
313	  This IOMMU is required for most peripherals using DMA to access
314	  the main memory.
315
316	  Say Y here if you are using an Apple SoC.
317
318# ARM IOMMU support
319config ARM_SMMU
320	tristate "ARM Ltd. System MMU (SMMU) Support"
321	depends on ARM64 || ARM || COMPILE_TEST
322	depends on !GENERIC_ATOMIC64	# for IOMMU_IO_PGTABLE_LPAE
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 MTK_IOMMU
421	tristate "MediaTek IOMMU Support"
422	depends on ARCH_MEDIATEK || COMPILE_TEST
423	select ARM_DMA_USE_IOMMU
424	select IOMMU_API
425	select IOMMU_IO_PGTABLE_ARMV7S
426	select MEMORY
427	select MTK_SMI
428	help
429	  Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
430	  Memory Management Unit. This option enables remapping of DMA memory
431	  accesses for the multimedia subsystem.
432
433	  If unsure, say N here.
434
435config MTK_IOMMU_V1
436	tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
437	depends on ARM
438	depends on ARCH_MEDIATEK || COMPILE_TEST
439	select ARM_DMA_USE_IOMMU
440	select IOMMU_API
441	select MEMORY
442	select MTK_SMI
443	help
444	  Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
445	  Multimedia Memory Managememt Unit. This option enables remapping of
446	  DMA memory accesses for the multimedia subsystem.
447
448	  if unsure, say N here.
449
450config QCOM_IOMMU
451	# Note: iommu drivers cannot (yet?) be built as modules
452	bool "Qualcomm IOMMU Support"
453	depends on ARCH_QCOM || COMPILE_TEST
454	depends on !GENERIC_ATOMIC64	# for IOMMU_IO_PGTABLE_LPAE
455	select QCOM_SCM
456	select IOMMU_API
457	select IOMMU_IO_PGTABLE_LPAE
458	select ARM_DMA_USE_IOMMU
459	help
460	  Support for IOMMU on certain Qualcomm SoCs.
461
462config HYPERV_IOMMU
463	bool "Hyper-V IRQ Handling"
464	depends on HYPERV && X86
465	select IOMMU_API
466	default HYPERV
467	help
468	  Stub IOMMU driver to handle IRQs to support Hyper-V Linux
469	  guest and root partitions.
470
471config VIRTIO_IOMMU
472	tristate "Virtio IOMMU driver"
473	depends on VIRTIO
474	depends on (ARM64 || X86)
475	select IOMMU_API
476	select INTERVAL_TREE
477	select ACPI_VIOT if ACPI
478	help
479	  Para-virtualised IOMMU driver with virtio.
480
481	  Say Y here if you intend to run this kernel as a guest.
482
483config SPRD_IOMMU
484	tristate "Unisoc IOMMU Support"
485	depends on ARCH_SPRD || COMPILE_TEST
486	select IOMMU_API
487	help
488	  Support for IOMMU on Unisoc's SoCs, this IOMMU can be used by
489	  Unisoc's multimedia devices, such as display, Image codec(jpeg)
490	  and a few signal processors, including VSP(video), GSP(graphic),
491	  ISP(image), and CPP(camera pixel processor), etc.
492
493	  Say Y here if you want to use the multimedia devices listed above.
494
495endif # IOMMU_SUPPORT
496