Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
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 DRM_KMS_HELPER if DRM_FBDEV_EMULATION
13 select FB_CORE if DRM_FBDEV_EMULATION
14 select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION
15 select HDMI
16 select I2C
17 select DMA_SHARED_BUFFER
18 select SYNC_FILE
19# gallium uses SYS_kcmp for os_same_file_description() to de-duplicate
20# device and dmabuf fd. Let's make sure that is available for our userspace.
21 select KCMP
22 select VIDEO_CMDLINE
23 select VIDEO_NOMODESET
24 help
25 Kernel-level support for the Direct Rendering Infrastructure (DRI)
26 introduced in XFree86 4.0. If you say Y here, you need to select
27 the module that's right for your graphics card from the list below.
28 These modules provide support for synchronization, security, and
29 DMA transfers. Please see <http://dri.sourceforge.net/> for more
30 details. You should also select and configure AGP
31 (/dev/agpgart) support if it is available for your platform.
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=y
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 help
73 KUnit Helpers for KMS drivers.
74
75config DRM_KUNIT_TEST
76 tristate "KUnit tests for DRM" if !KUNIT_ALL_TESTS
77 depends on DRM && KUNIT
78 select PRIME_NUMBERS
79 select DRM_DISPLAY_DP_HELPER
80 select DRM_DISPLAY_HELPER
81 select DRM_LIB_RANDOM
82 select DRM_KMS_HELPER
83 select DRM_BUDDY
84 select DRM_EXPORT_FOR_TESTS if m
85 select DRM_KUNIT_TEST_HELPERS
86 select DRM_EXEC
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_DEBUG_DP_MST_TOPOLOGY_REFS
106 bool "Enable refcount backtrace history in the DP MST helpers"
107 depends on STACKTRACE_SUPPORT
108 select STACKDEPOT
109 depends on DRM_KMS_HELPER
110 depends on DEBUG_KERNEL
111 depends on EXPERT
112 help
113 Enables debug tracing for topology refs in DRM's DP MST helpers. A
114 history of each topology reference/dereference will be printed to the
115 kernel log once a port or branch device's topology refcount reaches 0.
116
117 This has the potential to use a lot of memory and print some very
118 large kernel messages. If in doubt, say "N".
119
120config DRM_DEBUG_MODESET_LOCK
121 bool "Enable backtrace history for lock contention"
122 depends on STACKTRACE_SUPPORT
123 depends on DEBUG_KERNEL
124 depends on EXPERT
125 select STACKDEPOT
126 default y if DEBUG_WW_MUTEX_SLOWPATH
127 help
128 Enable debug tracing of failures to gracefully handle drm modeset lock
129 contention. A history of each drm modeset lock path hitting -EDEADLK
130 will be saved until gracefully handled, and the backtrace will be
131 printed when attempting to lock a contended lock.
132
133 If in doubt, say "N".
134
135config DRM_FBDEV_EMULATION
136 bool "Enable legacy fbdev support for your modesetting driver"
137 depends on DRM
138 select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
139 default FB
140 help
141 Choose this option if you have a need for the legacy fbdev
142 support. Note that this support also provides the linux console
143 support on top of your modesetting driver.
144
145 If in doubt, say "Y".
146
147config DRM_FBDEV_OVERALLOC
148 int "Overallocation of the fbdev buffer"
149 depends on DRM_FBDEV_EMULATION
150 default 100
151 help
152 Defines the fbdev buffer overallocation in percent. Default
153 is 100. Typical values for double buffering will be 200,
154 triple buffering 300.
155
156config DRM_FBDEV_LEAK_PHYS_SMEM
157 bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)"
158 depends on DRM_FBDEV_EMULATION && EXPERT
159 default n
160 help
161 In order to keep user-space compatibility, we want in certain
162 use-cases to keep leaking the fbdev physical address to the
163 user-space program handling the fbdev buffer.
164 This affects, not only, Amlogic, Allwinner or Rockchip devices
165 with ARM Mali GPUs using an userspace Blob.
166 This option is not supported by upstream developers and should be
167 removed as soon as possible and be considered as a broken and
168 legacy behaviour from a modern fbdev device driver.
169
170 Please send any bug reports when using this to your proprietary
171 software vendor that requires this.
172
173 If in doubt, say "N" or spread the word to your closed source
174 library vendor.
175
176config DRM_LOAD_EDID_FIRMWARE
177 bool "Allow to specify an EDID data set instead of probing for it"
178 depends on DRM
179 help
180 Say Y here, if you want to use EDID data to be loaded from the
181 /lib/firmware directory or one of the provided built-in
182 data sets. This may be necessary, if the graphics adapter or
183 monitor are unable to provide appropriate EDID data. Since this
184 feature is provided as a workaround for broken hardware, the
185 default case is N. Details and instructions how to build your own
186 EDID data are given in Documentation/admin-guide/edid.rst.
187
188source "drivers/gpu/drm/display/Kconfig"
189
190config DRM_TTM
191 tristate
192 depends on DRM && MMU
193 help
194 GPU memory management subsystem for devices with multiple
195 GPU memory types. Will be enabled automatically if a device driver
196 uses it.
197
198config DRM_TTM_KUNIT_TEST
199 tristate "KUnit tests for TTM" if !KUNIT_ALL_TESTS
200 default n
201 depends on DRM && KUNIT && MMU
202 select DRM_TTM
203 select DRM_EXPORT_FOR_TESTS if m
204 select DRM_KUNIT_TEST_HELPERS
205 default KUNIT_ALL_TESTS
206 help
207 Enables unit tests for TTM, a GPU memory manager subsystem used
208 to manage memory buffers. This option is mostly useful for kernel
209 developers.
210
211 If in doubt, say "N".
212
213config DRM_EXEC
214 tristate
215 depends on DRM
216 help
217 Execution context for command submissions
218
219config DRM_GPUVM
220 tristate
221 depends on DRM
222 help
223 GPU-VM representation providing helpers to manage a GPUs virtual
224 address space
225
226config DRM_BUDDY
227 tristate
228 depends on DRM
229 help
230 A page based buddy allocator
231
232config DRM_VRAM_HELPER
233 tristate
234 depends on DRM
235 help
236 Helpers for VRAM memory management
237
238config DRM_TTM_HELPER
239 tristate
240 depends on DRM
241 select DRM_TTM
242 help
243 Helpers for ttm-based gem objects
244
245config DRM_GEM_DMA_HELPER
246 tristate
247 depends on DRM
248 select FB_DMAMEM_HELPERS if DRM_FBDEV_EMULATION
249 help
250 Choose this if you need the GEM DMA helper functions
251
252config DRM_GEM_SHMEM_HELPER
253 tristate
254 depends on DRM && MMU
255 help
256 Choose this if you need the GEM shmem helper functions
257
258config DRM_SUBALLOC_HELPER
259 tristate
260 depends on DRM
261
262config DRM_SCHED
263 tristate
264 depends on DRM
265
266source "drivers/gpu/drm/i2c/Kconfig"
267
268source "drivers/gpu/drm/arm/Kconfig"
269
270source "drivers/gpu/drm/radeon/Kconfig"
271
272source "drivers/gpu/drm/amd/amdgpu/Kconfig"
273
274source "drivers/gpu/drm/nouveau/Kconfig"
275
276source "drivers/gpu/drm/i915/Kconfig"
277
278source "drivers/gpu/drm/kmb/Kconfig"
279
280config DRM_VGEM
281 tristate "Virtual GEM provider"
282 depends on DRM && MMU
283 select DRM_GEM_SHMEM_HELPER
284 help
285 Choose this option to get a virtual graphics memory manager,
286 as used by Mesa's software renderer for enhanced performance.
287 If M is selected the module will be called vgem.
288
289config DRM_VKMS
290 tristate "Virtual KMS (EXPERIMENTAL)"
291 depends on DRM && MMU
292 select DRM_KMS_HELPER
293 select DRM_GEM_SHMEM_HELPER
294 select CRC32
295 default n
296 help
297 Virtual Kernel Mode-Setting (VKMS) is used for testing or for
298 running GPU in a headless machines. Choose this option to get
299 a VKMS.
300
301 If M is selected the module will be called vkms.
302
303source "drivers/gpu/drm/exynos/Kconfig"
304
305source "drivers/gpu/drm/rockchip/Kconfig"
306
307source "drivers/gpu/drm/vmwgfx/Kconfig"
308
309source "drivers/gpu/drm/gma500/Kconfig"
310
311source "drivers/gpu/drm/udl/Kconfig"
312
313source "drivers/gpu/drm/ast/Kconfig"
314
315source "drivers/gpu/drm/mgag200/Kconfig"
316
317source "drivers/gpu/drm/armada/Kconfig"
318
319source "drivers/gpu/drm/atmel-hlcdc/Kconfig"
320
321source "drivers/gpu/drm/renesas/Kconfig"
322
323source "drivers/gpu/drm/sun4i/Kconfig"
324
325source "drivers/gpu/drm/omapdrm/Kconfig"
326
327source "drivers/gpu/drm/tilcdc/Kconfig"
328
329source "drivers/gpu/drm/qxl/Kconfig"
330
331source "drivers/gpu/drm/virtio/Kconfig"
332
333source "drivers/gpu/drm/msm/Kconfig"
334
335source "drivers/gpu/drm/fsl-dcu/Kconfig"
336
337source "drivers/gpu/drm/tegra/Kconfig"
338
339source "drivers/gpu/drm/stm/Kconfig"
340
341source "drivers/gpu/drm/panel/Kconfig"
342
343source "drivers/gpu/drm/bridge/Kconfig"
344
345source "drivers/gpu/drm/sti/Kconfig"
346
347source "drivers/gpu/drm/imx/Kconfig"
348
349source "drivers/gpu/drm/ingenic/Kconfig"
350
351source "drivers/gpu/drm/v3d/Kconfig"
352
353source "drivers/gpu/drm/vc4/Kconfig"
354
355source "drivers/gpu/drm/loongson/Kconfig"
356
357source "drivers/gpu/drm/etnaviv/Kconfig"
358
359source "drivers/gpu/drm/hisilicon/Kconfig"
360
361source "drivers/gpu/drm/logicvc/Kconfig"
362
363source "drivers/gpu/drm/mediatek/Kconfig"
364
365source "drivers/gpu/drm/mxsfb/Kconfig"
366
367source "drivers/gpu/drm/meson/Kconfig"
368
369source "drivers/gpu/drm/tiny/Kconfig"
370
371source "drivers/gpu/drm/pl111/Kconfig"
372
373source "drivers/gpu/drm/tve200/Kconfig"
374
375source "drivers/gpu/drm/xen/Kconfig"
376
377source "drivers/gpu/drm/vboxvideo/Kconfig"
378
379source "drivers/gpu/drm/lima/Kconfig"
380
381source "drivers/gpu/drm/panfrost/Kconfig"
382
383source "drivers/gpu/drm/aspeed/Kconfig"
384
385source "drivers/gpu/drm/mcde/Kconfig"
386
387source "drivers/gpu/drm/tidss/Kconfig"
388
389source "drivers/gpu/drm/xlnx/Kconfig"
390
391source "drivers/gpu/drm/gud/Kconfig"
392
393source "drivers/gpu/drm/solomon/Kconfig"
394
395source "drivers/gpu/drm/sprd/Kconfig"
396
397config DRM_HYPERV
398 tristate "DRM Support for Hyper-V synthetic video device"
399 depends on DRM && PCI && MMU && HYPERV
400 select DRM_KMS_HELPER
401 select DRM_GEM_SHMEM_HELPER
402 help
403 This is a KMS driver for Hyper-V synthetic video device. Choose this
404 option if you would like to enable drm driver for Hyper-V virtual
405 machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so
406 that DRM driver is used by default.
407
408 If M is selected the module will be called hyperv_drm.
409
410# Keep legacy drivers last
411
412menuconfig DRM_LEGACY
413 bool "Enable legacy drivers (DANGEROUS)"
414 depends on DRM && MMU
415 help
416 Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous
417 APIs to user-space, which can be used to circumvent access
418 restrictions and other security measures. For backwards compatibility
419 those drivers are still available, but their use is highly
420 inadvisable and might harm your system.
421
422 You are recommended to use the safe modeset-only drivers instead, and
423 perform 3D emulation in user-space.
424
425 Unless you have strong reasons to go rogue, say "N".
426
427if DRM_LEGACY
428# leave here to list legacy drivers
429endif # DRM_LEGACY
430
431config DRM_EXPORT_FOR_TESTS
432 bool
433
434# Separate option because drm_panel_orientation_quirks.c is shared with fbdev
435config DRM_PANEL_ORIENTATION_QUIRKS
436 tristate
437
438config DRM_LIB_RANDOM
439 bool
440 default n
441
442config DRM_PRIVACY_SCREEN
443 bool
444 default n