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 help 103 CRTC helpers for KMS drivers. 104 105config DRM_PANIC 106 bool "Display a user-friendly message when a kernel panic occurs" 107 depends on DRM 108 select FONT_SUPPORT 109 help 110 Enable a drm panic handler, which will display a user-friendly message 111 when a kernel panic occurs. It's useful when using a user-space 112 console instead of fbcon. 113 It will only work if your graphic driver supports this feature. 114 To support Hi-DPI Display, you can enable bigger fonts like 115 FONT_TER16x32 116 117config DRM_PANIC_FOREGROUND_COLOR 118 hex "Drm panic screen foreground color, in RGB" 119 depends on DRM_PANIC 120 default 0xffffff 121 122config DRM_PANIC_BACKGROUND_COLOR 123 hex "Drm panic screen background color, in RGB" 124 depends on DRM_PANIC 125 default 0x000000 126 127config DRM_PANIC_DEBUG 128 bool "Add a debug fs entry to trigger drm_panic" 129 depends on DRM_PANIC && DEBUG_FS 130 help 131 Add dri/[device]/drm_panic_plane_x in the kernel debugfs, to force the 132 panic handler to write the panic message to this plane scanout buffer. 133 This is unsafe and should not be enabled on a production build. 134 If in doubt, say "N". 135 136config DRM_PANIC_SCREEN 137 string "Panic screen formatter" 138 default "user" 139 depends on DRM_PANIC 140 help 141 This option enable to choose what will be displayed when a kernel 142 panic occurs. You can choose between "user", a short message telling 143 the user to reboot the system, or "kmsg" which will display the last 144 lines of kmsg. 145 This can also be overridden by drm.panic_screen=xxxx kernel parameter 146 or by writing to /sys/module/drm/parameters/panic_screen sysfs entry 147 Default is "user" 148 149config DRM_PANIC_SCREEN_QR_CODE 150 bool "Add a panic screen with a QR code" 151 depends on DRM_PANIC && RUST 152 select ZLIB_DEFLATE 153 help 154 This option adds a QR code generator, and a panic screen with a QR 155 code. The QR code will contain the last lines of kmsg and other debug 156 information. This should be easier for the user to report a kernel 157 panic, with all debug information available. 158 To use this panic screen, also set DRM_PANIC_SCREEN to "qr_code" 159 160config DRM_PANIC_SCREEN_QR_CODE_URL 161 string "Base URL of the QR code in the panic screen" 162 depends on DRM_PANIC_SCREEN_QR_CODE 163 help 164 This option sets the base URL to report the kernel panic. If it's set 165 the QR code will contain the URL and the kmsg compressed with zlib as 166 a URL parameter. If it's empty, the QR code will contain the kmsg as 167 uncompressed text only. 168 There is a demo code in javascript, to decode and uncompress the kmsg 169 data from the URL parameter at https://github.com/kdj0c/panic_report 170 171config DRM_PANIC_SCREEN_QR_VERSION 172 int "Maximum version (size) of the QR code." 173 depends on DRM_PANIC_SCREEN_QR_CODE 174 default 40 175 help 176 This option limits the version (or size) of the QR code. QR code 177 version ranges from Version 1 (21x21) to Version 40 (177x177). 178 Smaller QR code are easier to read, but will contain less debugging 179 data. Default is 40. 180 181config DRM_DEBUG_DP_MST_TOPOLOGY_REFS 182 bool "Enable refcount backtrace history in the DP MST helpers" 183 depends on STACKTRACE_SUPPORT 184 select STACKDEPOT 185 depends on DRM_KMS_HELPER 186 depends on DEBUG_KERNEL 187 depends on EXPERT 188 help 189 Enables debug tracing for topology refs in DRM's DP MST helpers. A 190 history of each topology reference/dereference will be printed to the 191 kernel log once a port or branch device's topology refcount reaches 0. 192 193 This has the potential to use a lot of memory and print some very 194 large kernel messages. If in doubt, say "N". 195 196config DRM_DEBUG_MODESET_LOCK 197 bool "Enable backtrace history for lock contention" 198 depends on STACKTRACE_SUPPORT 199 depends on DEBUG_KERNEL 200 depends on EXPERT 201 select STACKDEPOT 202 default y if DEBUG_WW_MUTEX_SLOWPATH 203 help 204 Enable debug tracing of failures to gracefully handle drm modeset lock 205 contention. A history of each drm modeset lock path hitting -EDEADLK 206 will be saved until gracefully handled, and the backtrace will be 207 printed when attempting to lock a contended lock. 208 209 If in doubt, say "N". 210 211config DRM_CLIENT 212 bool 213 depends on DRM 214 help 215 Enables support for DRM clients. DRM drivers that need 216 struct drm_client_dev and its interfaces should select this 217 option. Drivers that support the default clients should 218 select DRM_CLIENT_SELECTION instead. 219 220config DRM_CLIENT_LIB 221 tristate 222 depends on DRM 223 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION 224 select FB_CORE if DRM_FBDEV_EMULATION 225 help 226 This option enables the DRM client library and selects all 227 modules and components according to the enabled clients. 228 229config DRM_CLIENT_SELECTION 230 tristate 231 depends on DRM 232 select DRM_CLIENT_LIB if DRM_FBDEV_EMULATION 233 help 234 Drivers that support in-kernel DRM clients have to select this 235 option. 236 237config DRM_CLIENT_SETUP 238 bool 239 depends on DRM_CLIENT_SELECTION 240 help 241 Enables the DRM client selection. DRM drivers that support the 242 default clients should select DRM_CLIENT_SELECTION instead. 243 244menu "Supported DRM clients" 245 depends on DRM_CLIENT_SELECTION 246 247config DRM_FBDEV_EMULATION 248 bool "Enable legacy fbdev support for your modesetting driver" 249 depends on DRM_CLIENT_SELECTION 250 select DRM_CLIENT 251 select DRM_CLIENT_SETUP 252 select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE 253 default FB 254 help 255 Choose this option if you have a need for the legacy fbdev 256 support. Note that this support also provides the linux console 257 support on top of your modesetting driver. 258 259 If in doubt, say "Y". 260 261config DRM_FBDEV_OVERALLOC 262 int "Overallocation of the fbdev buffer" 263 depends on DRM_FBDEV_EMULATION 264 default 100 265 help 266 Defines the fbdev buffer overallocation in percent. Default 267 is 100. Typical values for double buffering will be 200, 268 triple buffering 300. 269 270config DRM_FBDEV_LEAK_PHYS_SMEM 271 bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)" 272 depends on DRM_FBDEV_EMULATION && EXPERT 273 default n 274 help 275 In order to keep user-space compatibility, we want in certain 276 use-cases to keep leaking the fbdev physical address to the 277 user-space program handling the fbdev buffer. 278 This affects, not only, Amlogic, Allwinner or Rockchip devices 279 with ARM Mali GPUs using an userspace Blob. 280 This option is not supported by upstream developers and should be 281 removed as soon as possible and be considered as a broken and 282 legacy behaviour from a modern fbdev device driver. 283 284 Please send any bug reports when using this to your proprietary 285 software vendor that requires this. 286 287 If in doubt, say "N" or spread the word to your closed source 288 library vendor. 289 290endmenu 291 292config DRM_LOAD_EDID_FIRMWARE 293 bool "Allow to specify an EDID data set instead of probing for it" 294 depends on DRM 295 help 296 Say Y here, if you want to use EDID data to be loaded from the 297 /lib/firmware directory or one of the provided built-in 298 data sets. This may be necessary, if the graphics adapter or 299 monitor are unable to provide appropriate EDID data. Since this 300 feature is provided as a workaround for broken hardware, the 301 default case is N. Details and instructions how to build your own 302 EDID data are given in Documentation/admin-guide/edid.rst. 303 304source "drivers/gpu/drm/display/Kconfig" 305 306config DRM_TTM 307 tristate 308 depends on DRM && MMU 309 help 310 GPU memory management subsystem for devices with multiple 311 GPU memory types. Will be enabled automatically if a device driver 312 uses it. 313 314config DRM_TTM_KUNIT_TEST 315 tristate "KUnit tests for TTM" if !KUNIT_ALL_TESTS 316 default n 317 depends on DRM && KUNIT && MMU && (UML || COMPILE_TEST) 318 select DRM_TTM 319 select DRM_BUDDY 320 select DRM_EXPORT_FOR_TESTS if m 321 select DRM_KUNIT_TEST_HELPERS 322 default KUNIT_ALL_TESTS 323 help 324 Enables unit tests for TTM, a GPU memory manager subsystem used 325 to manage memory buffers. This option is mostly useful for kernel 326 developers. It depends on (UML || COMPILE_TEST) since no other driver 327 which uses TTM can be loaded while running the tests. 328 329 If in doubt, say "N". 330 331config DRM_EXEC 332 tristate 333 depends on DRM 334 help 335 Execution context for command submissions 336 337config DRM_GPUVM 338 tristate 339 depends on DRM 340 select DRM_EXEC 341 help 342 GPU-VM representation providing helpers to manage a GPUs virtual 343 address space 344 345config DRM_BUDDY 346 tristate 347 depends on DRM 348 help 349 A page based buddy allocator 350 351config DRM_VRAM_HELPER 352 tristate 353 depends on DRM 354 help 355 Helpers for VRAM memory management 356 357config DRM_TTM_HELPER 358 tristate 359 depends on DRM 360 select DRM_TTM 361 select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION 362 help 363 Helpers for ttm-based gem objects 364 365config DRM_GEM_DMA_HELPER 366 tristate 367 depends on DRM 368 select FB_DMAMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION 369 help 370 Choose this if you need the GEM DMA helper functions 371 372config DRM_GEM_SHMEM_HELPER 373 tristate 374 depends on DRM && MMU 375 select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION 376 help 377 Choose this if you need the GEM shmem helper functions 378 379config DRM_SUBALLOC_HELPER 380 tristate 381 depends on DRM 382 383config DRM_SCHED 384 tristate 385 depends on DRM 386 387source "drivers/gpu/drm/i2c/Kconfig" 388 389source "drivers/gpu/drm/arm/Kconfig" 390 391source "drivers/gpu/drm/radeon/Kconfig" 392 393source "drivers/gpu/drm/amd/amdgpu/Kconfig" 394 395source "drivers/gpu/drm/nouveau/Kconfig" 396 397source "drivers/gpu/drm/i915/Kconfig" 398 399source "drivers/gpu/drm/xe/Kconfig" 400 401source "drivers/gpu/drm/kmb/Kconfig" 402 403config DRM_VGEM 404 tristate "Virtual GEM provider" 405 depends on DRM && MMU 406 select DRM_GEM_SHMEM_HELPER 407 help 408 Choose this option to get a virtual graphics memory manager, 409 as used by Mesa's software renderer for enhanced performance. 410 If M is selected the module will be called vgem. 411 412source "drivers/gpu/drm/vkms/Kconfig" 413 414source "drivers/gpu/drm/exynos/Kconfig" 415 416source "drivers/gpu/drm/rockchip/Kconfig" 417 418source "drivers/gpu/drm/vmwgfx/Kconfig" 419 420source "drivers/gpu/drm/gma500/Kconfig" 421 422source "drivers/gpu/drm/udl/Kconfig" 423 424source "drivers/gpu/drm/ast/Kconfig" 425 426source "drivers/gpu/drm/mgag200/Kconfig" 427 428source "drivers/gpu/drm/armada/Kconfig" 429 430source "drivers/gpu/drm/atmel-hlcdc/Kconfig" 431 432source "drivers/gpu/drm/renesas/Kconfig" 433 434source "drivers/gpu/drm/sun4i/Kconfig" 435 436source "drivers/gpu/drm/omapdrm/Kconfig" 437 438source "drivers/gpu/drm/tilcdc/Kconfig" 439 440source "drivers/gpu/drm/qxl/Kconfig" 441 442source "drivers/gpu/drm/virtio/Kconfig" 443 444source "drivers/gpu/drm/msm/Kconfig" 445 446source "drivers/gpu/drm/fsl-dcu/Kconfig" 447 448source "drivers/gpu/drm/tegra/Kconfig" 449 450source "drivers/gpu/drm/stm/Kconfig" 451 452source "drivers/gpu/drm/panel/Kconfig" 453 454source "drivers/gpu/drm/bridge/Kconfig" 455 456source "drivers/gpu/drm/sti/Kconfig" 457 458source "drivers/gpu/drm/imx/Kconfig" 459 460source "drivers/gpu/drm/ingenic/Kconfig" 461 462source "drivers/gpu/drm/v3d/Kconfig" 463 464source "drivers/gpu/drm/vc4/Kconfig" 465 466source "drivers/gpu/drm/loongson/Kconfig" 467 468source "drivers/gpu/drm/etnaviv/Kconfig" 469 470source "drivers/gpu/drm/hisilicon/Kconfig" 471 472source "drivers/gpu/drm/logicvc/Kconfig" 473 474source "drivers/gpu/drm/mediatek/Kconfig" 475 476source "drivers/gpu/drm/mxsfb/Kconfig" 477 478source "drivers/gpu/drm/meson/Kconfig" 479 480source "drivers/gpu/drm/tiny/Kconfig" 481 482source "drivers/gpu/drm/pl111/Kconfig" 483 484source "drivers/gpu/drm/tve200/Kconfig" 485 486source "drivers/gpu/drm/xen/Kconfig" 487 488source "drivers/gpu/drm/vboxvideo/Kconfig" 489 490source "drivers/gpu/drm/lima/Kconfig" 491 492source "drivers/gpu/drm/panfrost/Kconfig" 493 494source "drivers/gpu/drm/panthor/Kconfig" 495 496source "drivers/gpu/drm/aspeed/Kconfig" 497 498source "drivers/gpu/drm/mcde/Kconfig" 499 500source "drivers/gpu/drm/tidss/Kconfig" 501 502source "drivers/gpu/drm/xlnx/Kconfig" 503 504source "drivers/gpu/drm/gud/Kconfig" 505 506source "drivers/gpu/drm/solomon/Kconfig" 507 508source "drivers/gpu/drm/sprd/Kconfig" 509 510source "drivers/gpu/drm/imagination/Kconfig" 511 512config DRM_HYPERV 513 tristate "DRM Support for Hyper-V synthetic video device" 514 depends on DRM && PCI && MMU && HYPERV 515 select DRM_CLIENT_SELECTION 516 select DRM_KMS_HELPER 517 select DRM_GEM_SHMEM_HELPER 518 help 519 This is a KMS driver for Hyper-V synthetic video device. Choose this 520 option if you would like to enable drm driver for Hyper-V virtual 521 machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so 522 that DRM driver is used by default. 523 524 If M is selected the module will be called hyperv_drm. 525 526config DRM_EXPORT_FOR_TESTS 527 bool 528 529config DRM_LIB_RANDOM 530 bool 531 default n 532 533config DRM_PRIVACY_SCREEN 534 bool 535 default n 536 537config DRM_WERROR 538 bool "Compile the drm subsystem with warnings as errors" 539 depends on DRM && EXPERT 540 depends on !WERROR 541 default n 542 help 543 A kernel build should not cause any compiler warnings, and this 544 enables the '-Werror' flag to enforce that rule in the drm subsystem. 545 546 The drm subsystem enables more warnings than the kernel default, so 547 this config option is disabled by default. 548 549 If in doubt, say N. 550 551endif 552 553# Separate option because drm_panel_orientation_quirks.c is shared with fbdev 554config DRM_PANEL_ORIENTATION_QUIRKS 555 tristate 556