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 HDMI 13 select I2C 14 select DMA_SHARED_BUFFER 15 select SYNC_FILE 16# gallium uses SYS_kcmp for os_same_file_description() to de-duplicate 17# device and dmabuf fd. Let's make sure that is available for our userspace. 18 select KCMP 19 select VIDEO 20 help 21 Kernel-level support for the Direct Rendering Infrastructure (DRI) 22 introduced in XFree86 4.0. If you say Y here, you need to select 23 the module that's right for your graphics card from the list below. 24 These modules provide support for synchronization, security, and 25 DMA transfers. Please see <http://dri.sourceforge.net/> for more 26 details. You should also select and configure AGP 27 (/dev/agpgart) support if it is available for your platform. 28 29if DRM 30 31config DRM_MIPI_DBI 32 tristate 33 depends on DRM 34 select DRM_KMS_HELPER 35 36config DRM_MIPI_DSI 37 bool 38 depends on DRM 39 40config DRM_DEBUG_MM 41 bool "Insert extra checks and debug info into the DRM range managers" 42 default n 43 depends on DRM 44 depends on STACKTRACE_SUPPORT 45 select STACKDEPOT 46 help 47 Enable allocation tracking of memory manager and leak detection on 48 shutdown. 49 50 Recommended for driver developers only. 51 52 If in doubt, say "N". 53 54config DRM_USE_DYNAMIC_DEBUG 55 bool "use dynamic debug to implement drm.debug" 56 default n 57 depends on BROKEN 58 depends on DRM 59 depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE 60 depends on JUMP_LABEL 61 help 62 Use dynamic-debug to avoid drm_debug_enabled() runtime overheads. 63 Due to callsite counts in DRM drivers (~4k in amdgpu) and 56 64 bytes per callsite, the .data costs can be substantial, and 65 are therefore configurable. 66 67config DRM_KUNIT_TEST_HELPERS 68 tristate 69 depends on DRM && KUNIT 70 select DRM_KMS_HELPER 71 help 72 KUnit Helpers for KMS drivers. 73 74config DRM_KUNIT_TEST 75 tristate "KUnit tests for DRM" if !KUNIT_ALL_TESTS 76 depends on DRM && KUNIT && MMU 77 select DRM_BUDDY 78 select DRM_DISPLAY_DP_HELPER 79 select DRM_DISPLAY_HDMI_STATE_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 select FB_CORE if DRM_FBDEV_EMULATION 103 help 104 CRTC helpers for KMS drivers. 105 106config DRM_DRAW 107 bool 108 depends on DRM 109 110config DRM_PANIC 111 bool "Display a user-friendly message when a kernel panic occurs" 112 depends on DRM 113 select FONT_SUPPORT 114 select DRM_DRAW 115 help 116 Enable a drm panic handler, which will display a user-friendly message 117 when a kernel panic occurs. It's useful when using a user-space 118 console instead of fbcon. 119 It will only work if your graphic driver supports this feature. 120 To support Hi-DPI Display, you can enable bigger fonts like 121 FONT_TER16x32 122 123config DRM_PANIC_FOREGROUND_COLOR 124 hex "Drm panic screen foreground color, in RGB" 125 depends on DRM_PANIC 126 default 0xffffff 127 128config DRM_PANIC_BACKGROUND_COLOR 129 hex "Drm panic screen background color, in RGB" 130 depends on DRM_PANIC 131 default 0x000000 132 133config DRM_PANIC_DEBUG 134 bool "Add a debug fs entry to trigger drm_panic" 135 depends on DRM_PANIC && DEBUG_FS 136 help 137 Add dri/[device]/drm_panic_plane_x in the kernel debugfs, to force the 138 panic handler to write the panic message to this plane scanout buffer. 139 This is unsafe and should not be enabled on a production build. 140 If in doubt, say "N". 141 142config DRM_PANIC_SCREEN 143 string "Panic screen formatter" 144 default "user" 145 depends on DRM_PANIC 146 help 147 This option enable to choose what will be displayed when a kernel 148 panic occurs. You can choose between "user", a short message telling 149 the user to reboot the system, or "kmsg" which will display the last 150 lines of kmsg. 151 This can also be overridden by drm.panic_screen=xxxx kernel parameter 152 or by writing to /sys/module/drm/parameters/panic_screen sysfs entry 153 Default is "user" 154 155config DRM_PANIC_SCREEN_QR_CODE 156 bool "Add a panic screen with a QR code" 157 depends on DRM_PANIC && RUST 158 select ZLIB_DEFLATE 159 help 160 This option adds a QR code generator, and a panic screen with a QR 161 code. The QR code will contain the last lines of kmsg and other debug 162 information. This should be easier for the user to report a kernel 163 panic, with all debug information available. 164 To use this panic screen, also set DRM_PANIC_SCREEN to "qr_code" 165 166config DRM_PANIC_SCREEN_QR_CODE_URL 167 string "Base URL of the QR code in the panic screen" 168 depends on DRM_PANIC_SCREEN_QR_CODE 169 help 170 This option sets the base URL to report the kernel panic. If it's set 171 the QR code will contain the URL and the kmsg compressed with zlib as 172 a URL parameter. If it's empty, the QR code will contain the kmsg as 173 uncompressed text only. 174 There is a demo code in javascript, to decode and uncompress the kmsg 175 data from the URL parameter at https://github.com/kdj0c/panic_report 176 177config DRM_PANIC_SCREEN_QR_VERSION 178 int "Maximum version (size) of the QR code." 179 depends on DRM_PANIC_SCREEN_QR_CODE 180 default 40 181 help 182 This option limits the version (or size) of the QR code. QR code 183 version ranges from Version 1 (21x21) to Version 40 (177x177). 184 Smaller QR code are easier to read, but will contain less debugging 185 data. Default is 40. 186 187config DRM_DEBUG_DP_MST_TOPOLOGY_REFS 188 bool "Enable refcount backtrace history in the DP MST helpers" 189 depends on STACKTRACE_SUPPORT 190 select STACKDEPOT 191 depends on DRM_KMS_HELPER 192 depends on DEBUG_KERNEL 193 depends on EXPERT 194 help 195 Enables debug tracing for topology refs in DRM's DP MST helpers. A 196 history of each topology reference/dereference will be printed to the 197 kernel log once a port or branch device's topology refcount reaches 0. 198 199 This has the potential to use a lot of memory and print some very 200 large kernel messages. If in doubt, say "N". 201 202config DRM_DEBUG_MODESET_LOCK 203 bool "Enable backtrace history for lock contention" 204 depends on STACKTRACE_SUPPORT 205 depends on DEBUG_KERNEL 206 depends on EXPERT 207 select STACKDEPOT 208 default y if DEBUG_WW_MUTEX_SLOWPATH 209 help 210 Enable debug tracing of failures to gracefully handle drm modeset lock 211 contention. A history of each drm modeset lock path hitting -EDEADLK 212 will be saved until gracefully handled, and the backtrace will be 213 printed when attempting to lock a contended lock. 214 215 If in doubt, say "N". 216 217config DRM_CLIENT 218 bool 219 depends on DRM 220 help 221 Enables support for DRM clients. DRM drivers that need 222 struct drm_client_dev and its interfaces should select this 223 option. Drivers that support the default clients should 224 select DRM_CLIENT_SELECTION instead. 225 226source "drivers/gpu/drm/clients/Kconfig" 227 228config DRM_LOAD_EDID_FIRMWARE 229 bool "Allow to specify an EDID data set instead of probing for it" 230 depends on DRM 231 help 232 Say Y here, if you want to use EDID data to be loaded from the 233 /lib/firmware directory or one of the provided built-in 234 data sets. This may be necessary, if the graphics adapter or 235 monitor are unable to provide appropriate EDID data. Since this 236 feature is provided as a workaround for broken hardware, the 237 default case is N. Details and instructions how to build your own 238 EDID data are given in Documentation/admin-guide/edid.rst. 239 240source "drivers/gpu/drm/display/Kconfig" 241 242config DRM_TTM 243 tristate 244 depends on DRM && MMU 245 help 246 GPU memory management subsystem for devices with multiple 247 GPU memory types. Will be enabled automatically if a device driver 248 uses it. 249 250config DRM_TTM_KUNIT_TEST 251 tristate "KUnit tests for TTM" if !KUNIT_ALL_TESTS 252 default n 253 depends on DRM && KUNIT && MMU && (UML || COMPILE_TEST) 254 select DRM_TTM 255 select DRM_BUDDY 256 select DRM_EXPORT_FOR_TESTS if m 257 select DRM_KUNIT_TEST_HELPERS 258 default KUNIT_ALL_TESTS 259 help 260 Enables unit tests for TTM, a GPU memory manager subsystem used 261 to manage memory buffers. This option is mostly useful for kernel 262 developers. It depends on (UML || COMPILE_TEST) since no other driver 263 which uses TTM can be loaded while running the tests. 264 265 If in doubt, say "N". 266 267config DRM_EXEC 268 tristate 269 depends on DRM 270 help 271 Execution context for command submissions 272 273config DRM_GPUVM 274 tristate 275 depends on DRM 276 select DRM_EXEC 277 help 278 GPU-VM representation providing helpers to manage a GPUs virtual 279 address space 280 281config DRM_GPUSVM 282 tristate 283 depends on DRM && DEVICE_PRIVATE 284 select HMM_MIRROR 285 select MMU_NOTIFIER 286 help 287 GPU-SVM representation providing helpers to manage a GPUs shared 288 virtual memory 289 290config DRM_BUDDY 291 tristate 292 depends on DRM 293 help 294 A page based buddy allocator 295 296config DRM_VRAM_HELPER 297 tristate 298 depends on DRM 299 help 300 Helpers for VRAM memory management 301 302config DRM_TTM_HELPER 303 tristate 304 depends on DRM 305 select DRM_TTM 306 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION 307 select FB_CORE if DRM_FBDEV_EMULATION 308 select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION 309 help 310 Helpers for ttm-based gem objects 311 312config DRM_GEM_DMA_HELPER 313 tristate 314 depends on DRM 315 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION 316 select FB_CORE if DRM_FBDEV_EMULATION 317 select FB_DMAMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION 318 help 319 Choose this if you need the GEM DMA helper functions 320 321config DRM_GEM_SHMEM_HELPER 322 tristate 323 depends on DRM && MMU 324 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION 325 select FB_CORE if DRM_FBDEV_EMULATION 326 select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION 327 help 328 Choose this if you need the GEM shmem helper functions 329 330config DRM_SUBALLOC_HELPER 331 tristate 332 depends on DRM 333 334config DRM_SCHED 335 tristate 336 depends on DRM 337 338source "drivers/gpu/drm/arm/Kconfig" 339 340source "drivers/gpu/drm/radeon/Kconfig" 341 342source "drivers/gpu/drm/amd/amdgpu/Kconfig" 343 344source "drivers/gpu/drm/nouveau/Kconfig" 345 346source "drivers/gpu/drm/i915/Kconfig" 347 348source "drivers/gpu/drm/xe/Kconfig" 349 350source "drivers/gpu/drm/kmb/Kconfig" 351 352config DRM_VGEM 353 tristate "Virtual GEM provider" 354 depends on DRM && MMU 355 select DRM_GEM_SHMEM_HELPER 356 help 357 Choose this option to get a virtual graphics memory manager, 358 as used by Mesa's software renderer for enhanced performance. 359 If M is selected the module will be called vgem. 360 361source "drivers/gpu/drm/vkms/Kconfig" 362 363source "drivers/gpu/drm/exynos/Kconfig" 364 365source "drivers/gpu/drm/rockchip/Kconfig" 366 367source "drivers/gpu/drm/vmwgfx/Kconfig" 368 369source "drivers/gpu/drm/gma500/Kconfig" 370 371source "drivers/gpu/drm/udl/Kconfig" 372 373source "drivers/gpu/drm/ast/Kconfig" 374 375source "drivers/gpu/drm/mgag200/Kconfig" 376 377source "drivers/gpu/drm/armada/Kconfig" 378 379source "drivers/gpu/drm/atmel-hlcdc/Kconfig" 380 381source "drivers/gpu/drm/renesas/Kconfig" 382 383source "drivers/gpu/drm/sun4i/Kconfig" 384 385source "drivers/gpu/drm/omapdrm/Kconfig" 386 387source "drivers/gpu/drm/tilcdc/Kconfig" 388 389source "drivers/gpu/drm/qxl/Kconfig" 390 391source "drivers/gpu/drm/virtio/Kconfig" 392 393source "drivers/gpu/drm/msm/Kconfig" 394 395source "drivers/gpu/drm/fsl-dcu/Kconfig" 396 397source "drivers/gpu/drm/tegra/Kconfig" 398 399source "drivers/gpu/drm/stm/Kconfig" 400 401source "drivers/gpu/drm/panel/Kconfig" 402 403source "drivers/gpu/drm/bridge/Kconfig" 404 405source "drivers/gpu/drm/sti/Kconfig" 406 407source "drivers/gpu/drm/imx/Kconfig" 408 409source "drivers/gpu/drm/ingenic/Kconfig" 410 411source "drivers/gpu/drm/v3d/Kconfig" 412 413source "drivers/gpu/drm/vc4/Kconfig" 414 415source "drivers/gpu/drm/loongson/Kconfig" 416 417source "drivers/gpu/drm/etnaviv/Kconfig" 418 419source "drivers/gpu/drm/hisilicon/Kconfig" 420 421source "drivers/gpu/drm/logicvc/Kconfig" 422 423source "drivers/gpu/drm/mediatek/Kconfig" 424 425source "drivers/gpu/drm/mxsfb/Kconfig" 426 427source "drivers/gpu/drm/meson/Kconfig" 428 429source "drivers/gpu/drm/tiny/Kconfig" 430 431source "drivers/gpu/drm/pl111/Kconfig" 432 433source "drivers/gpu/drm/tve200/Kconfig" 434 435source "drivers/gpu/drm/xen/Kconfig" 436 437source "drivers/gpu/drm/vboxvideo/Kconfig" 438 439source "drivers/gpu/drm/lima/Kconfig" 440 441source "drivers/gpu/drm/panfrost/Kconfig" 442 443source "drivers/gpu/drm/panthor/Kconfig" 444 445source "drivers/gpu/drm/aspeed/Kconfig" 446 447source "drivers/gpu/drm/mcde/Kconfig" 448 449source "drivers/gpu/drm/tidss/Kconfig" 450 451source "drivers/gpu/drm/adp/Kconfig" 452 453source "drivers/gpu/drm/xlnx/Kconfig" 454 455source "drivers/gpu/drm/gud/Kconfig" 456 457source "drivers/gpu/drm/solomon/Kconfig" 458 459source "drivers/gpu/drm/sprd/Kconfig" 460 461source "drivers/gpu/drm/imagination/Kconfig" 462 463config DRM_HYPERV 464 tristate "DRM Support for Hyper-V synthetic video device" 465 depends on DRM && PCI && MMU && HYPERV 466 select DRM_CLIENT_SELECTION 467 select DRM_KMS_HELPER 468 select DRM_GEM_SHMEM_HELPER 469 help 470 This is a KMS driver for Hyper-V synthetic video device. Choose this 471 option if you would like to enable drm driver for Hyper-V virtual 472 machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so 473 that DRM driver is used by default. 474 475 If M is selected the module will be called hyperv_drm. 476 477config DRM_EXPORT_FOR_TESTS 478 bool 479 480# Separate option as not all DRM drivers use it 481config DRM_PANEL_BACKLIGHT_QUIRKS 482 tristate 483 484config DRM_LIB_RANDOM 485 bool 486 default n 487 488config DRM_PRIVACY_SCREEN 489 bool 490 default n 491 492config DRM_WERROR 493 bool "Compile the drm subsystem with warnings as errors" 494 depends on DRM && EXPERT 495 depends on !WERROR 496 default n 497 help 498 A kernel build should not cause any compiler warnings, and this 499 enables the '-Werror' flag to enforce that rule in the drm subsystem. 500 501 The drm subsystem enables more warnings than the kernel default, so 502 this config option is disabled by default. 503 504 If in doubt, say N. 505 506config DRM_HEADER_TEST 507 bool "Ensure DRM headers are self-contained and pass kernel-doc" 508 depends on DRM && EXPERT && BROKEN 509 default n 510 help 511 Ensure the DRM subsystem headers both under drivers/gpu/drm and 512 include/drm compile, are self-contained, have header guards, and have 513 no kernel-doc warnings. 514 515 If in doubt, say N. 516 517endif 518 519# Separate option because drm_panel_orientation_quirks.c is shared with fbdev 520config DRM_PANEL_ORIENTATION_QUIRKS 521 tristate 522