1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Drm device configuration 4# 5# This driver provides support for the 6# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher. 7# 8menuconfig DRM 9 tristate "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)" 10 depends on (AGP || AGP=n) && !EMULATED_CMPXCHG && HAS_DMA 11 select DRM_PANEL_ORIENTATION_QUIRKS 12 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION 13 select FB_CORE if DRM_FBDEV_EMULATION 14 select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION 15 select HDMI 16 select I2C 17 select DMA_SHARED_BUFFER 18 select SYNC_FILE 19# gallium uses SYS_kcmp for os_same_file_description() to de-duplicate 20# device and dmabuf fd. Let's make sure that is available for our userspace. 21 select KCMP 22 select VIDEO 23 help 24 Kernel-level support for the Direct Rendering Infrastructure (DRI) 25 introduced in XFree86 4.0. If you say Y here, you need to select 26 the module that's right for your graphics card from the list below. 27 These modules provide support for synchronization, security, and 28 DMA transfers. Please see <http://dri.sourceforge.net/> for more 29 details. You should also select and configure AGP 30 (/dev/agpgart) support if it is available for your platform. 31 32config DRM_MIPI_DBI 33 tristate 34 depends on DRM 35 select DRM_KMS_HELPER 36 37config DRM_MIPI_DSI 38 bool 39 depends on DRM 40 41config DRM_DEBUG_MM 42 bool "Insert extra checks and debug info into the DRM range managers" 43 default n 44 depends on DRM 45 depends on STACKTRACE_SUPPORT 46 select STACKDEPOT 47 help 48 Enable allocation tracking of memory manager and leak detection on 49 shutdown. 50 51 Recommended for driver developers only. 52 53 If in doubt, say "N". 54 55config DRM_USE_DYNAMIC_DEBUG 56 bool "use dynamic debug to implement drm.debug" 57 default n 58 depends on BROKEN 59 depends on DRM 60 depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE 61 depends on JUMP_LABEL 62 help 63 Use dynamic-debug to avoid drm_debug_enabled() runtime overheads. 64 Due to callsite counts in DRM drivers (~4k in amdgpu) and 56 65 bytes per callsite, the .data costs can be substantial, and 66 are therefore configurable. 67 68config DRM_KUNIT_TEST_HELPERS 69 tristate 70 depends on DRM && KUNIT 71 select DRM_KMS_HELPER 72 help 73 KUnit Helpers for KMS drivers. 74 75config DRM_KUNIT_TEST 76 tristate "KUnit tests for DRM" if !KUNIT_ALL_TESTS 77 depends on DRM && KUNIT && MMU 78 select DRM_BUDDY 79 select DRM_DISPLAY_DP_HELPER 80 select DRM_DISPLAY_HELPER 81 select DRM_EXEC 82 select DRM_EXPORT_FOR_TESTS if m 83 select DRM_GEM_SHMEM_HELPER 84 select DRM_KUNIT_TEST_HELPERS 85 select DRM_LIB_RANDOM 86 select PRIME_NUMBERS 87 default KUNIT_ALL_TESTS 88 help 89 This builds unit tests for DRM. This option is not useful for 90 distributions or general kernels, but only for kernel 91 developers working on DRM and associated drivers. 92 93 For more information on KUnit and unit tests in general, 94 please refer to the KUnit documentation in 95 Documentation/dev-tools/kunit/. 96 97 If in doubt, say "N". 98 99config DRM_KMS_HELPER 100 tristate 101 depends on DRM 102 help 103 CRTC helpers for KMS drivers. 104 105config DRM_DEBUG_DP_MST_TOPOLOGY_REFS 106 bool "Enable refcount backtrace history in the DP MST helpers" 107 depends on STACKTRACE_SUPPORT 108 select STACKDEPOT 109 depends on DRM_KMS_HELPER 110 depends on DEBUG_KERNEL 111 depends on EXPERT 112 help 113 Enables debug tracing for topology refs in DRM's DP MST helpers. A 114 history of each topology reference/dereference will be printed to the 115 kernel log once a port or branch device's topology refcount reaches 0. 116 117 This has the potential to use a lot of memory and print some very 118 large kernel messages. If in doubt, say "N". 119 120config DRM_DEBUG_MODESET_LOCK 121 bool "Enable backtrace history for lock contention" 122 depends on STACKTRACE_SUPPORT 123 depends on DEBUG_KERNEL 124 depends on EXPERT 125 select STACKDEPOT 126 default y if DEBUG_WW_MUTEX_SLOWPATH 127 help 128 Enable debug tracing of failures to gracefully handle drm modeset lock 129 contention. A history of each drm modeset lock path hitting -EDEADLK 130 will be saved until gracefully handled, and the backtrace will be 131 printed when attempting to lock a contended lock. 132 133 If in doubt, say "N". 134 135config DRM_FBDEV_EMULATION 136 bool "Enable legacy fbdev support for your modesetting driver" 137 depends on DRM 138 select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE 139 default FB 140 help 141 Choose this option if you have a need for the legacy fbdev 142 support. Note that this support also provides the linux console 143 support on top of your modesetting driver. 144 145 If in doubt, say "Y". 146 147config DRM_FBDEV_OVERALLOC 148 int "Overallocation of the fbdev buffer" 149 depends on DRM_FBDEV_EMULATION 150 default 100 151 help 152 Defines the fbdev buffer overallocation in percent. Default 153 is 100. Typical values for double buffering will be 200, 154 triple buffering 300. 155 156config DRM_FBDEV_LEAK_PHYS_SMEM 157 bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)" 158 depends on DRM_FBDEV_EMULATION && EXPERT 159 default n 160 help 161 In order to keep user-space compatibility, we want in certain 162 use-cases to keep leaking the fbdev physical address to the 163 user-space program handling the fbdev buffer. 164 This affects, not only, Amlogic, Allwinner or Rockchip devices 165 with ARM Mali GPUs using an userspace Blob. 166 This option is not supported by upstream developers and should be 167 removed as soon as possible and be considered as a broken and 168 legacy behaviour from a modern fbdev device driver. 169 170 Please send any bug reports when using this to your proprietary 171 software vendor that requires this. 172 173 If in doubt, say "N" or spread the word to your closed source 174 library vendor. 175 176config DRM_LOAD_EDID_FIRMWARE 177 bool "Allow to specify an EDID data set instead of probing for it" 178 depends on DRM 179 help 180 Say Y here, if you want to use EDID data to be loaded from the 181 /lib/firmware directory or one of the provided built-in 182 data sets. This may be necessary, if the graphics adapter or 183 monitor are unable to provide appropriate EDID data. Since this 184 feature is provided as a workaround for broken hardware, the 185 default case is N. Details and instructions how to build your own 186 EDID data are given in Documentation/admin-guide/edid.rst. 187 188source "drivers/gpu/drm/display/Kconfig" 189 190config DRM_TTM 191 tristate 192 depends on DRM && MMU 193 help 194 GPU memory management subsystem for devices with multiple 195 GPU memory types. Will be enabled automatically if a device driver 196 uses it. 197 198config DRM_TTM_KUNIT_TEST 199 tristate "KUnit tests for TTM" if !KUNIT_ALL_TESTS 200 default n 201 depends on DRM && KUNIT && MMU && (UML || COMPILE_TEST) 202 select DRM_TTM 203 select DRM_EXPORT_FOR_TESTS if m 204 select DRM_KUNIT_TEST_HELPERS 205 default KUNIT_ALL_TESTS 206 help 207 Enables unit tests for TTM, a GPU memory manager subsystem used 208 to manage memory buffers. This option is mostly useful for kernel 209 developers. It depends on (UML || COMPILE_TEST) since no other driver 210 which uses TTM can be loaded while running the tests. 211 212 If in doubt, say "N". 213 214config DRM_EXEC 215 tristate 216 depends on DRM 217 help 218 Execution context for command submissions 219 220config DRM_GPUVM 221 tristate 222 depends on DRM 223 help 224 GPU-VM representation providing helpers to manage a GPUs virtual 225 address space 226 227config DRM_BUDDY 228 tristate 229 depends on DRM 230 help 231 A page based buddy allocator 232 233config DRM_VRAM_HELPER 234 tristate 235 depends on DRM 236 help 237 Helpers for VRAM memory management 238 239config DRM_TTM_HELPER 240 tristate 241 depends on DRM 242 select DRM_TTM 243 help 244 Helpers for ttm-based gem objects 245 246config DRM_GEM_DMA_HELPER 247 tristate 248 depends on DRM 249 select FB_DMAMEM_HELPERS if DRM_FBDEV_EMULATION 250 help 251 Choose this if you need the GEM DMA helper functions 252 253config DRM_GEM_SHMEM_HELPER 254 tristate 255 depends on DRM && MMU 256 help 257 Choose this if you need the GEM shmem helper functions 258 259config DRM_SUBALLOC_HELPER 260 tristate 261 depends on DRM 262 263config DRM_SCHED 264 tristate 265 depends on DRM 266 267source "drivers/gpu/drm/i2c/Kconfig" 268 269source "drivers/gpu/drm/arm/Kconfig" 270 271source "drivers/gpu/drm/radeon/Kconfig" 272 273source "drivers/gpu/drm/amd/amdgpu/Kconfig" 274 275source "drivers/gpu/drm/nouveau/Kconfig" 276 277source "drivers/gpu/drm/i915/Kconfig" 278 279source "drivers/gpu/drm/xe/Kconfig" 280 281source "drivers/gpu/drm/kmb/Kconfig" 282 283config DRM_VGEM 284 tristate "Virtual GEM provider" 285 depends on DRM && MMU 286 select DRM_GEM_SHMEM_HELPER 287 help 288 Choose this option to get a virtual graphics memory manager, 289 as used by Mesa's software renderer for enhanced performance. 290 If M is selected the module will be called vgem. 291 292source "drivers/gpu/drm/vkms/Kconfig" 293 294source "drivers/gpu/drm/exynos/Kconfig" 295 296source "drivers/gpu/drm/rockchip/Kconfig" 297 298source "drivers/gpu/drm/vmwgfx/Kconfig" 299 300source "drivers/gpu/drm/gma500/Kconfig" 301 302source "drivers/gpu/drm/udl/Kconfig" 303 304source "drivers/gpu/drm/ast/Kconfig" 305 306source "drivers/gpu/drm/mgag200/Kconfig" 307 308source "drivers/gpu/drm/armada/Kconfig" 309 310source "drivers/gpu/drm/atmel-hlcdc/Kconfig" 311 312source "drivers/gpu/drm/renesas/Kconfig" 313 314source "drivers/gpu/drm/sun4i/Kconfig" 315 316source "drivers/gpu/drm/omapdrm/Kconfig" 317 318source "drivers/gpu/drm/tilcdc/Kconfig" 319 320source "drivers/gpu/drm/qxl/Kconfig" 321 322source "drivers/gpu/drm/virtio/Kconfig" 323 324source "drivers/gpu/drm/msm/Kconfig" 325 326source "drivers/gpu/drm/fsl-dcu/Kconfig" 327 328source "drivers/gpu/drm/tegra/Kconfig" 329 330source "drivers/gpu/drm/stm/Kconfig" 331 332source "drivers/gpu/drm/panel/Kconfig" 333 334source "drivers/gpu/drm/bridge/Kconfig" 335 336source "drivers/gpu/drm/sti/Kconfig" 337 338source "drivers/gpu/drm/imx/Kconfig" 339 340source "drivers/gpu/drm/ingenic/Kconfig" 341 342source "drivers/gpu/drm/v3d/Kconfig" 343 344source "drivers/gpu/drm/vc4/Kconfig" 345 346source "drivers/gpu/drm/loongson/Kconfig" 347 348source "drivers/gpu/drm/etnaviv/Kconfig" 349 350source "drivers/gpu/drm/hisilicon/Kconfig" 351 352source "drivers/gpu/drm/logicvc/Kconfig" 353 354source "drivers/gpu/drm/mediatek/Kconfig" 355 356source "drivers/gpu/drm/mxsfb/Kconfig" 357 358source "drivers/gpu/drm/meson/Kconfig" 359 360source "drivers/gpu/drm/tiny/Kconfig" 361 362source "drivers/gpu/drm/pl111/Kconfig" 363 364source "drivers/gpu/drm/tve200/Kconfig" 365 366source "drivers/gpu/drm/xen/Kconfig" 367 368source "drivers/gpu/drm/vboxvideo/Kconfig" 369 370source "drivers/gpu/drm/lima/Kconfig" 371 372source "drivers/gpu/drm/panfrost/Kconfig" 373 374source "drivers/gpu/drm/aspeed/Kconfig" 375 376source "drivers/gpu/drm/mcde/Kconfig" 377 378source "drivers/gpu/drm/tidss/Kconfig" 379 380source "drivers/gpu/drm/xlnx/Kconfig" 381 382source "drivers/gpu/drm/gud/Kconfig" 383 384source "drivers/gpu/drm/solomon/Kconfig" 385 386source "drivers/gpu/drm/sprd/Kconfig" 387 388source "drivers/gpu/drm/imagination/Kconfig" 389 390config DRM_HYPERV 391 tristate "DRM Support for Hyper-V synthetic video device" 392 depends on DRM && PCI && MMU && HYPERV 393 select DRM_KMS_HELPER 394 select DRM_GEM_SHMEM_HELPER 395 help 396 This is a KMS driver for Hyper-V synthetic video device. Choose this 397 option if you would like to enable drm driver for Hyper-V virtual 398 machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so 399 that DRM driver is used by default. 400 401 If M is selected the module will be called hyperv_drm. 402 403config DRM_EXPORT_FOR_TESTS 404 bool 405 406# Separate option because drm_panel_orientation_quirks.c is shared with fbdev 407config DRM_PANEL_ORIENTATION_QUIRKS 408 tristate 409 410config DRM_LIB_RANDOM 411 bool 412 default n 413 414config DRM_PRIVACY_SCREEN 415 bool 416 default n 417