1 # IOMMU_API always gets selected by whoever wants it.
5 menuconfig IOMMU_SUPPORT
6 bool "IOMMU Hardware Support"
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
22 bool "MSM IOMMU Support"
23 depends on ARCH_MSM8X60 || ARCH_MSM8960
26 Support for the IOMMUs found on certain Qualcomm SOCs.
27 These IOMMUs allow virtualization of the address space used by most
28 cores within the multimedia subsystem.
30 If unsure, say N here.
32 config IOMMU_PGTABLES_L2
34 depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
38 bool "AMD IOMMU support"
45 depends on X86_64 && PCI && ACPI && X86_IO_APIC
47 With this option you can enable support for AMD IOMMU hardware in
48 your system. An IOMMU is a hardware component which provides
49 remapping of DMA memory accesses from devices. With an AMD IOMMU you
50 can isolate the DMA memory of different devices and protect the
51 system from misbehaving device drivers or hardware.
53 You can find out if your system has an AMD IOMMU if you look into
54 your BIOS for an option to enable it or if you have an IVRS ACPI
57 config AMD_IOMMU_STATS
58 bool "Export AMD IOMMU statistics to debugfs"
62 This option enables code in the AMD IOMMU driver to collect various
63 statistics about whats happening in the driver and exports that
64 information to userspace via debugfs.
68 tristate "AMD IOMMU Version 2 driver"
69 depends on AMD_IOMMU && PROFILING
72 This option enables support for the AMD IOMMUv2 features of the IOMMU
73 hardware. Select this option if you want to use devices that support
74 the PCI PRI and PASID interface.
81 bool "Support for Intel IOMMU using DMA Remapping Devices"
82 depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC)
86 DMA remapping (DMAR) devices support enables independent address
87 translations for Direct Memory Access (DMA) from devices.
88 These DMA remapping devices are reported via ACPI tables
89 and include PCI device scope covered by these DMA
92 config INTEL_IOMMU_DEFAULT_ON
94 prompt "Enable Intel DMA Remapping Devices by default"
95 depends on INTEL_IOMMU
97 Selecting this option will enable a DMAR device at boot time if
98 one is found. If this option is not selected, DMAR support can
99 be enabled by passing intel_iommu=on to the kernel.
101 config INTEL_IOMMU_BROKEN_GFX_WA
102 bool "Workaround broken graphics drivers (going away soon)"
103 depends on INTEL_IOMMU && BROKEN && X86
105 Current Graphics drivers tend to use physical address
106 for DMA and avoid using DMA APIs. Setting this config
107 option permits the IOMMU driver to set a unity map for
108 all the OS-visible memory. Hence the driver can continue
109 to use physical addresses for DMA, at least until this
110 option is removed in the 2.6.32 kernel.
112 config INTEL_IOMMU_FLOPPY_WA
114 depends on INTEL_IOMMU && X86
116 Floppy disk drivers are known to bypass DMA API calls
117 thereby failing to work when IOMMU is enabled. This
118 workaround will setup a 1:1 mapping for the first
119 16MiB to make floppy (an ISA device) work.
122 bool "Support for Interrupt Remapping"
123 depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
126 Supports Interrupt remapping for IO-APIC and MSI devices.
127 To use x2apic mode in the CPU's which support x2APIC enhancements or
128 to support platforms with CPU's having > 8 bit APIC ID, say Y.
130 config ROCKCHIP_IOMMU
131 bool "Rockchip IOMMU Support"
132 depends on ARCH_ROCKCHIP
135 Support for the IOMMU(System MMU) of Rockchip rk32xx application
136 processor family. This enables H/W multimedia accellerators to see
137 non-linear physical memory chunks as a linear memory in their
140 If unsure, say N here.
142 config ROCKCHIP_IOVMM
143 bool "IO Virtual Memory Manager for Rockcihp IOMMUs"
144 select GENERIC_ALLOCATOR
145 depends on ROCKCHIP_IOMMU
148 Supporting the users of Rockchip IOMMU for allocating and mapping
149 an IO virtual memory region with a physical memory region
150 and managing the allocated virtual memory regions.
152 config ROCKCHIP_IOMMU_DEBUG
153 bool "Debugging log for Rockchip IOMMU"
154 depends on ROCKCHIP_IOMMU
156 Select this to see the detailed log message that shows what
157 happens in the IOMMU driver
159 Say N unless you need kernel log message for IOMMU debugging
163 bool "OMAP IOMMU Support"
164 depends on ARCH_OMAP2PLUS
168 tristate "OMAP IO Virtual Memory Manager Support"
169 depends on OMAP_IOMMU
171 config OMAP_IOMMU_DEBUG
172 tristate "Export OMAP IOMMU/IOVMM internals in DebugFS"
173 depends on OMAP_IOVMM && DEBUG_FS
175 Select this to see extensive information about
176 the internal state of OMAP IOMMU/IOVMM in debugfs.
178 Say N unless you know you need this.
180 config TEGRA_IOMMU_GART
181 bool "Tegra GART IOMMU Support"
182 depends on ARCH_TEGRA_2x_SOC
185 Enables support for remapping discontiguous physical memory
186 shared with the operating system into contiguous I/O virtual
187 space through the GART (Graphics Address Relocation Table)
188 hardware included on Tegra SoCs.
190 config TEGRA_IOMMU_SMMU
191 bool "Tegra SMMU IOMMU Support"
192 depends on ARCH_TEGRA && TEGRA_AHB
195 Enables support for remapping discontiguous physical memory
196 shared with the operating system into contiguous I/O virtual
197 space through the SMMU (System Memory Management Unit)
198 hardware included on Tegra SoCs.
201 bool "Exynos IOMMU Support"
202 depends on ARCH_EXYNOS && EXYNOS_DEV_SYSMMU
205 Support for the IOMMU(System MMU) of Samsung Exynos application
206 processor family. This enables H/W multimedia accellerators to see
207 non-linear physical memory chunks as a linear memory in their
210 If unsure, say N here.
212 config EXYNOS_IOMMU_DEBUG
213 bool "Debugging log for Exynos IOMMU"
214 depends on EXYNOS_IOMMU
216 Select this to see the detailed log message that shows what
217 happens in the IOMMU driver
219 Say N unless you need kernel log message for IOMMU debugging
221 config SHMOBILE_IPMMU
224 config SHMOBILE_IPMMU_TLB
227 config SHMOBILE_IOMMU
228 bool "IOMMU for Renesas IPMMU/IPMMUI"
230 depends on (ARM && ARCH_SHMOBILE)
232 select ARM_DMA_USE_IOMMU
233 select SHMOBILE_IPMMU
234 select SHMOBILE_IPMMU_TLB
236 Support for Renesas IPMMU/IPMMUI. This option enables
237 remapping of DMA memory accesses from all of the IP blocks
240 Warning: Drivers (including userspace drivers of UIO
241 devices) of the IP blocks on the ICB *must* use addresses
242 allocated from the IPMMU (iova) for DMA with this option
248 prompt "IPMMU/IPMMUI address space size"
249 default SHMOBILE_IOMMU_ADDRSIZE_2048MB
250 depends on SHMOBILE_IOMMU
252 This option sets IPMMU/IPMMUI address space size by
253 adjusting the 1st level page table size. The page table size
254 is calculated as follows:
256 page table size = number of page table entries * 4 bytes
257 number of page table entries = address space size / 1 MiB
259 For example, when the address space size is 2048 MiB, the
260 1st level page table size is 8192 bytes.
262 config SHMOBILE_IOMMU_ADDRSIZE_2048MB
265 config SHMOBILE_IOMMU_ADDRSIZE_1024MB
268 config SHMOBILE_IOMMU_ADDRSIZE_512MB
271 config SHMOBILE_IOMMU_ADDRSIZE_256MB
274 config SHMOBILE_IOMMU_ADDRSIZE_128MB
277 config SHMOBILE_IOMMU_ADDRSIZE_64MB
280 config SHMOBILE_IOMMU_ADDRSIZE_32MB
285 config SHMOBILE_IOMMU_L1SIZE
287 default 8192 if SHMOBILE_IOMMU_ADDRSIZE_2048MB
288 default 4096 if SHMOBILE_IOMMU_ADDRSIZE_1024MB
289 default 2048 if SHMOBILE_IOMMU_ADDRSIZE_512MB
290 default 1024 if SHMOBILE_IOMMU_ADDRSIZE_256MB
291 default 512 if SHMOBILE_IOMMU_ADDRSIZE_128MB
292 default 256 if SHMOBILE_IOMMU_ADDRSIZE_64MB
293 default 128 if SHMOBILE_IOMMU_ADDRSIZE_32MB
295 endif # IOMMU_SUPPORT