Kconfig 9.9 KB
Newer Older
1 2 3
# IOMMU_API always gets selected by whoever wants it.
config IOMMU_API
	bool
4

5 6
menuconfig IOMMU_SUPPORT
	bool "IOMMU Hardware Support"
A
Arnd Bergmann 已提交
7
	depends on MMU
8 9 10 11 12 13 14 15 16
	default y
	---help---
	  Say Y here if you want to compile device drivers for IO Memory
	  Management Units into the kernel. These devices usually allow to
	  remap DMA requests and/or remap interrupts from other devices on the
	  system.

if IOMMU_SUPPORT

17 18 19 20 21 22
menu "Generic IOMMU Pagetable Support"

# Selected by the actual pagetable implementations
config IOMMU_IO_PGTABLE
	bool

23 24 25 26 27 28 29 30 31
config IOMMU_IO_PGTABLE_LPAE
	bool "ARMv7/v8 Long Descriptor Format"
	select IOMMU_IO_PGTABLE
	help
	  Enable support for the ARM long descriptor pagetable format.
	  This allocator supports 4K/2M/1G, 16K/32M and 64K/512M page
	  sizes at both stage-1 and stage-2, as well as address spaces
	  up to 48-bits in size.

32 33 34 35 36 37 38 39 40
config IOMMU_IO_PGTABLE_LPAE_SELFTEST
	bool "LPAE selftests"
	depends on IOMMU_IO_PGTABLE_LPAE
	help
	  Enable self-tests for LPAE page table allocator. This performs
	  a series of page-table consistency checks during boot.

	  If unsure, say N here.

41 42
endmenu

43 44 45
config IOMMU_IOVA
	bool

46 47
config OF_IOMMU
       def_bool y
48
       depends on OF && IOMMU_API
49

50 51
config FSL_PAMU
	bool "Freescale IOMMU support"
52 53
	depends on PPC32
	depends on PPC_E500MC || COMPILE_TEST
54 55 56 57 58 59 60
	select IOMMU_API
	select GENERIC_ALLOCATOR
	help
	  Freescale PAMU support. PAMU is the IOMMU present on Freescale QorIQ platforms.
	  PAMU can authorize memory access, remap the memory address, and remap I/O
	  transaction types.

61 62 63
# MSM IOMMU support
config MSM_IOMMU
	bool "MSM IOMMU Support"
64 65
	depends on ARM
	depends on ARCH_MSM8X60 || ARCH_MSM8960 || COMPILE_TEST
66 67 68 69 70 71 72 73 74 75 76
	select IOMMU_API
	help
	  Support for the IOMMUs found on certain Qualcomm SOCs.
	  These IOMMUs allow virtualization of the address space used by most
	  cores within the multimedia subsystem.

	  If unsure, say N here.

config IOMMU_PGTABLES_L2
	def_bool y
	depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n
77 78 79 80 81 82

# AMD IOMMU support
config AMD_IOMMU
	bool "AMD IOMMU support"
	select SWIOTLB
	select PCI_MSI
83 84 85
	select PCI_ATS
	select PCI_PRI
	select PCI_PASID
86
	select IOMMU_API
87
	depends on X86_64 && PCI && ACPI
88 89 90 91
	---help---
	  With this option you can enable support for AMD IOMMU hardware in
	  your system. An IOMMU is a hardware component which provides
	  remapping of DMA memory accesses from devices. With an AMD IOMMU you
M
Masanari Iida 已提交
92
	  can isolate the DMA memory of different devices and protect the
93 94 95 96 97 98 99 100 101 102 103 104 105 106 107
	  system from misbehaving device drivers or hardware.

	  You can find out if your system has an AMD IOMMU if you look into
	  your BIOS for an option to enable it or if you have an IVRS ACPI
	  table.

config AMD_IOMMU_STATS
	bool "Export AMD IOMMU statistics to debugfs"
	depends on AMD_IOMMU
	select DEBUG_FS
	---help---
	  This option enables code in the AMD IOMMU driver to collect various
	  statistics about whats happening in the driver and exports that
	  information to userspace via debugfs.
	  If unsure, say N.
108

109
config AMD_IOMMU_V2
110
	tristate "AMD IOMMU Version 2 driver"
111
	depends on AMD_IOMMU
112
	select MMU_NOTIFIER
113 114 115
	---help---
	  This option enables support for the AMD IOMMUv2 features of the IOMMU
	  hardware. Select this option if you want to use devices that support
M
Masanari Iida 已提交
116
	  the PCI PRI and PASID interface.
117

118
# Intel IOMMU support
119 120 121 122 123
config DMAR_TABLE
	bool

config INTEL_IOMMU
	bool "Support for Intel IOMMU using DMA Remapping Devices"
124 125
	depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC)
	select IOMMU_API
126
	select IOMMU_IOVA
