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