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

 
  1#
  2# Drm device configuration
  3#
  4# This driver provides support for the
  5# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.
  6#
  7menuconfig DRM
  8	tristate "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)"
  9	depends on (AGP || AGP=n) && !EMULATED_CMPXCHG && MMU && HAS_DMA
 
 
 
 
 10	select HDMI
 11	select I2C
 12	select I2C_ALGOBIT
 13	select DMA_SHARED_BUFFER
 
 
 
 
 
 
 14	help
 15	  Kernel-level support for the Direct Rendering Infrastructure (DRI)
 16	  introduced in XFree86 4.0. If you say Y here, you need to select
 17	  the module that's right for your graphics card from the list below.
 18	  These modules provide support for synchronization, security, and
 19	  DMA transfers. Please see <http://dri.sourceforge.net/> for more
 20	  details.  You should also select and configure AGP
 21	  (/dev/agpgart) support if it is available for your platform.
 22
 
 
 
 
 
 23config DRM_MIPI_DSI
 24	bool
 25	depends on DRM
 26
 27config DRM_USB
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 28	tristate
 29	depends on DRM
 30	depends on USB_SUPPORT && USB_ARCH_HAS_HCD
 31	select USB
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 32
 33config DRM_KMS_HELPER
 34	tristate
 35	depends on DRM
 36	help
 37	  CRTC helpers for KMS drivers.
 38
 39config DRM_KMS_FB_HELPER
 40	bool
 41	depends on DRM_KMS_HELPER
 42	select FB
 43	select FRAMEBUFFER_CONSOLE if !EXPERT
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 44	select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
 
 45	help
 46	  FBDEV helpers for KMS drivers.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 47
 48config DRM_LOAD_EDID_FIRMWARE
 49	bool "Allow to specify an EDID data set instead of probing for it"
 50	depends on DRM_KMS_HELPER
 51	help
 52	  Say Y here, if you want to use EDID data to be loaded from the
 53	  /lib/firmware directory or one of the provided built-in
 54	  data sets. This may be necessary, if the graphics adapter or
 55	  monitor are unable to provide appropriate EDID data. Since this
 56	  feature is provided as a workaround for broken hardware, the
 57	  default case is N. Details and instructions how to build your own
 58	  EDID data are given in Documentation/EDID/HOWTO.txt.
 
 
 59
 60config DRM_TTM
 61	tristate
 62	depends on DRM
 63	help
 64	  GPU memory management subsystem for devices with multiple
 65	  GPU memory types. Will be enabled automatically if a device driver
 66	  uses it.
 67
 68config DRM_GEM_CMA_HELPER
 69	bool
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 70	depends on DRM
 
 71	help
 72	  Choose this if you need the GEM CMA helper functions
 73
 74config DRM_KMS_CMA_HELPER
 75	bool
 76	select DRM_GEM_CMA_HELPER
 77	select DRM_KMS_FB_HELPER
 78	select FB_SYS_FILLRECT
 79	select FB_SYS_COPYAREA
 80	select FB_SYS_IMAGEBLIT
 81	help
 82	  Choose this if you need the KMS CMA helper functions
 
 
 
 
 
 
 
 
 83
 84source "drivers/gpu/drm/i2c/Kconfig"
 85
 86config DRM_TDFX
 87	tristate "3dfx Banshee/Voodoo3+"
 88	depends on DRM && PCI
 89	help
 90	  Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
 91	  graphics card.  If M is selected, the module will be called tdfx.
 92
 93config DRM_R128
 94	tristate "ATI Rage 128"
 95	depends on DRM && PCI
 96	select FW_LOADER
 97	help
 98	  Choose this option if you have an ATI Rage 128 graphics card.  If M
 99	  is selected, the module will be called r128.  AGP support for
100	  this card is strongly suggested (unless you have a PCI version).
101
102config DRM_RADEON
103	tristate "ATI Radeon"
104	depends on DRM && PCI
105	select FB_CFB_FILLRECT
106	select FB_CFB_COPYAREA
107	select FB_CFB_IMAGEBLIT
108	select FW_LOADER
109        select DRM_KMS_HELPER
110	select DRM_KMS_FB_HELPER
111        select DRM_TTM
112	select POWER_SUPPLY
113	select HWMON
114	select BACKLIGHT_CLASS_DEVICE
115	help
116	  Choose this option if you have an ATI Radeon graphics card.  There
117	  are both PCI and AGP versions.  You don't need to choose this to
118	  run the Radeon in plain VGA mode.
119
120	  If M is selected, the module will be called radeon.
121
122source "drivers/gpu/drm/radeon/Kconfig"
123
124source "drivers/gpu/drm/nouveau/Kconfig"
125
126config DRM_I810
127	tristate "Intel I810"
128	# !PREEMPT because of missing ioctl locking
129	depends on DRM && AGP && AGP_INTEL && (!PREEMPT || BROKEN)
130	help
131	  Choose this option if you have an Intel I810 graphics card.  If M is
132	  selected, the module will be called i810.  AGP support is required
133	  for this driver to work.
134
135source "drivers/gpu/drm/i915/Kconfig"
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
136
137config DRM_MGA
138	tristate "Matrox g200/g400"
139	depends on DRM && PCI
140	select FW_LOADER
141	help
142	  Choose this option if you have a Matrox G200, G400 or G450 graphics
143	  card.  If M is selected, the module will be called mga.  AGP
144	  support is required for this driver to work.
145
146config DRM_SIS
147	tristate "SiS video cards"
148	depends on DRM && AGP
149	depends on FB_SIS || FB_SIS=n
150	help
151	  Choose this option if you have a SiS 630 or compatible video
152          chipset. If M is selected the module will be called sis. AGP
153          support is required for this driver to work.
154
155config DRM_VIA
156	tristate "Via unichrome video cards"
157	depends on DRM && PCI
158	help
159	  Choose this option if you have a Via unichrome or compatible video
160	  chipset. If M is selected the module will be called via.
161
162config DRM_SAVAGE
163	tristate "Savage video cards"
164	depends on DRM && PCI
165	help
166	  Choose this option if you have a Savage3D/4/SuperSavage/Pro/Twister
167	  chipset. If M is selected the module will be called savage.
168
169source "drivers/gpu/drm/exynos/Kconfig"
170
 
 
171source "drivers/gpu/drm/vmwgfx/Kconfig"
172
173source "drivers/gpu/drm/gma500/Kconfig"
174
175source "drivers/gpu/drm/udl/Kconfig"
176
177source "drivers/gpu/drm/ast/Kconfig"
178
179source "drivers/gpu/drm/mgag200/Kconfig"
180
181source "drivers/gpu/drm/cirrus/Kconfig"
182
183source "drivers/gpu/drm/armada/Kconfig"
184
185source "drivers/gpu/drm/rcar-du/Kconfig"
186
187source "drivers/gpu/drm/shmobile/Kconfig"
188
189source "drivers/gpu/drm/omapdrm/Kconfig"
190
191source "drivers/gpu/drm/tilcdc/Kconfig"
192
193source "drivers/gpu/drm/qxl/Kconfig"
194
195source "drivers/gpu/drm/bochs/Kconfig"
196
197source "drivers/gpu/drm/msm/Kconfig"
198
 
 
199source "drivers/gpu/drm/tegra/Kconfig"
200
 
 
201source "drivers/gpu/drm/panel/Kconfig"
202
203source "drivers/gpu/drm/bridge/Kconfig"