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_BUDDY
220	tristate
221	depends on DRM
222	help
223	  A page based buddy allocator
224
225config DRM_VRAM_HELPER
226	tristate
227	depends on DRM
228	help
229	  Helpers for VRAM memory management
230
231config DRM_TTM_HELPER
232	tristate
233	depends on DRM
234	select DRM_TTM
235	help
236	  Helpers for ttm-based gem objects
237
238config DRM_GEM_DMA_HELPER
239	tristate
240	depends on DRM
241	select FB_DMAMEM_HELPERS if DRM_FBDEV_EMULATION
242	help
243	  Choose this if you need the GEM DMA helper functions
244
245config DRM_GEM_SHMEM_HELPER
246	tristate
247	depends on DRM && MMU
248	help
249	  Choose this if you need the GEM shmem helper functions
250
251config DRM_SUBALLOC_HELPER
252	tristate
253	depends on DRM
254
255config DRM_SCHED
256	tristate
257	depends on DRM
258
259source "drivers/gpu/drm/i2c/Kconfig"
260
261source "drivers/gpu/drm/arm/Kconfig"
262
263source "drivers/gpu/drm/radeon/Kconfig"
264
265source "drivers/gpu/drm/amd/amdgpu/Kconfig"
266
267source "drivers/gpu/drm/nouveau/Kconfig"
268
269source "drivers/gpu/drm/i915/Kconfig"
270
271source "drivers/gpu/drm/kmb/Kconfig"
272
273config DRM_VGEM
274	tristate "Virtual GEM provider"
275	depends on DRM && MMU
276	select DRM_GEM_SHMEM_HELPER
277	help
278	  Choose this option to get a virtual graphics memory manager,
279	  as used by Mesa's software renderer for enhanced performance.
280	  If M is selected the module will be called vgem.
281
282config DRM_VKMS
283	tristate "Virtual KMS (EXPERIMENTAL)"
284	depends on DRM && MMU
285	select DRM_KMS_HELPER
286	select DRM_GEM_SHMEM_HELPER
287	select CRC32
288	default n
289	help
290	  Virtual Kernel Mode-Setting (VKMS) is used for testing or for
291	  running GPU in a headless machines. Choose this option to get
292	  a VKMS.
293
294	  If M is selected the module will be called vkms.
295
296source "drivers/gpu/drm/exynos/Kconfig"
297
298source "drivers/gpu/drm/rockchip/Kconfig"
299
300source "drivers/gpu/drm/vmwgfx/Kconfig"
301
302source "drivers/gpu/drm/gma500/Kconfig"
303
304source "drivers/gpu/drm/udl/Kconfig"
305
306source "drivers/gpu/drm/ast/Kconfig"
307
308source "drivers/gpu/drm/mgag200/Kconfig"
309
310source "drivers/gpu/drm/armada/Kconfig"
311
312source "drivers/gpu/drm/atmel-hlcdc/Kconfig"
313
314source "drivers/gpu/drm/renesas/Kconfig"
315
316source "drivers/gpu/drm/sun4i/Kconfig"
317
318source "drivers/gpu/drm/omapdrm/Kconfig"
319
320source "drivers/gpu/drm/tilcdc/Kconfig"
321
322source "drivers/gpu/drm/qxl/Kconfig"
323
324source "drivers/gpu/drm/virtio/Kconfig"
325
326source "drivers/gpu/drm/msm/Kconfig"
327
328source "drivers/gpu/drm/fsl-dcu/Kconfig"
329
330source "drivers/gpu/drm/tegra/Kconfig"
331
332source "drivers/gpu/drm/stm/Kconfig"
333
334source "drivers/gpu/drm/panel/Kconfig"
335
336source "drivers/gpu/drm/bridge/Kconfig"
337
338source "drivers/gpu/drm/sti/Kconfig"
339
340source "drivers/gpu/drm/imx/Kconfig"
341
342source "drivers/gpu/drm/ingenic/Kconfig"
343
344source "drivers/gpu/drm/v3d/Kconfig"
345
346source "drivers/gpu/drm/vc4/Kconfig"
347
348source "drivers/gpu/drm/loongson/Kconfig"
349
350source "drivers/gpu/drm/etnaviv/Kconfig"
351
352source "drivers/gpu/drm/hisilicon/Kconfig"
353
354source "drivers/gpu/drm/logicvc/Kconfig"
355
356source "drivers/gpu/drm/mediatek/Kconfig"
357
358source "drivers/gpu/drm/mxsfb/Kconfig"
359
360source "drivers/gpu/drm/meson/Kconfig"
361
362source "drivers/gpu/drm/tiny/Kconfig"
363
364source "drivers/gpu/drm/pl111/Kconfig"
365
366source "drivers/gpu/drm/tve200/Kconfig"
367
368source "drivers/gpu/drm/xen/Kconfig"
369
370source "drivers/gpu/drm/vboxvideo/Kconfig"
371
372source "drivers/gpu/drm/lima/Kconfig"
373
374source "drivers/gpu/drm/panfrost/Kconfig"
375
376source "drivers/gpu/drm/aspeed/Kconfig"
377
378source "drivers/gpu/drm/mcde/Kconfig"
379
380source "drivers/gpu/drm/tidss/Kconfig"
381
382source "drivers/gpu/drm/xlnx/Kconfig"
383
384source "drivers/gpu/drm/gud/Kconfig"
385
386source "drivers/gpu/drm/solomon/Kconfig"
387
388source "drivers/gpu/drm/sprd/Kconfig"
389
390config DRM_HYPERV
391	tristate "DRM Support for Hyper-V synthetic video device"
392	depends on DRM && PCI && MMU && HYPERV
393	select DRM_KMS_HELPER
394	select DRM_GEM_SHMEM_HELPER
395	help
396	 This is a KMS driver for Hyper-V synthetic video device. Choose this
397	 option if you would like to enable drm driver for Hyper-V virtual
398	 machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so
399	 that DRM driver is used by default.
400
401	 If M is selected the module will be called hyperv_drm.
402
403# Keep legacy drivers last
404
405menuconfig DRM_LEGACY
406	bool "Enable legacy drivers (DANGEROUS)"
407	depends on DRM && MMU
408	help
409	  Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous
410	  APIs to user-space, which can be used to circumvent access
411	  restrictions and other security measures. For backwards compatibility
412	  those drivers are still available, but their use is highly
413	  inadvisable and might harm your system.
414
415	  You are recommended to use the safe modeset-only drivers instead, and
416	  perform 3D emulation in user-space.
417
418	  Unless you have strong reasons to go rogue, say "N".
419
420if DRM_LEGACY
421# leave here to list legacy drivers
422endif # DRM_LEGACY
423
424config DRM_EXPORT_FOR_TESTS
425	bool
426
427# Separate option because drm_panel_orientation_quirks.c is shared with fbdev
428config DRM_PANEL_ORIENTATION_QUIRKS
429	tristate
430
431config DRM_LIB_RANDOM
432	bool
433	default n
434
435config DRM_PRIVACY_SCREEN
436	bool
437	default n
438