127
	select DMAR_TABLE
128 129 130 131 132 133 134
	help
	  DMA remapping (DMAR) devices support enables independent address
	  translations for Direct Memory Access (DMA) from devices.
	  These DMA remapping devices are reported via ACPI tables
	  and include PCI device scope covered by these DMA
	  remapping devices.

135
config INTEL_IOMMU_DEFAULT_ON
136
	def_bool y
137 138
	prompt "Enable Intel DMA Remapping Devices by default"
	depends on INTEL_IOMMU
139 140 141 142 143
	help
	  Selecting this option will enable a DMAR device at boot time if
	  one is found. If this option is not selected, DMAR support can
	  be enabled by passing intel_iommu=on to the kernel.

144
config INTEL_IOMMU_BROKEN_GFX_WA
145
	bool "Workaround broken graphics drivers (going away soon)"
146
	depends on INTEL_IOMMU && BROKEN && X86
147 148 149 150 151 152 153 154
	---help---
	  Current Graphics drivers tend to use physical address
	  for DMA and avoid using DMA APIs. Setting this config
	  option permits the IOMMU driver to set a unity map for
	  all the OS-visible memory. Hence the driver can continue
	  to use physical addresses for DMA, at least until this
	  option is removed in the 2.6.32 kernel.

155
config INTEL_IOMMU_FLOPPY_WA
156
	def_bool y
157
	depends on INTEL_IOMMU && X86
158 159 160 161 162 163
	---help---
	  Floppy disk drivers are known to bypass DMA API calls
	  thereby failing to work when IOMMU is enabled. This
	  workaround will setup a 1:1 mapping for the first
	  16MiB to make floppy (an ISA device) work.

164
config IRQ_REMAP
165 166
	bool "Support for Interrupt Remapping"
	depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI
167
	select DMAR_TABLE
168 169 170 171
	---help---
	  Supports Interrupt remapping for IO-APIC and MSI devices.
	  To use x2apic mode in the CPU's which support x2APIC enhancements or
	  to support platforms with CPU's having > 8 bit APIC ID, say Y.
172

173 174 175
# OMAP IOMMU support
config OMAP_IOMMU
	bool "OMAP IOMMU Support"
176 177
	depends on ARM && MMU
	depends on ARCH_OMAP2PLUS || COMPILE_TEST
178 179 180
	select IOMMU_API

config OMAP_IOMMU_DEBUG
181 182 183 184 185
	bool "Export OMAP IOMMU internals in DebugFS"
	depends on OMAP_IOMMU && DEBUG_FS
	---help---
	  Select this to see extensive information about
	  the internal state of OMAP IOMMU in debugfs.
186

187
	  Say N unless you know you need this.
188

D
Daniel Kurtz 已提交
189 190
config ROCKCHIP_IOMMU
	bool "Rockchip IOMMU Support"
191 192
	depends on ARM
	depends on ARCH_ROCKCHIP || COMPILE_TEST
D
Daniel Kurtz 已提交
193 194 195 196 197 198 199 200
	select IOMMU_API
	select ARM_DMA_USE_IOMMU
	help
	  Support for IOMMUs found on Rockchip rk32xx SOCs.
	  These IOMMUs allow virtualization of the address space used by most
	  cores within the multimedia subsystem.
	  Say Y here if you are using a Rockchip SoC that includes an IOMMU
	  device.
201

202 203 204 205 206 207 208 209 210 211
config TEGRA_IOMMU_GART
	bool "Tegra GART IOMMU Support"
	depends on ARCH_TEGRA_2x_SOC
	select IOMMU_API
	help
	  Enables support for remapping discontiguous physical memory
	  shared with the operating system into contiguous I/O virtual
	  space through the GART (Graphics Address Relocation Table)
	  hardware included on Tegra SoCs.

212
config TEGRA_IOMMU_SMMU
213 214 215 216
	bool "NVIDIA Tegra SMMU Support"
	depends on ARCH_TEGRA
	depends on TEGRA_AHB
	depends on TEGRA_MC
217 218
	select IOMMU_API
	help
219 220
	  This driver supports the IOMMU hardware (SMMU) found on NVIDIA Tegra
	  SoCs (Tegra30 up to Tegra124).
221

222 223
config EXYNOS_IOMMU
	bool "Exynos IOMMU Support"
A
Arnd Bergmann 已提交
224
	depends on ARCH_EXYNOS && ARM && MMU
225
	select IOMMU_API
226
	select ARM_DMA_USE_IOMMU
227
	help
S
Sachin Kamat 已提交
228 229 230 231
	  Support for the IOMMU (System MMU) of Samsung Exynos application
	  processor family. This enables H/W multimedia accelerators to see
	  non-linear physical memory chunks as linear memory in their
	  address space.
232 233 234 235 236 237 238 239

	  If unsure, say N here.

