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