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