xref: /openbmc/linux/drivers/iommu/Kconfig (revision 26ba4e57) 
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 && !GENERIC_ATOMIC64)
32	help
33	  Enable support for the ARM long descriptor pagetable format.
34	  This allocator supports 4K/2M/1G, 16K/32M and 64K/512M page
35	  sizes at both stage-1 and stage-2, as well as address spaces
36	  up to 48-bits in size.
37
38config IOMMU_IO_PGTABLE_LPAE_SELFTEST
39	bool "LPAE selftests"
40	depends on IOMMU_IO_PGTABLE_LPAE
41	help
42	  Enable self-tests for LPAE page table allocator. This performs
43	  a series of page-table consistency checks during boot.
44
45	  If unsure, say N here.
46
47config IOMMU_IO_PGTABLE_ARMV7S
48	bool "ARMv7/v8 Short Descriptor Format"
49	select IOMMU_IO_PGTABLE
50	depends on ARM || ARM64 || COMPILE_TEST
51	help
52	  Enable support for the ARM Short-descriptor pagetable format.
53	  This supports 32-bit virtual and physical addresses mapped using
54	  2-level tables with 4KB pages/1MB sections, and contiguous entries
55	  for 64KB pages/16MB supersections if indicated by the IOMMU driver.
56
57config IOMMU_IO_PGTABLE_ARMV7S_SELFTEST
58	bool "ARMv7s selftests"
59	depends on IOMMU_IO_PGTABLE_ARMV7S
60	help
61	  Enable self-tests for ARMv7s page table allocator. This performs
62	  a series of page-table consistency checks during boot.
63
64	  If unsure, say N here.
65
66endmenu
67
68config IOMMU_DEBUGFS
69	bool "Export IOMMU internals in DebugFS"
70	depends on DEBUG_FS
71	help
72	  Allows exposure of IOMMU device internals. This option enables
73	  the use of debugfs by IOMMU drivers as required. Devices can,
74	  at initialization time, cause the IOMMU code to create a top-level
75	  debug/iommu directory, and then populate a subdirectory with
76	  entries as required.
77
78config IOMMU_DEFAULT_PASSTHROUGH
79	bool "IOMMU passthrough by default"
80	depends on IOMMU_API
81        help
82	  Enable passthrough by default, removing the need to pass in
83	  iommu.passthrough=on or iommu=pt through command line. If this
84	  is enabled, you can still disable with iommu.passthrough=off
85	  or iommu=nopt depending on the architecture.
86
87	  If unsure, say N here.
88
89config OF_IOMMU
90       def_bool y
91       depends on OF && IOMMU_API
92
93# IOMMU-agnostic DMA-mapping layer
94config IOMMU_DMA
95	bool
96	select IOMMU_API
97	select IOMMU_IOVA
98	select IRQ_MSI_IOMMU
99	select NEED_SG_DMA_LENGTH
100
101config FSL_PAMU
102	bool "Freescale IOMMU support"
103	depends on PCI
104	depends on PHYS_64BIT
105	depends on PPC_E500MC || (COMPILE_TEST && PPC)
106	select IOMMU_API
107	select GENERIC_ALLOCATOR
108	help
109	  Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
110	  PAMU can authorize memory access, remap the memory address, and remap I/O
111	  transaction types.
112
113# MSM IOMMU support
114config MSM_IOMMU
115	bool "MSM IOMMU Support"
116	depends on ARM
117	depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
118	select IOMMU_API
119	select IOMMU_IO_PGTABLE_ARMV7S
120	help
121	  Support for the IOMMUs found on certain Qualcomm SOCs.
122	  These IOMMUs allow virtualization of the address space used by most
123	  cores within the multimedia subsystem.
124
125	  If unsure, say N here.
126
127config IOMMU_PGTABLES_L2
128	def_bool y
129	depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
130
131# AMD IOMMU support
132config AMD_IOMMU
133	bool "AMD IOMMU support"
134	select SWIOTLB
135	select PCI_MSI
136	select PCI_ATS
137	select PCI_PRI
138	select PCI_PASID
139	select IOMMU_API
140	select IOMMU_IOVA
141	depends on X86_64 && PCI && ACPI
142	---help---
143	  With this option you can enable support for AMD IOMMU hardware in
144	  your system. An IOMMU is a hardware component which provides
145	  remapping of DMA memory accesses from devices. With an AMD IOMMU you
146	  can isolate the DMA memory of different devices and protect the
147	  system from misbehaving device drivers or hardware.
148
149	  You can find out if your system has an AMD IOMMU if you look into
150	  your BIOS for an option to enable it or if you have an IVRS ACPI
151	  table.
152
153config AMD_IOMMU_V2
154	tristate "AMD IOMMU Version 2 driver"
155	depends on AMD_IOMMU
156	select MMU_NOTIFIER
157	---help---
158	  This option enables support for the AMD IOMMUv2 features of the IOMMU
159	  hardware. Select this option if you want to use devices that support
160	  the PCI PRI and PASID interface.
161
162config AMD_IOMMU_DEBUGFS
163	bool "Enable AMD IOMMU internals in DebugFS"
164	depends on AMD_IOMMU && IOMMU_DEBUGFS
165	---help---
166	  !!!WARNING!!!  !!!WARNING!!!  !!!WARNING!!!  !!!WARNING!!!
167
168	  DO NOT ENABLE THIS OPTION UNLESS YOU REALLY, -REALLY- KNOW WHAT YOU ARE DOING!!!
169	  Exposes AMD IOMMU device internals in DebugFS.
170
171	  This option is -NOT- intended for production environments, and should
172	  not generally be enabled.
173
174# Intel IOMMU support
175config DMAR_TABLE
176	bool
177
178config INTEL_IOMMU
179	bool "Support for Intel IOMMU using DMA Remapping Devices"
180	depends on PCI_MSI && ACPI && (X86 || IA64)
181	select IOMMU_API
182	select IOMMU_IOVA
183	select NEED_DMA_MAP_STATE
184	select DMAR_TABLE
185	select SWIOTLB
186	help
187	  DMA remapping (DMAR) devices support enables independent address
188	  translations for Direct Memory Access (DMA) from devices.
189	  These DMA remapping devices are reported via ACPI tables
190	  and include PCI device scope covered by these DMA
191	  remapping devices.
192
193config INTEL_IOMMU_DEBUGFS
194	bool "Export Intel IOMMU internals in Debugfs"
195	depends on INTEL_IOMMU && IOMMU_DEBUGFS
196	help
197	  !!!WARNING!!!
198
199	  DO NOT ENABLE THIS OPTION UNLESS YOU REALLY KNOW WHAT YOU ARE DOING!!!
200
201	  Expose Intel IOMMU internals in Debugfs.
202
203	  This option is -NOT- intended for production environments, and should
204	  only be enabled for debugging Intel IOMMU.
205
206config INTEL_IOMMU_SVM
207	bool "Support for Shared Virtual Memory with Intel IOMMU"
208	depends on INTEL_IOMMU && X86
209	select PCI_PASID
210	select MMU_NOTIFIER
211	help
212	  Shared Virtual Memory (SVM) provides a facility for devices
213	  to access DMA resources through process address space by
214	  means of a Process Address Space ID (PASID).
215
216config INTEL_IOMMU_DEFAULT_ON
217	def_bool y
218	prompt "Enable Intel DMA Remapping Devices by default"
219	depends on INTEL_IOMMU
220	help
221	  Selecting this option will enable a DMAR device at boot time if
222	  one is found. If this option is not selected, DMAR support can
223	  be enabled by passing intel_iommu=on to the kernel.
224
225config INTEL_IOMMU_BROKEN_GFX_WA
226	bool "Workaround broken graphics drivers (going away soon)"
227	depends on INTEL_IOMMU && BROKEN && X86
228	---help---
229	  Current Graphics drivers tend to use physical address
230	  for DMA and avoid using DMA APIs. Setting this config
231	  option permits the IOMMU driver to set a unity map for
232	  all the OS-visible memory. Hence the driver can continue
233	  to use physical addresses for DMA, at least until this
234	  option is removed in the 2.6.32 kernel.
235
236config INTEL_IOMMU_FLOPPY_WA
237	def_bool y
238	depends on INTEL_IOMMU && X86
239	---help---
240	  Floppy disk drivers are known to bypass DMA API calls
241	  thereby failing to work when IOMMU is enabled. This
242	  workaround will setup a 1:1 mapping for the first
243	  16MiB to make floppy (an ISA device) work.
244
245config IRQ_REMAP
246	bool "Support for Interrupt Remapping"
247	depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
248	select DMAR_TABLE
249	---help---
250	  Supports Interrupt remapping for IO-APIC and MSI devices.
251	  To use x2apic mode in the CPU's which support x2APIC enhancements or
252	  to support platforms with CPU's having > 8 bit APIC ID, say Y.
253
254# OMAP IOMMU support
255config OMAP_IOMMU
256	bool "OMAP IOMMU Support"
257	depends on ARM && MMU
258	depends on ARCH_OMAP2PLUS || COMPILE_TEST
259	select IOMMU_API
260	---help---
261	  The OMAP3 media platform drivers depend on iommu support,
262	  if you need them say Y here.
263
264config OMAP_IOMMU_DEBUG
265	bool "Export OMAP IOMMU internals in DebugFS"
266	depends on OMAP_IOMMU && DEBUG_FS
267	---help---
268	  Select this to see extensive information about
269	  the internal state of OMAP IOMMU in debugfs.
270
271	  Say N unless you know you need this.
272
273config ROCKCHIP_IOMMU
274	bool "Rockchip IOMMU Support"
275	depends on ARM || ARM64
276	depends on ARCH_ROCKCHIP || COMPILE_TEST
277	select IOMMU_API
278	select ARM_DMA_USE_IOMMU
279	help
280	  Support for IOMMUs found on Rockchip rk32xx SOCs.
281	  These IOMMUs allow virtualization of the address space used by most
282	  cores within the multimedia subsystem.
283	  Say Y here if you are using a Rockchip SoC that includes an IOMMU
284	  device.
285
286config TEGRA_IOMMU_GART
287	bool "Tegra GART IOMMU Support"
288	depends on ARCH_TEGRA_2x_SOC
289	depends on TEGRA_MC
290	select IOMMU_API
291	help
292	  Enables support for remapping discontiguous physical memory
293	  shared with the operating system into contiguous I/O virtual
294	  space through the GART (Graphics Address Relocation Table)
295	  hardware included on Tegra SoCs.
296
297config TEGRA_IOMMU_SMMU
298	bool "NVIDIA Tegra SMMU Support"
299	depends on ARCH_TEGRA
300	depends on TEGRA_AHB
301	depends on TEGRA_MC
302	select IOMMU_API
303	help
304	  This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
305	  SoCs (Tegra30 up to Tegra210).
306
307config EXYNOS_IOMMU
308	bool "Exynos IOMMU Support"
309	depends on ARCH_EXYNOS && MMU
310	depends on !CPU_BIG_ENDIAN # revisit driver if we can enable big-endian ptes
311	select IOMMU_API
312	select ARM_DMA_USE_IOMMU
313	help
314	  Support for the IOMMU (System MMU) of Samsung Exynos application
315	  processor family. This enables H/W multimedia accelerators to see
316	  non-linear physical memory chunks as linear memory in their
317	  address space.
318
319	  If unsure, say N here.
320
321config EXYNOS_IOMMU_DEBUG
322	bool "Debugging log for Exynos IOMMU"
323	depends on EXYNOS_IOMMU
324	help
325	  Select this to see the detailed log message that shows what
326	  happens in the IOMMU driver.
327
328	  Say N unless you need kernel log message for IOMMU debugging.
329
330config IPMMU_VMSA
331	bool "Renesas VMSA-compatible IPMMU"
332	depends on ARM || IOMMU_DMA
333	depends on ARCH_RENESAS || (COMPILE_TEST && !GENERIC_ATOMIC64)
334	select IOMMU_API
335	select IOMMU_IO_PGTABLE_LPAE
336	select ARM_DMA_USE_IOMMU
337	help
338	  Support for the Renesas VMSA-compatible IPMMU found in the R-Mobile
339	  APE6, R-Car Gen2, and R-Car Gen3 SoCs.
340
341	  If unsure, say N.
342
343config SPAPR_TCE_IOMMU
344	bool "sPAPR TCE IOMMU Support"
345	depends on PPC_POWERNV || PPC_PSERIES
346	select IOMMU_API
347	help
348	  Enables bits of IOMMU API required by VFIO. The iommu_ops
349	  is not implemented as it is not necessary for VFIO.
350
351# ARM IOMMU support
352config ARM_SMMU
353	bool "ARM Ltd. System MMU (SMMU) Support"
354	depends on (ARM64 || ARM) && MMU
355	select IOMMU_API
356	select IOMMU_IO_PGTABLE_LPAE
357	select ARM_DMA_USE_IOMMU if ARM
358	help
359	  Support for implementations of the ARM System MMU architecture
360	  versions 1 and 2.
361
362	  Say Y here if your SoC includes an IOMMU device implementing
363	  the ARM SMMU architecture.
364
365config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
366	bool "Default to disabling bypass on ARM SMMU v1 and v2"
367	depends on ARM_SMMU
368	default y
369	help
370	  Say Y here to (by default) disable bypass streams such that
371	  incoming transactions from devices that are not attached to
372	  an iommu domain will report an abort back to the device and
373	  will not be allowed to pass through the SMMU.
374
375	  Any old kernels that existed before this KConfig was
376	  introduced would default to _allowing_ bypass (AKA the
377	  equivalent of NO for this config).  However the default for
378	  this option is YES because the old behavior is insecure.
379
380	  There are few reasons to allow unmatched stream bypass, and
381	  even fewer good ones.  If saying YES here breaks your board
382	  you should work on fixing your board.  This KConfig option
383	  is expected to be removed in the future and we'll simply
384	  hardcode the bypass disable in the code.
385
386	  NOTE: the kernel command line parameter
387	  'arm-smmu.disable_bypass' will continue to override this
388	  config.
389
390config ARM_SMMU_V3
391	bool "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_DOMAIN
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 S390_IOMMU
404	def_bool y if S390 && PCI
405	depends on S390 && PCI
406	select IOMMU_API
407	help
408	  Support for the IOMMU API for s390 PCI devices.
409
410config S390_CCW_IOMMU
411	bool "S390 CCW IOMMU Support"
412	depends on S390 && CCW
413	select IOMMU_API
414	help
415	  Enables bits of IOMMU API required by VFIO. The iommu_ops
416	  is not implemented as it is not necessary for VFIO.
417
418config S390_AP_IOMMU
419	bool "S390 AP IOMMU Support"
420	depends on S390 && ZCRYPT
421	select IOMMU_API
422	help
423	  Enables bits of IOMMU API required by VFIO. The iommu_ops
424	  is not implemented as it is not necessary for VFIO.
425
426config MTK_IOMMU
427	bool "MTK IOMMU Support"
428	depends on ARM || ARM64
429	depends on ARCH_MEDIATEK || COMPILE_TEST
430	select ARM_DMA_USE_IOMMU
431	select IOMMU_API
432	select IOMMU_DMA
433	select IOMMU_IO_PGTABLE_ARMV7S
434	select MEMORY
435	select MTK_SMI
436	help
437	  Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
438	  Memory Management Unit. This option enables remapping of DMA memory
439	  accesses for the multimedia subsystem.
440
441	  If unsure, say N here.
442
443config MTK_IOMMU_V1
444	bool "MTK IOMMU Version 1 (M4U gen1) Support"
445	depends on ARM
446	depends on ARCH_MEDIATEK || COMPILE_TEST
447	select ARM_DMA_USE_IOMMU
448	select IOMMU_API
449	select MEMORY
450	select MTK_SMI
451	help
452	  Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
453	  Multimedia Memory Managememt Unit. This option enables remapping of
454	  DMA memory accesses for the multimedia subsystem.
455
456	  if unsure, say N here.
457
458config QCOM_IOMMU
459	# Note: iommu drivers cannot (yet?) be built as modules
460	bool "Qualcomm IOMMU Support"
461	depends on ARCH_QCOM || (COMPILE_TEST && !GENERIC_ATOMIC64)
462	select IOMMU_API
463	select IOMMU_IO_PGTABLE_LPAE
464	select ARM_DMA_USE_IOMMU
465	help
466	  Support for IOMMU on certain Qualcomm SoCs.
467
468config HYPERV_IOMMU
469	bool "Hyper-V x2APIC IRQ Handling"
470	depends on HYPERV
471	select IOMMU_API
472	default HYPERV
473	help
474	  Stub IOMMU driver to handle IRQs as to allow Hyper-V Linux
475	  guests to run with x2APIC mode enabled.
476
477config VIRTIO_IOMMU
478	bool "Virtio IOMMU driver"
479	depends on VIRTIO=y
480	depends on ARM64
481	select IOMMU_API
482	select INTERVAL_TREE
483	help
484	  Para-virtualised IOMMU driver with virtio.
485
486	  Say Y here if you intend to run this kernel as a guest.
487
488endif # IOMMU_SUPPORT
489