]>
Commit | Line | Data |
---|---|---|
ab493a0f OBC |
1 | # IOMMU_API always gets selected by whoever wants it. |
2 | config IOMMU_API | |
3 | bool | |
b10f127e | 4 | |
68255b62 JR |
5 | menuconfig IOMMU_SUPPORT |
6 | bool "IOMMU Hardware Support" | |
7 | default y | |
8 | ---help--- | |
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 | |
12 | system. | |
13 | ||
14 | if IOMMU_SUPPORT | |
15 | ||
b10f127e OBC |
16 | # MSM IOMMU support |
17 | config MSM_IOMMU | |
18 | bool "MSM IOMMU Support" | |
19 | depends on ARCH_MSM8X60 || ARCH_MSM8960 | |
20 | select IOMMU_API | |
21 | help | |
22 | Support for the IOMMUs found on certain Qualcomm SOCs. | |
23 | These IOMMUs allow virtualization of the address space used by most | |
24 | cores within the multimedia subsystem. | |
25 | ||
26 | If unsure, say N here. | |
27 | ||
28 | config IOMMU_PGTABLES_L2 | |
29 | def_bool y | |
30 | depends on MSM_IOMMU && MMU && SMP && CPU_DCACHE_DISABLE=n | |
29b68415 OBC |
31 | |
32 | # AMD IOMMU support | |
33 | config AMD_IOMMU | |
34 | bool "AMD IOMMU support" | |
35 | select SWIOTLB | |
36 | select PCI_MSI | |
37 | select PCI_IOV | |
38 | select IOMMU_API | |
39 | depends on X86_64 && PCI && ACPI | |
40 | ---help--- | |
41 | With this option you can enable support for AMD IOMMU hardware in | |
42 | your system. An IOMMU is a hardware component which provides | |
43 | remapping of DMA memory accesses from devices. With an AMD IOMMU you | |
44 | can isolate the the DMA memory of different devices and protect the | |
45 | system from misbehaving device drivers or hardware. | |
46 | ||
47 | You can find out if your system has an AMD IOMMU if you look into | |
48 | your BIOS for an option to enable it or if you have an IVRS ACPI | |
49 | table. | |
50 | ||
51 | config AMD_IOMMU_STATS | |
52 | bool "Export AMD IOMMU statistics to debugfs" | |
53 | depends on AMD_IOMMU | |
54 | select DEBUG_FS | |
55 | ---help--- | |
56 | This option enables code in the AMD IOMMU driver to collect various | |
57 | statistics about whats happening in the driver and exports that | |
58 | information to userspace via debugfs. | |
59 | If unsure, say N. | |
166e9278 OBC |
60 | |
61 | # Intel IOMMU support | |
d3f13810 SS |
62 | config DMAR_TABLE |
63 | bool | |
64 | ||
65 | config INTEL_IOMMU | |
66 | bool "Support for Intel IOMMU using DMA Remapping Devices" | |
166e9278 OBC |
67 | depends on PCI_MSI && ACPI && (X86 || IA64_GENERIC) |
68 | select IOMMU_API | |
d3f13810 | 69 | select DMAR_TABLE |
166e9278 OBC |
70 | help |
71 | DMA remapping (DMAR) devices support enables independent address | |
72 | translations for Direct Memory Access (DMA) from devices. | |
73 | These DMA remapping devices are reported via ACPI tables | |
74 | and include PCI device scope covered by these DMA | |
75 | remapping devices. | |
76 | ||
d3f13810 | 77 | config INTEL_IOMMU_DEFAULT_ON |
166e9278 | 78 | def_bool y |
d3f13810 SS |
79 | prompt "Enable Intel DMA Remapping Devices by default" |
80 | depends on INTEL_IOMMU | |
166e9278 OBC |
81 | help |
82 | Selecting this option will enable a DMAR device at boot time if | |
83 | one is found. If this option is not selected, DMAR support can | |
84 | be enabled by passing intel_iommu=on to the kernel. | |
85 | ||
d3f13810 | 86 | config INTEL_IOMMU_BROKEN_GFX_WA |
166e9278 | 87 | bool "Workaround broken graphics drivers (going away soon)" |
d3f13810 | 88 | depends on INTEL_IOMMU && BROKEN && X86 |
166e9278 OBC |
89 | ---help--- |
90 | Current Graphics drivers tend to use physical address | |
91 | for DMA and avoid using DMA APIs. Setting this config | |
92 | option permits the IOMMU driver to set a unity map for | |
93 | all the OS-visible memory. Hence the driver can continue | |
94 | to use physical addresses for DMA, at least until this | |
95 | option is removed in the 2.6.32 kernel. | |
96 | ||
d3f13810 | 97 | config INTEL_IOMMU_FLOPPY_WA |
166e9278 | 98 | def_bool y |
d3f13810 | 99 | depends on INTEL_IOMMU && X86 |
166e9278 OBC |
100 | ---help--- |
101 | Floppy disk drivers are known to bypass DMA API calls | |
102 | thereby failing to work when IOMMU is enabled. This | |
103 | workaround will setup a 1:1 mapping for the first | |
104 | 16MiB to make floppy (an ISA device) work. | |
105 | ||
d3f13810 | 106 | config IRQ_REMAP |
166e9278 OBC |
107 | bool "Support for Interrupt Remapping (EXPERIMENTAL)" |
108 | depends on X86_64 && X86_IO_APIC && PCI_MSI && ACPI && EXPERIMENTAL | |
d3f13810 | 109 | select DMAR_TABLE |
166e9278 OBC |
110 | ---help--- |
111 | Supports Interrupt remapping for IO-APIC and MSI devices. | |
112 | To use x2apic mode in the CPU's which support x2APIC enhancements or | |
113 | to support platforms with CPU's having > 8 bit APIC ID, say Y. | |
68255b62 | 114 | |
fcf3a6ef OBC |
115 | # OMAP IOMMU support |
116 | config OMAP_IOMMU | |
117 | bool "OMAP IOMMU Support" | |
024ae884 | 118 | depends on ARCH_OMAP |
fcf3a6ef OBC |
119 | select IOMMU_API |
120 | ||
121 | config OMAP_IOVMM | |
7b6d45f1 JR |
122 | tristate "OMAP IO Virtual Memory Manager Support" |
123 | depends on OMAP_IOMMU | |
fcf3a6ef OBC |
124 | |
125 | config OMAP_IOMMU_DEBUG | |
126 | tristate "Export OMAP IOMMU/IOVMM internals in DebugFS" | |
127 | depends on OMAP_IOVMM && DEBUG_FS | |
128 | help | |
129 | Select this to see extensive information about | |
130 | the internal state of OMAP IOMMU/IOVMM in debugfs. | |
131 | ||
132 | Say N unless you know you need this. | |
133 | ||
68255b62 | 134 | endif # IOMMU_SUPPORT |