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