515 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2#3# Drm device configuration4#5# This driver provides support for the6# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.7#8menuconfig DRM9 tristate "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)"10 depends on (AGP || AGP=n) && !EMULATED_CMPXCHG && HAS_DMA11 select DRM_PANEL_ORIENTATION_QUIRKS12 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION13 select FB_CORE if DRM_FBDEV_EMULATION14 select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION15 select HDMI16 select I2C17 select DMA_SHARED_BUFFER18 select SYNC_FILE19# gallium uses SYS_kcmp for os_same_file_description() to de-duplicate20# device and dmabuf fd. Let's make sure that is available for our userspace.21 select KCMP22 select VIDEO23 help24 Kernel-level support for the Direct Rendering Infrastructure (DRI)25 introduced in XFree86 4.0. If you say Y here, you need to select26 the module that's right for your graphics card from the list below.27 These modules provide support for synchronization, security, and28 DMA transfers. Please see <http://dri.sourceforge.net/> for more29 details. You should also select and configure AGP30 (/dev/agpgart) support if it is available for your platform.31 32if DRM33 34config DRM_MIPI_DBI35 tristate36 depends on DRM37 select DRM_KMS_HELPER38 39config DRM_MIPI_DSI40 bool41 depends on DRM42 43config DRM_DEBUG_MM44 bool "Insert extra checks and debug info into the DRM range managers"45 default n46 depends on DRM47 depends on STACKTRACE_SUPPORT48 select STACKDEPOT49 help50 Enable allocation tracking of memory manager and leak detection on51 shutdown.52 53 Recommended for driver developers only.54 55 If in doubt, say "N".56 57config DRM_USE_DYNAMIC_DEBUG58 bool "use dynamic debug to implement drm.debug"59 default n60 depends on BROKEN61 depends on DRM62 depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE63 depends on JUMP_LABEL64 help65 Use dynamic-debug to avoid drm_debug_enabled() runtime overheads.66 Due to callsite counts in DRM drivers (~4k in amdgpu) and 5667 bytes per callsite, the .data costs can be substantial, and68 are therefore configurable.69 70config DRM_KUNIT_TEST_HELPERS71 tristate72 depends on DRM && KUNIT73 select DRM_KMS_HELPER74 help75 KUnit Helpers for KMS drivers.76 77config DRM_KUNIT_TEST78 tristate "KUnit tests for DRM" if !KUNIT_ALL_TESTS79 depends on DRM && KUNIT && MMU80 select DRM_BUDDY81 select DRM_DISPLAY_DP_HELPER82 select DRM_DISPLAY_HDMI_STATE_HELPER83 select DRM_DISPLAY_HELPER84 select DRM_EXEC85 select DRM_EXPORT_FOR_TESTS if m86 select DRM_GEM_SHMEM_HELPER87 select DRM_KUNIT_TEST_HELPERS88 select DRM_LIB_RANDOM89 select PRIME_NUMBERS90 default KUNIT_ALL_TESTS91 help92 This builds unit tests for DRM. This option is not useful for93 distributions or general kernels, but only for kernel94 developers working on DRM and associated drivers.95 96 For more information on KUnit and unit tests in general,97 please refer to the KUnit documentation in98 Documentation/dev-tools/kunit/.99 100 If in doubt, say "N".101 102config DRM_KMS_HELPER103 tristate104 depends on DRM105 help106 CRTC helpers for KMS drivers.107 108config DRM_PANIC109 bool "Display a user-friendly message when a kernel panic occurs"110 depends on DRM111 select FONT_SUPPORT112 help113 Enable a drm panic handler, which will display a user-friendly message114 when a kernel panic occurs. It's useful when using a user-space115 console instead of fbcon.116 It will only work if your graphic driver supports this feature.117 To support Hi-DPI Display, you can enable bigger fonts like118 FONT_TER16x32119 120config DRM_PANIC_FOREGROUND_COLOR121 hex "Drm panic screen foreground color, in RGB"122 depends on DRM_PANIC123 default 0xffffff124 125config DRM_PANIC_BACKGROUND_COLOR126 hex "Drm panic screen background color, in RGB"127 depends on DRM_PANIC128 default 0x000000129 130config DRM_PANIC_DEBUG131 bool "Add a debug fs entry to trigger drm_panic"132 depends on DRM_PANIC && DEBUG_FS133 help134 Add dri/[device]/drm_panic_plane_x in the kernel debugfs, to force the135 panic handler to write the panic message to this plane scanout buffer.136 This is unsafe and should not be enabled on a production build.137 If in doubt, say "N".138 139config DRM_PANIC_SCREEN140 string "Panic screen formatter"141 default "user"142 depends on DRM_PANIC143 help144 This option enable to choose what will be displayed when a kernel145 panic occurs. You can choose between "user", a short message telling146 the user to reboot the system, or "kmsg" which will display the last147 lines of kmsg.148 This can also be overridden by drm.panic_screen=xxxx kernel parameter149 or by writing to /sys/module/drm/parameters/panic_screen sysfs entry150 Default is "user"151 152config DRM_PANIC_SCREEN_QR_CODE153 bool "Add a panic screen with a QR code"154 depends on DRM_PANIC && RUST155 help156 This option adds a QR code generator, and a panic screen with a QR157 code. The QR code will contain the last lines of kmsg and other debug158 information. This should be easier for the user to report a kernel159 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_URL163 string "Base URL of the QR code in the panic screen"164 depends on DRM_PANIC_SCREEN_QR_CODE165 help166 This option sets the base URL to report the kernel panic. If it's set167 the QR code will contain the URL and the kmsg compressed with zlib as168 a URL parameter. If it's empty, the QR code will contain the kmsg as169 uncompressed text only.170 There is a demo code in javascript, to decode and uncompress the kmsg171 data from the URL parameter at https://github.com/kdj0c/panic_report172 173config DRM_PANIC_SCREEN_QR_VERSION174 int "Maximum version (size) of the QR code."175 depends on DRM_PANIC_SCREEN_QR_CODE176 default 40177 help178 This option limits the version (or size) of the QR code. QR code179 version ranges from Version 1 (21x21) to Version 40 (177x177).180 Smaller QR code are easier to read, but will contain less debugging181 data. Default is 40.182 183config DRM_DEBUG_DP_MST_TOPOLOGY_REFS184 bool "Enable refcount backtrace history in the DP MST helpers"185 depends on STACKTRACE_SUPPORT186 select STACKDEPOT187 depends on DRM_KMS_HELPER188 depends on DEBUG_KERNEL189 depends on EXPERT190 help191 Enables debug tracing for topology refs in DRM's DP MST helpers. A192 history of each topology reference/dereference will be printed to the193 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 very196 large kernel messages. If in doubt, say "N".197 198config DRM_DEBUG_MODESET_LOCK199 bool "Enable backtrace history for lock contention"200 depends on STACKTRACE_SUPPORT201 depends on DEBUG_KERNEL202 depends on EXPERT203 select STACKDEPOT204 default y if DEBUG_WW_MUTEX_SLOWPATH205 help206 Enable debug tracing of failures to gracefully handle drm modeset lock207 contention. A history of each drm modeset lock path hitting -EDEADLK208 will be saved until gracefully handled, and the backtrace will be209 printed when attempting to lock a contended lock.210 211 If in doubt, say "N".212 213config DRM_FBDEV_EMULATION214 bool "Enable legacy fbdev support for your modesetting driver"215 depends on DRM216 select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE217 default FB218 help219 Choose this option if you have a need for the legacy fbdev220 support. Note that this support also provides the linux console221 support on top of your modesetting driver.222 223 If in doubt, say "Y".224 225config DRM_FBDEV_OVERALLOC226 int "Overallocation of the fbdev buffer"227 depends on DRM_FBDEV_EMULATION228 default 100229 help230 Defines the fbdev buffer overallocation in percent. Default231 is 100. Typical values for double buffering will be 200,232 triple buffering 300.233 234config DRM_FBDEV_LEAK_PHYS_SMEM235 bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)"236 depends on DRM_FBDEV_EMULATION && EXPERT237 default n238 help239 In order to keep user-space compatibility, we want in certain240 use-cases to keep leaking the fbdev physical address to the241 user-space program handling the fbdev buffer.242 This affects, not only, Amlogic, Allwinner or Rockchip devices243 with ARM Mali GPUs using an userspace Blob.244 This option is not supported by upstream developers and should be245 removed as soon as possible and be considered as a broken and246 legacy behaviour from a modern fbdev device driver.247 248 Please send any bug reports when using this to your proprietary249 software vendor that requires this.250 251 If in doubt, say "N" or spread the word to your closed source252 library vendor.253 254config DRM_LOAD_EDID_FIRMWARE255 bool "Allow to specify an EDID data set instead of probing for it"256 depends on DRM257 help258 Say Y here, if you want to use EDID data to be loaded from the259 /lib/firmware directory or one of the provided built-in260 data sets. This may be necessary, if the graphics adapter or261 monitor are unable to provide appropriate EDID data. Since this262 feature is provided as a workaround for broken hardware, the263 default case is N. Details and instructions how to build your own264 EDID data are given in Documentation/admin-guide/edid.rst.265 266source "drivers/gpu/drm/display/Kconfig"267 268config DRM_TTM269 tristate270 depends on DRM && MMU271 help272 GPU memory management subsystem for devices with multiple273 GPU memory types. Will be enabled automatically if a device driver274 uses it.275 276config DRM_TTM_KUNIT_TEST277 tristate "KUnit tests for TTM" if !KUNIT_ALL_TESTS278 default n279 depends on DRM && KUNIT && MMU && (UML || COMPILE_TEST)280 select DRM_TTM281 select DRM_BUDDY282 select DRM_EXPORT_FOR_TESTS if m283 select DRM_KUNIT_TEST_HELPERS284 default KUNIT_ALL_TESTS285 help286 Enables unit tests for TTM, a GPU memory manager subsystem used287 to manage memory buffers. This option is mostly useful for kernel288 developers. It depends on (UML || COMPILE_TEST) since no other driver289 which uses TTM can be loaded while running the tests.290 291 If in doubt, say "N".292 293config DRM_EXEC294 tristate295 depends on DRM296 help297 Execution context for command submissions298 299config DRM_GPUVM300 tristate301 depends on DRM302 select DRM_EXEC303 help304 GPU-VM representation providing helpers to manage a GPUs virtual305 address space306 307config DRM_BUDDY308 tristate309 depends on DRM310 help311 A page based buddy allocator312 313config DRM_VRAM_HELPER314 tristate315 depends on DRM316 help317 Helpers for VRAM memory management318 319config DRM_TTM_HELPER320 tristate321 depends on DRM322 select DRM_TTM323 help324 Helpers for ttm-based gem objects325 326config DRM_GEM_DMA_HELPER327 tristate328 depends on DRM329 select FB_DMAMEM_HELPERS if DRM_FBDEV_EMULATION330 help331 Choose this if you need the GEM DMA helper functions332 333config DRM_GEM_SHMEM_HELPER334 tristate335 depends on DRM && MMU336 help337 Choose this if you need the GEM shmem helper functions338 339config DRM_SUBALLOC_HELPER340 tristate341 depends on DRM342 343config DRM_SCHED344 tristate345 depends on DRM346 347source "drivers/gpu/drm/i2c/Kconfig"348 349source "drivers/gpu/drm/arm/Kconfig"350 351source "drivers/gpu/drm/radeon/Kconfig"352 353source "drivers/gpu/drm/amd/amdgpu/Kconfig"354 355source "drivers/gpu/drm/nouveau/Kconfig"356 357source "drivers/gpu/drm/i915/Kconfig"358 359source "drivers/gpu/drm/xe/Kconfig"360 361source "drivers/gpu/drm/kmb/Kconfig"362 363config DRM_VGEM364 tristate "Virtual GEM provider"365 depends on DRM && MMU366 select DRM_GEM_SHMEM_HELPER367 help368 Choose this option to get a virtual graphics memory manager,369 as used by Mesa's software renderer for enhanced performance.370 If M is selected the module will be called vgem.371 372source "drivers/gpu/drm/vkms/Kconfig"373 374source "drivers/gpu/drm/exynos/Kconfig"375 376source "drivers/gpu/drm/rockchip/Kconfig"377 378source "drivers/gpu/drm/vmwgfx/Kconfig"379 380source "drivers/gpu/drm/gma500/Kconfig"381 382source "drivers/gpu/drm/udl/Kconfig"383 384source "drivers/gpu/drm/ast/Kconfig"385 386source "drivers/gpu/drm/mgag200/Kconfig"387 388source "drivers/gpu/drm/armada/Kconfig"389 390source "drivers/gpu/drm/atmel-hlcdc/Kconfig"391 392source "drivers/gpu/drm/renesas/Kconfig"393 394source "drivers/gpu/drm/sun4i/Kconfig"395 396source "drivers/gpu/drm/omapdrm/Kconfig"397 398source "drivers/gpu/drm/tilcdc/Kconfig"399 400source "drivers/gpu/drm/qxl/Kconfig"401 402source "drivers/gpu/drm/virtio/Kconfig"403 404source "drivers/gpu/drm/msm/Kconfig"405 406source "drivers/gpu/drm/fsl-dcu/Kconfig"407 408source "drivers/gpu/drm/tegra/Kconfig"409 410source "drivers/gpu/drm/stm/Kconfig"411 412source "drivers/gpu/drm/panel/Kconfig"413 414source "drivers/gpu/drm/bridge/Kconfig"415 416source "drivers/gpu/drm/sti/Kconfig"417 418source "drivers/gpu/drm/imx/Kconfig"419 420source "drivers/gpu/drm/ingenic/Kconfig"421 422source "drivers/gpu/drm/v3d/Kconfig"423 424source "drivers/gpu/drm/vc4/Kconfig"425 426source "drivers/gpu/drm/loongson/Kconfig"427 428source "drivers/gpu/drm/etnaviv/Kconfig"429 430source "drivers/gpu/drm/hisilicon/Kconfig"431 432source "drivers/gpu/drm/logicvc/Kconfig"433 434source "drivers/gpu/drm/mediatek/Kconfig"435 436source "drivers/gpu/drm/mxsfb/Kconfig"437 438source "drivers/gpu/drm/meson/Kconfig"439 440source "drivers/gpu/drm/tiny/Kconfig"441 442source "drivers/gpu/drm/pl111/Kconfig"443 444source "drivers/gpu/drm/tve200/Kconfig"445 446source "drivers/gpu/drm/xen/Kconfig"447 448source "drivers/gpu/drm/vboxvideo/Kconfig"449 450source "drivers/gpu/drm/lima/Kconfig"451 452source "drivers/gpu/drm/panfrost/Kconfig"453 454source "drivers/gpu/drm/panthor/Kconfig"455 456source "drivers/gpu/drm/aspeed/Kconfig"457 458source "drivers/gpu/drm/mcde/Kconfig"459 460source "drivers/gpu/drm/tidss/Kconfig"461 462source "drivers/gpu/drm/xlnx/Kconfig"463 464source "drivers/gpu/drm/gud/Kconfig"465 466source "drivers/gpu/drm/solomon/Kconfig"467 468source "drivers/gpu/drm/sprd/Kconfig"469 470source "drivers/gpu/drm/imagination/Kconfig"471 472config DRM_HYPERV473 tristate "DRM Support for Hyper-V synthetic video device"474 depends on DRM && PCI && MMU && HYPERV475 select DRM_KMS_HELPER476 select DRM_GEM_SHMEM_HELPER477 help478 This is a KMS driver for Hyper-V synthetic video device. Choose this479 option if you would like to enable drm driver for Hyper-V virtual480 machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so481 that DRM driver is used by default.482 483 If M is selected the module will be called hyperv_drm.484 485config DRM_EXPORT_FOR_TESTS486 bool487 488config DRM_LIB_RANDOM489 bool490 default n491 492config DRM_PRIVACY_SCREEN493 bool494 default n495 496config DRM_WERROR497 bool "Compile the drm subsystem with warnings as errors"498 depends on DRM && EXPERT499 depends on !WERROR500 default n501 help502 A kernel build should not cause any compiler warnings, and this503 enables the '-Werror' flag to enforce that rule in the drm subsystem.504 505 The drm subsystem enables more warnings than the kernel default, so506 this config option is disabled by default.507 508 If in doubt, say N.509 510endif511 512# Separate option because drm_panel_orientation_quirks.c is shared with fbdev513config DRM_PANEL_ORIENTATION_QUIRKS514 tristate515