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 && HAS_DMA
10 select DRM_PANEL_ORIENTATION_QUIRKS
15 select DMA_SHARED_BUFFER
18 Kernel-level support for the Direct Rendering Infrastructure (DRI)
19 introduced in XFree86 4.0. If you say Y here, you need to select
20 the module that's right for your graphics card from the list below.
21 These modules provide support for synchronization, security, and
22 DMA transfers. Please see <http://dri.sourceforge.net/> for more
23 details. You should also select and configure AGP
24 (/dev/agpgart) support if it is available for your platform.
30 config DRM_DP_AUX_CHARDEV
31 bool "DRM DP AUX Interface"
34 Choose this option to enable a /dev/drm_dp_auxN node that allows to
35 read and write values to arbitrary DPCD registers on the DP aux
39 bool "Insert extra checks and debug info into the DRM range managers"
42 depends on STACKTRACE_SUPPORT
45 Enable allocation tracking of memory manager and leak detection on
48 Recommended for driver developers only.
52 config DRM_DEBUG_SELFTEST
53 tristate "kselftests for DRM"
55 depends on DEBUG_KERNEL
61 This option provides kernel modules that can be used to run
62 various selftests on parts of the DRM api. This option is not
63 useful for distributions or general kernels, but only for kernel
64 developers working on DRM and associated drivers.
72 CRTC helpers for KMS drivers.
74 config DRM_KMS_FB_HELPER
76 depends on DRM_KMS_HELPER
78 select FRAMEBUFFER_CONSOLE if !EXPERT
79 select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
81 select FB_SYS_FILLRECT
82 select FB_SYS_COPYAREA
83 select FB_SYS_IMAGEBLIT
84 select FB_CFB_FILLRECT
85 select FB_CFB_COPYAREA
86 select FB_CFB_IMAGEBLIT
89 FBDEV helpers for KMS drivers.
91 config DRM_FBDEV_EMULATION
92 bool "Enable legacy fbdev support for your modesetting driver"
95 select DRM_KMS_FB_HELPER
98 Choose this option if you have a need for the legacy fbdev
99 support. Note that this support also provides the linux console
100 support on top of your modesetting driver.
102 If in doubt, say "Y".
104 config DRM_FBDEV_OVERALLOC
105 int "Overallocation of the fbdev buffer"
106 depends on DRM_FBDEV_EMULATION
109 Defines the fbdev buffer overallocation in percent. Default
110 is 100. Typical values for double buffering will be 200,
111 triple buffering 300.
113 config DRM_FBDEV_LEAK_PHYS_SMEM
114 bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)"
115 depends on DRM_FBDEV_EMULATION && EXPERT
118 In order to keep user-space compatibility, we want in certain
119 use-cases to keep leaking the fbdev physical address to the
120 user-space program handling the fbdev buffer.
121 This affects, not only, Amlogic, Allwinner or Rockchip devices
122 with ARM Mali GPUs using an userspace Blob.
123 This option is not supported by upstream developers and should be
124 removed as soon as possible and be considered as a broken and
125 legacy behaviour from a modern fbdev device driver.
127 Please send any bug reports when using this to your proprietary
128 software vendor that requires this.
130 If in doubt, say "N" or spread the word to your closed source
133 config DRM_LOAD_EDID_FIRMWARE
134 bool "Allow to specify an EDID data set instead of probing for it"
137 Say Y here, if you want to use EDID data to be loaded from the
138 /lib/firmware directory or one of the provided built-in
139 data sets. This may be necessary, if the graphics adapter or
140 monitor are unable to provide appropriate EDID data. Since this
141 feature is provided as a workaround for broken hardware, the
142 default case is N. Details and instructions how to build your own
143 EDID data are given in Documentation/EDID/HOWTO.txt.
146 bool "Enable DisplayPort CEC-Tunneling-over-AUX HDMI support"
149 Choose this option if you want to enable HDMI CEC support for
150 DisplayPort/USB-C to HDMI adapters.
152 Note: not all adapters support this feature, and even for those
153 that do support this they often do not hook up the CEC pin.
157 depends on DRM && MMU
159 GPU memory management subsystem for devices with multiple
160 GPU memory types. Will be enabled automatically if a device driver
163 config DRM_GEM_CMA_HELPER
167 Choose this if you need the GEM CMA helper functions
169 config DRM_KMS_CMA_HELPER
172 select DRM_GEM_CMA_HELPER
174 Choose this if you need the KMS CMA helper functions
178 depends on DRM && MMU
184 source "drivers/gpu/drm/i2c/Kconfig"
186 source "drivers/gpu/drm/arm/Kconfig"
189 tristate "ATI Radeon"
190 depends on DRM && PCI && MMU
192 select DRM_KMS_HELPER
196 select BACKLIGHT_CLASS_DEVICE
197 select BACKLIGHT_LCD_SUPPORT
200 Choose this option if you have an ATI Radeon graphics card. There
201 are both PCI and AGP versions. You don't need to choose this to
202 run the Radeon in plain VGA mode.
204 If M is selected, the module will be called radeon.
206 source "drivers/gpu/drm/radeon/Kconfig"
210 depends on DRM && PCI && MMU
212 select DRM_KMS_HELPER
217 select BACKLIGHT_CLASS_DEVICE
218 select BACKLIGHT_LCD_SUPPORT
222 Choose this option if you have a recent AMD Radeon graphics card.
224 If M is selected, the module will be called amdgpu.
226 source "drivers/gpu/drm/amd/amdgpu/Kconfig"
228 source "drivers/gpu/drm/amd/lib/Kconfig"
230 source "drivers/gpu/drm/nouveau/Kconfig"
232 source "drivers/gpu/drm/i915/Kconfig"
235 tristate "Virtual GEM provider"
238 Choose this option to get a virtual graphics memory manager,
239 as used by Mesa's software renderer for enhanced performance.
240 If M is selected the module will be called vgem.
243 tristate "Virtual KMS (EXPERIMENTAL)"
245 select DRM_KMS_HELPER
248 Virtual Kernel Mode-Setting (VKMS) is used for testing or for
249 running GPU in a headless machines. Choose this option to get
252 If M is selected the module will be called vkms.
254 source "drivers/gpu/drm/exynos/Kconfig"
256 source "drivers/gpu/drm/rockchip/Kconfig"
258 source "drivers/gpu/drm/vmwgfx/Kconfig"
260 source "drivers/gpu/drm/gma500/Kconfig"
262 source "drivers/gpu/drm/udl/Kconfig"
264 source "drivers/gpu/drm/ast/Kconfig"
266 source "drivers/gpu/drm/mgag200/Kconfig"
268 source "drivers/gpu/drm/cirrus/Kconfig"
270 source "drivers/gpu/drm/armada/Kconfig"
272 source "drivers/gpu/drm/atmel-hlcdc/Kconfig"
274 source "drivers/gpu/drm/rcar-du/Kconfig"
276 source "drivers/gpu/drm/shmobile/Kconfig"
278 source "drivers/gpu/drm/sun4i/Kconfig"
280 source "drivers/gpu/drm/omapdrm/Kconfig"
282 source "drivers/gpu/drm/tilcdc/Kconfig"
284 source "drivers/gpu/drm/qxl/Kconfig"
286 source "drivers/gpu/drm/bochs/Kconfig"
288 source "drivers/gpu/drm/virtio/Kconfig"
290 source "drivers/gpu/drm/msm/Kconfig"
292 source "drivers/gpu/drm/fsl-dcu/Kconfig"
294 source "drivers/gpu/drm/tegra/Kconfig"
296 source "drivers/gpu/drm/stm/Kconfig"
298 source "drivers/gpu/drm/panel/Kconfig"
300 source "drivers/gpu/drm/bridge/Kconfig"
302 source "drivers/gpu/drm/sti/Kconfig"
304 source "drivers/gpu/drm/imx/Kconfig"
306 source "drivers/gpu/drm/v3d/Kconfig"
308 source "drivers/gpu/drm/vc4/Kconfig"
310 source "drivers/gpu/drm/etnaviv/Kconfig"
312 source "drivers/gpu/drm/arc/Kconfig"
314 source "drivers/gpu/drm/hisilicon/Kconfig"
316 source "drivers/gpu/drm/mediatek/Kconfig"
318 source "drivers/gpu/drm/zte/Kconfig"
320 source "drivers/gpu/drm/mxsfb/Kconfig"
322 source "drivers/gpu/drm/meson/Kconfig"
324 source "drivers/gpu/drm/tinydrm/Kconfig"
326 source "drivers/gpu/drm/pl111/Kconfig"
328 source "drivers/gpu/drm/tve200/Kconfig"
330 source "drivers/gpu/drm/xen/Kconfig"
332 # Keep legacy drivers last
334 menuconfig DRM_LEGACY
335 bool "Enable legacy drivers (DANGEROUS)"
336 depends on DRM && MMU
339 Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous
340 APIs to user-space, which can be used to circumvent access
341 restrictions and other security measures. For backwards compatibility
342 those drivers are still available, but their use is highly
343 inadvisable and might harm your system.
345 You are recommended to use the safe modeset-only drivers instead, and
346 perform 3D emulation in user-space.
348 Unless you have strong reasons to go rogue, say "N".
353 tristate "3dfx Banshee/Voodoo3+"
354 depends on DRM && PCI
356 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
357 graphics card. If M is selected, the module will be called tdfx.
360 tristate "ATI Rage 128"
361 depends on DRM && PCI
364 Choose this option if you have an ATI Rage 128 graphics card. If M
365 is selected, the module will be called r128. AGP support for
366 this card is strongly suggested (unless you have a PCI version).
369 tristate "Intel I810"
370 # !PREEMPT because of missing ioctl locking
371 depends on DRM && AGP && AGP_INTEL && (!PREEMPT || BROKEN)
373 Choose this option if you have an Intel I810 graphics card. If M is
374 selected, the module will be called i810. AGP support is required
375 for this driver to work.
378 tristate "Matrox g200/g400"
379 depends on DRM && PCI
382 Choose this option if you have a Matrox G200, G400 or G450 graphics
383 card. If M is selected, the module will be called mga. AGP
384 support is required for this driver to work.
387 tristate "SiS video cards"
388 depends on DRM && AGP
389 depends on FB_SIS || FB_SIS=n
391 Choose this option if you have a SiS 630 or compatible video
392 chipset. If M is selected the module will be called sis. AGP
393 support is required for this driver to work.
396 tristate "Via unichrome video cards"
397 depends on DRM && PCI
399 Choose this option if you have a Via unichrome or compatible video
400 chipset. If M is selected the module will be called via.
403 tristate "Savage video cards"
404 depends on DRM && PCI
406 Choose this option if you have a Savage3D/4/SuperSavage/Pro/Twister
407 chipset. If M is selected the module will be called savage.
411 # Separate option because drm_panel_orientation_quirks.c is shared with fbdev
412 config DRM_PANEL_ORIENTATION_QUIRKS
415 config DRM_LIB_RANDOM