2 # Drm device configuration
4 # This driver provides support for the
5 # Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.
8 tristate "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)"
9 depends on (AGP || AGP=n) && !EMULATED_CMPXCHG && MMU && HAS_DMA
14 select DMA_SHARED_BUFFER
16 Kernel-level support for the Direct Rendering Infrastructure (DRI)
17 introduced in XFree86 4.0. If you say Y here, you need to select
18 the module that's right for your graphics card from the list below.
19 These modules provide support for synchronization, security, and
20 DMA transfers. Please see <http://dri.sourceforge.net/> for more
21 details. You should also select and configure AGP
22 (/dev/agpgart) support if it is available for your platform.
28 config DRM_DP_AUX_CHARDEV
29 bool "DRM DP AUX Interface"
32 Choose this option to enable a /dev/drm_dp_auxN node that allows to
33 read and write values to arbitrary DPCD registers on the DP aux
40 CRTC helpers for KMS drivers.
42 config DRM_KMS_FB_HELPER
44 depends on DRM_KMS_HELPER
46 select FRAMEBUFFER_CONSOLE if !EXPERT
47 select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
49 select FB_SYS_FILLRECT
50 select FB_SYS_COPYAREA
51 select FB_SYS_IMAGEBLIT
52 select FB_CFB_FILLRECT
53 select FB_CFB_COPYAREA
54 select FB_CFB_IMAGEBLIT
57 FBDEV helpers for KMS drivers.
59 config DRM_FBDEV_EMULATION
60 bool "Enable legacy fbdev support for your modesetting driver"
63 select DRM_KMS_FB_HELPER
66 Choose this option if you have a need for the legacy fbdev
67 support. Note that this support also provides the linux console
68 support on top of your modesetting driver.
72 config DRM_LOAD_EDID_FIRMWARE
73 bool "Allow to specify an EDID data set instead of probing for it"
74 depends on DRM_KMS_HELPER
76 Say Y here, if you want to use EDID data to be loaded from the
77 /lib/firmware directory or one of the provided built-in
78 data sets. This may be necessary, if the graphics adapter or
79 monitor are unable to provide appropriate EDID data. Since this
80 feature is provided as a workaround for broken hardware, the
81 default case is N. Details and instructions how to build your own
82 EDID data are given in Documentation/EDID/HOWTO.txt.
88 GPU memory management subsystem for devices with multiple
89 GPU memory types. Will be enabled automatically if a device driver
92 config DRM_GEM_CMA_HELPER
96 Choose this if you need the GEM CMA helper functions
98 config DRM_KMS_CMA_HELPER
101 select DRM_GEM_CMA_HELPER
102 select DRM_KMS_FB_HELPER
103 select FB_SYS_FILLRECT
104 select FB_SYS_COPYAREA
105 select FB_SYS_IMAGEBLIT
107 Choose this if you need the KMS CMA helper functions
109 source "drivers/gpu/drm/i2c/Kconfig"
111 source "drivers/gpu/drm/arm/Kconfig"
114 tristate "ATI Radeon"
115 depends on DRM && PCI
117 select DRM_KMS_HELPER
121 select BACKLIGHT_CLASS_DEVICE
122 select BACKLIGHT_LCD_SUPPORT
125 Choose this option if you have an ATI Radeon graphics card. There
126 are both PCI and AGP versions. You don't need to choose this to
127 run the Radeon in plain VGA mode.
129 If M is selected, the module will be called radeon.
131 source "drivers/gpu/drm/radeon/Kconfig"
135 depends on DRM && PCI
137 select DRM_KMS_HELPER
141 select BACKLIGHT_CLASS_DEVICE
142 select BACKLIGHT_LCD_SUPPORT
145 Choose this option if you have a recent AMD Radeon graphics card.
147 If M is selected, the module will be called amdgpu.
149 source "drivers/gpu/drm/amd/amdgpu/Kconfig"
150 source "drivers/gpu/drm/amd/powerplay/Kconfig"
152 source "drivers/gpu/drm/amd/acp/Kconfig"
154 source "drivers/gpu/drm/nouveau/Kconfig"
156 source "drivers/gpu/drm/i915/Kconfig"
159 tristate "Virtual GEM provider"
162 Choose this option to get a virtual graphics memory manager,
163 as used by Mesa's software renderer for enhanced performance.
164 If M is selected the module will be called vgem.
167 source "drivers/gpu/drm/exynos/Kconfig"
169 source "drivers/gpu/drm/rockchip/Kconfig"
171 source "drivers/gpu/drm/vmwgfx/Kconfig"
173 source "drivers/gpu/drm/gma500/Kconfig"
175 source "drivers/gpu/drm/udl/Kconfig"
177 source "drivers/gpu/drm/ast/Kconfig"
179 source "drivers/gpu/drm/mgag200/Kconfig"
181 source "drivers/gpu/drm/cirrus/Kconfig"
183 source "drivers/gpu/drm/armada/Kconfig"
185 source "drivers/gpu/drm/atmel-hlcdc/Kconfig"
187 source "drivers/gpu/drm/rcar-du/Kconfig"
189 source "drivers/gpu/drm/shmobile/Kconfig"
191 source "drivers/gpu/drm/sun4i/Kconfig"
193 source "drivers/gpu/drm/omapdrm/Kconfig"
195 source "drivers/gpu/drm/tilcdc/Kconfig"
197 source "drivers/gpu/drm/qxl/Kconfig"
199 source "drivers/gpu/drm/bochs/Kconfig"
201 source "drivers/gpu/drm/virtio/Kconfig"
203 source "drivers/gpu/drm/msm/Kconfig"
205 source "drivers/gpu/drm/fsl-dcu/Kconfig"
207 source "drivers/gpu/drm/tegra/Kconfig"
209 source "drivers/gpu/drm/panel/Kconfig"
211 source "drivers/gpu/drm/bridge/Kconfig"
213 source "drivers/gpu/drm/sti/Kconfig"
215 source "drivers/gpu/drm/amd/amdkfd/Kconfig"
217 source "drivers/gpu/drm/imx/Kconfig"
219 source "drivers/gpu/drm/vc4/Kconfig"
221 source "drivers/gpu/drm/etnaviv/Kconfig"
223 source "drivers/gpu/drm/arc/Kconfig"
225 source "drivers/gpu/drm/hisilicon/Kconfig"
227 source "drivers/gpu/drm/mediatek/Kconfig"
229 # Keep legacy drivers last
231 menuconfig DRM_LEGACY
232 bool "Enable legacy drivers (DANGEROUS)"
236 Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous
237 APIs to user-space, which can be used to circumvent access
238 restrictions and other security measures. For backwards compatibility
239 those drivers are still available, but their use is highly
240 inadvisable and might harm your system.
242 You are recommended to use the safe modeset-only drivers instead, and
243 perform 3D emulation in user-space.
245 Unless you have strong reasons to go rogue, say "N".
250 tristate "3dfx Banshee/Voodoo3+"
251 depends on DRM && PCI
253 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
254 graphics card. If M is selected, the module will be called tdfx.
257 tristate "ATI Rage 128"
258 depends on DRM && PCI
261 Choose this option if you have an ATI Rage 128 graphics card. If M
262 is selected, the module will be called r128. AGP support for
263 this card is strongly suggested (unless you have a PCI version).
266 tristate "Intel I810"
267 # !PREEMPT because of missing ioctl locking
268 depends on DRM && AGP && AGP_INTEL && (!PREEMPT || BROKEN)
270 Choose this option if you have an Intel I810 graphics card. If M is
271 selected, the module will be called i810. AGP support is required
272 for this driver to work.
275 tristate "Matrox g200/g400"
276 depends on DRM && PCI
279 Choose this option if you have a Matrox G200, G400 or G450 graphics
280 card. If M is selected, the module will be called mga. AGP
281 support is required for this driver to work.
284 tristate "SiS video cards"
285 depends on DRM && AGP
286 depends on FB_SIS || FB_SIS=n
288 Choose this option if you have a SiS 630 or compatible video
289 chipset. If M is selected the module will be called sis. AGP
290 support is required for this driver to work.
293 tristate "Via unichrome video cards"
294 depends on DRM && PCI
296 Choose this option if you have a Via unichrome or compatible video
297 chipset. If M is selected the module will be called via.
300 tristate "Savage video cards"
301 depends on DRM && PCI
303 Choose this option if you have a Savage3D/4/SuperSavage/Pro/Twister
304 chipset. If M is selected the module will be called savage.