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