config EXYNOS_IOMMU_DEBUG
	bool "Debugging log for Exynos IOMMU"
	depends on EXYNOS_IOMMU
	help
	  Select this to see the detailed log message that shows what
S
Sachin Kamat 已提交
240
	  happens in the IOMMU driver.
241

S
Sachin Kamat 已提交
242
	  Say N unless you need kernel log message for IOMMU debugging.
243

244 245 246 247 248 249 250 251 252
config SHMOBILE_IPMMU
	bool

config SHMOBILE_IPMMU_TLB
	bool

config SHMOBILE_IOMMU
	bool "IOMMU for Renesas IPMMU/IPMMUI"
	default n
A
Arnd Bergmann 已提交
253
	depends on ARM && MMU
254
	depends on ARCH_SHMOBILE || COMPILE_TEST
255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318
	select IOMMU_API
	select ARM_DMA_USE_IOMMU
	select SHMOBILE_IPMMU
	select SHMOBILE_IPMMU_TLB
	help
	  Support for Renesas IPMMU/IPMMUI. This option enables
	  remapping of DMA memory accesses from all of the IP blocks
	  on the ICB.

	  Warning: Drivers (including userspace drivers of UIO
	  devices) of the IP blocks on the ICB *must* use addresses
	  allocated from the IPMMU (iova) for DMA with this option
	  enabled.

	  If unsure, say N.

choice
	prompt "IPMMU/IPMMUI address space size"
	default SHMOBILE_IOMMU_ADDRSIZE_2048MB
	depends on SHMOBILE_IOMMU
	help
	  This option sets IPMMU/IPMMUI address space size by
	  adjusting the 1st level page table size. The page table size
	  is calculated as follows:

	      page table size = number of page table entries * 4 bytes
	      number of page table entries = address space size / 1 MiB

	  For example, when the address space size is 2048 MiB, the
	  1st level page table size is 8192 bytes.

	config SHMOBILE_IOMMU_ADDRSIZE_2048MB
		bool "2 GiB"

	config SHMOBILE_IOMMU_ADDRSIZE_1024MB
		bool "1 GiB"

	config SHMOBILE_IOMMU_ADDRSIZE_512MB
		bool "512 MiB"

	config SHMOBILE_IOMMU_ADDRSIZE_256MB
		bool "256 MiB"

	config SHMOBILE_IOMMU_ADDRSIZE_128MB
		bool "128 MiB"

	config SHMOBILE_IOMMU_ADDRSIZE_64MB
		bool "64 MiB"

	config SHMOBILE_IOMMU_ADDRSIZE_32MB
		bool "32 MiB"

endchoice

config SHMOBILE_IOMMU_L1SIZE
	int
	default 8192 if SHMOBILE_IOMMU_ADDRSIZE_2048MB
	default 4096 if SHMOBILE_IOMMU_ADDRSIZE_1024MB
	default 2048 if SHMOBILE_IOMMU_ADDRSIZE_512MB
	default 1024 if SHMOBILE_IOMMU_ADDRSIZE_256MB
	default 512 if SHMOBILE_IOMMU_ADDRSIZE_128MB
	default 256 if SHMOBILE_IOMMU_ADDRSIZE_64MB
	default 128 if SHMOBILE_IOMMU_ADDRSIZE_32MB

319 320 321 322 323
config IPMMU_VMSA
	bool "Renesas VMSA-compatible IPMMU"
	depends on ARM_LPAE
	depends on ARCH_SHMOBILE || COMPILE_TEST
	select IOMMU_API
324
	select IOMMU_IO_PGTABLE_LPAE
325 326 327 328 329 330 331
	select ARM_DMA_USE_IOMMU
	help
	  Support for the Renesas VMSA-compatible IPMMU Renesas found in the
	  R-Mobile APE6 and R-Car H2/M2 SoCs.

	  If unsure, say N.

332 333
config SPAPR_TCE_IOMMU
	bool "sPAPR TCE IOMMU Support"
334
	depends on PPC_POWERNV || PPC_PSERIES
335 336 337 338 339
	select IOMMU_API
	help
	  Enables bits of IOMMU API required by VFIO. The iommu_ops
	  is not implemented as it is not necessary for VFIO.

340 341
config ARM_SMMU
	bool "ARM Ltd. System MMU (SMMU) Support"
342
	depends on (ARM64 || ARM) && MMU
343
	select IOMMU_API
344
	select IOMMU_IO_PGTABLE_LPAE
345 346 347
	select ARM_DMA_USE_IOMMU if ARM
	help
	  Support for implementations of the ARM System MMU architecture
348
	  versions 1 and 2.
349 350 351 352

	  Say Y here if your SoC includes an IOMMU device implementing
	  the ARM SMMU architecture.

353
endif # IOMMU_SUPPORT