Loading...
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 HDMI
13 select FB_CMDLINE
14 select I2C
15 select I2C_ALGOBIT
16 select DMA_SHARED_BUFFER
17 select SYNC_FILE
18 help
19 Kernel-level support for the Direct Rendering Infrastructure (DRI)
20 introduced in XFree86 4.0. If you say Y here, you need to select
21 the module that's right for your graphics card from the list below.
22 These modules provide support for synchronization, security, and
23 DMA transfers. Please see <http://dri.sourceforge.net/> for more
24 details. You should also select and configure AGP
25 (/dev/agpgart) support if it is available for your platform.
26
27config DRM_MIPI_DBI
28 tristate
29 depends on DRM
30
31config DRM_MIPI_DSI
32 bool
33 depends on DRM
34
35config DRM_DP_AUX_CHARDEV
36 bool "DRM DP AUX Interface"
37 depends on DRM
38 help
39 Choose this option to enable a /dev/drm_dp_auxN node that allows to
40 read and write values to arbitrary DPCD registers on the DP aux
41 channel.
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=y
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_DEBUG_SELFTEST
58 tristate "kselftests for DRM"
59 depends on DRM
60 depends on DEBUG_KERNEL
61 select PRIME_NUMBERS
62 select DRM_LIB_RANDOM
63 select DRM_KMS_HELPER
64 default n
65 help
66 This option provides kernel modules that can be used to run
67 various selftests on parts of the DRM api. This option is not
68 useful for distributions or general kernels, but only for kernel
69 developers working on DRM and associated drivers.
70
71 If in doubt, say "N".
72
73config DRM_KMS_HELPER
74 tristate
75 depends on DRM
76 help
77 CRTC helpers for KMS drivers.
78
79config DRM_KMS_FB_HELPER
80 bool
81 depends on DRM_KMS_HELPER
82 select FB
83 select FRAMEBUFFER_CONSOLE if !EXPERT
84 select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
85 select FB_SYS_FOPS
86 select FB_SYS_FILLRECT
87 select FB_SYS_COPYAREA
88 select FB_SYS_IMAGEBLIT
89 select FB_CFB_FILLRECT
90 select FB_CFB_COPYAREA
91 select FB_CFB_IMAGEBLIT
92 select FB_DEFERRED_IO
93 help
94 FBDEV helpers for KMS drivers.
95
96config DRM_FBDEV_EMULATION
97 bool "Enable legacy fbdev support for your modesetting driver"
98 depends on DRM
99 select DRM_KMS_HELPER
100 select DRM_KMS_FB_HELPER
101 default y
102 help
103 Choose this option if you have a need for the legacy fbdev
104 support. Note that this support also provides the linux console
105 support on top of your modesetting driver.
106
107 If in doubt, say "Y".
108
109config DRM_FBDEV_OVERALLOC
110 int "Overallocation of the fbdev buffer"
111 depends on DRM_FBDEV_EMULATION
112 default 100
113 help
114 Defines the fbdev buffer overallocation in percent. Default
115 is 100. Typical values for double buffering will be 200,
116 triple buffering 300.
117
118config DRM_FBDEV_LEAK_PHYS_SMEM
119 bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)"
120 depends on DRM_FBDEV_EMULATION && EXPERT
121 default n
122 help
123 In order to keep user-space compatibility, we want in certain
124 use-cases to keep leaking the fbdev physical address to the
125 user-space program handling the fbdev buffer.
126 This affects, not only, Amlogic, Allwinner or Rockchip devices
127 with ARM Mali GPUs using an userspace Blob.
128 This option is not supported by upstream developers and should be
129 removed as soon as possible and be considered as a broken and
130 legacy behaviour from a modern fbdev device driver.
131
132 Please send any bug reports when using this to your proprietary
133 software vendor that requires this.
134
135 If in doubt, say "N" or spread the word to your closed source
136 library vendor.
137
138config DRM_LOAD_EDID_FIRMWARE
139 bool "Allow to specify an EDID data set instead of probing for it"
140 depends on DRM
141 help
142 Say Y here, if you want to use EDID data to be loaded from the
143 /lib/firmware directory or one of the provided built-in
144 data sets. This may be necessary, if the graphics adapter or
145 monitor are unable to provide appropriate EDID data. Since this
146 feature is provided as a workaround for broken hardware, the
147 default case is N. Details and instructions how to build your own
148 EDID data are given in Documentation/driver-api/edid.rst.
149
150config DRM_DP_CEC
151 bool "Enable DisplayPort CEC-Tunneling-over-AUX HDMI support"
152 select CEC_CORE
153 help
154 Choose this option if you want to enable HDMI CEC support for
155 DisplayPort/USB-C to HDMI adapters.
156
157 Note: not all adapters support this feature, and even for those
158 that do support this they often do not hook up the CEC pin.
159
160config DRM_TTM
161 tristate
162 depends on DRM && MMU
163 help
164 GPU memory management subsystem for devices with multiple
165 GPU memory types. Will be enabled automatically if a device driver
166 uses it.
167
168config DRM_VRAM_HELPER
169 tristate
170 depends on DRM
171 select DRM_TTM
172 help
173 Helpers for VRAM memory management
174
175config DRM_GEM_CMA_HELPER
176 bool
177 depends on DRM
178 help
179 Choose this if you need the GEM CMA helper functions
180
181config DRM_KMS_CMA_HELPER
182 bool
183 depends on DRM
184 select DRM_GEM_CMA_HELPER
185 help
186 Choose this if you need the KMS CMA helper functions
187
188config DRM_GEM_SHMEM_HELPER
189 bool
190 depends on DRM
191 help
192 Choose this if you need the GEM shmem helper functions
193
194config DRM_VM
195 bool
196 depends on DRM && MMU
197
198config DRM_SCHED
199 tristate
200 depends on DRM
201
202source "drivers/gpu/drm/i2c/Kconfig"
203
204source "drivers/gpu/drm/arm/Kconfig"
205
206config DRM_RADEON
207 tristate "ATI Radeon"
208 depends on DRM && PCI && MMU
209 select FW_LOADER
210 select DRM_KMS_HELPER
211 select DRM_TTM
212 select POWER_SUPPLY
213 select HWMON
214 select BACKLIGHT_CLASS_DEVICE
215 select INTERVAL_TREE
216 help
217 Choose this option if you have an ATI Radeon graphics card. There
218 are both PCI and AGP versions. You don't need to choose this to
219 run the Radeon in plain VGA mode.
220
221 If M is selected, the module will be called radeon.
222
223source "drivers/gpu/drm/radeon/Kconfig"
224
225config DRM_AMDGPU
226 tristate "AMD GPU"
227 depends on DRM && PCI && MMU
228 select FW_LOADER
229 select DRM_KMS_HELPER
230 select DRM_SCHED
231 select DRM_TTM
232 select POWER_SUPPLY
233 select HWMON
234 select BACKLIGHT_CLASS_DEVICE
235 select INTERVAL_TREE
236 select CHASH
237 help
238 Choose this option if you have a recent AMD Radeon graphics card.
239
240 If M is selected, the module will be called amdgpu.
241
242source "drivers/gpu/drm/amd/amdgpu/Kconfig"
243
244source "drivers/gpu/drm/nouveau/Kconfig"
245
246source "drivers/gpu/drm/i915/Kconfig"
247
248config DRM_VGEM
249 tristate "Virtual GEM provider"
250 depends on DRM
251 help
252 Choose this option to get a virtual graphics memory manager,
253 as used by Mesa's software renderer for enhanced performance.
254 If M is selected the module will be called vgem.
255
256config DRM_VKMS
257 tristate "Virtual KMS (EXPERIMENTAL)"
258 depends on DRM
259 select DRM_KMS_HELPER
260 default n
261 help
262 Virtual Kernel Mode-Setting (VKMS) is used for testing or for
263 running GPU in a headless machines. Choose this option to get
264 a VKMS.
265
266 If M is selected the module will be called vkms.
267
268config DRM_ATI_PCIGART
269 bool
270
271source "drivers/gpu/drm/exynos/Kconfig"
272
273source "drivers/gpu/drm/rockchip/Kconfig"
274
275source "drivers/gpu/drm/vmwgfx/Kconfig"
276
277source "drivers/gpu/drm/gma500/Kconfig"
278
279source "drivers/gpu/drm/udl/Kconfig"
280
281source "drivers/gpu/drm/ast/Kconfig"
282
283source "drivers/gpu/drm/mgag200/Kconfig"
284
285source "drivers/gpu/drm/cirrus/Kconfig"
286
287source "drivers/gpu/drm/armada/Kconfig"
288
289source "drivers/gpu/drm/atmel-hlcdc/Kconfig"
290
291source "drivers/gpu/drm/rcar-du/Kconfig"
292
293source "drivers/gpu/drm/shmobile/Kconfig"
294
295source "drivers/gpu/drm/sun4i/Kconfig"
296
297source "drivers/gpu/drm/omapdrm/Kconfig"
298
299source "drivers/gpu/drm/tilcdc/Kconfig"
300
301source "drivers/gpu/drm/qxl/Kconfig"
302
303source "drivers/gpu/drm/bochs/Kconfig"
304
305source "drivers/gpu/drm/virtio/Kconfig"
306
307source "drivers/gpu/drm/msm/Kconfig"
308
309source "drivers/gpu/drm/fsl-dcu/Kconfig"
310
311source "drivers/gpu/drm/tegra/Kconfig"
312
313source "drivers/gpu/drm/stm/Kconfig"
314
315source "drivers/gpu/drm/panel/Kconfig"
316
317source "drivers/gpu/drm/bridge/Kconfig"
318
319source "drivers/gpu/drm/sti/Kconfig"
320
321source "drivers/gpu/drm/imx/Kconfig"
322
323source "drivers/gpu/drm/ingenic/Kconfig"
324
325source "drivers/gpu/drm/v3d/Kconfig"
326
327source "drivers/gpu/drm/vc4/Kconfig"
328
329source "drivers/gpu/drm/etnaviv/Kconfig"
330
331source "drivers/gpu/drm/arc/Kconfig"
332
333source "drivers/gpu/drm/hisilicon/Kconfig"
334
335source "drivers/gpu/drm/mediatek/Kconfig"
336
337source "drivers/gpu/drm/zte/Kconfig"
338
339source "drivers/gpu/drm/mxsfb/Kconfig"
340
341source "drivers/gpu/drm/meson/Kconfig"
342
343source "drivers/gpu/drm/tiny/Kconfig"
344
345source "drivers/gpu/drm/pl111/Kconfig"
346
347source "drivers/gpu/drm/tve200/Kconfig"
348
349source "drivers/gpu/drm/xen/Kconfig"
350
351source "drivers/gpu/drm/vboxvideo/Kconfig"
352
353source "drivers/gpu/drm/lima/Kconfig"
354
355source "drivers/gpu/drm/panfrost/Kconfig"
356
357source "drivers/gpu/drm/aspeed/Kconfig"
358
359source "drivers/gpu/drm/mcde/Kconfig"
360
361# Keep legacy drivers last
362
363menuconfig DRM_LEGACY
364 bool "Enable legacy drivers (DANGEROUS)"
365 depends on DRM && MMU
366 select DRM_VM
367 select DRM_ATI_PCIGART if PCI
368 help
369 Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous
370 APIs to user-space, which can be used to circumvent access
371 restrictions and other security measures. For backwards compatibility
372 those drivers are still available, but their use is highly
373 inadvisable and might harm your system.
374
375 You are recommended to use the safe modeset-only drivers instead, and
376 perform 3D emulation in user-space.
377
378 Unless you have strong reasons to go rogue, say "N".
379
380if DRM_LEGACY
381
382config DRM_TDFX
383 tristate "3dfx Banshee/Voodoo3+"
384 depends on DRM && PCI
385 help
386 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
387 graphics card. If M is selected, the module will be called tdfx.
388
389config DRM_R128
390 tristate "ATI Rage 128"
391 depends on DRM && PCI
392 select FW_LOADER
393 help
394 Choose this option if you have an ATI Rage 128 graphics card. If M
395 is selected, the module will be called r128. AGP support for
396 this card is strongly suggested (unless you have a PCI version).
397
398config DRM_I810
399 tristate "Intel I810"
400 # !PREEMPT because of missing ioctl locking
401 depends on DRM && AGP && AGP_INTEL && (!PREEMPTION || BROKEN)
402 help
403 Choose this option if you have an Intel I810 graphics card. If M is
404 selected, the module will be called i810. AGP support is required
405 for this driver to work.
406
407config DRM_MGA
408 tristate "Matrox g200/g400"
409 depends on DRM && PCI
410 select FW_LOADER
411 help
412 Choose this option if you have a Matrox G200, G400 or G450 graphics
413 card. If M is selected, the module will be called mga. AGP
414 support is required for this driver to work.
415
416config DRM_SIS
417 tristate "SiS video cards"
418 depends on DRM && AGP
419 depends on FB_SIS || FB_SIS=n
420 help
421 Choose this option if you have a SiS 630 or compatible video
422 chipset. If M is selected the module will be called sis. AGP
423 support is required for this driver to work.
424
425config DRM_VIA
426 tristate "Via unichrome video cards"
427 depends on DRM && PCI
428 help
429 Choose this option if you have a Via unichrome or compatible video
430 chipset. If M is selected the module will be called via.
431
432config DRM_SAVAGE
433 tristate "Savage video cards"
434 depends on DRM && PCI
435 help
436 Choose this option if you have a Savage3D/4/SuperSavage/Pro/Twister
437 chipset. If M is selected the module will be called savage.
438
439endif # DRM_LEGACY
440
441# Separate option because drm_panel_orientation_quirks.c is shared with fbdev
442config DRM_PANEL_ORIENTATION_QUIRKS
443 tristate
444
445config DRM_LIB_RANDOM
446 bool
447 default n
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 HDMI
13 select I2C
14 select DMA_SHARED_BUFFER
15 select SYNC_FILE
16# gallium uses SYS_kcmp for os_same_file_description() to de-duplicate
17# device and dmabuf fd. Let's make sure that is available for our userspace.
18 select KCMP
19 select VIDEO
20 help
21 Kernel-level support for the Direct Rendering Infrastructure (DRI)
22 introduced in XFree86 4.0. If you say Y here, you need to select
23 the module that's right for your graphics card from the list below.
24 These modules provide support for synchronization, security, and
25 DMA transfers. Please see <http://dri.sourceforge.net/> for more
26 details. You should also select and configure AGP
27 (/dev/agpgart) support if it is available for your platform.
28
29if DRM
30
31config DRM_MIPI_DBI
32 tristate
33 depends on DRM
34 select DRM_KMS_HELPER
35
36config DRM_MIPI_DSI
37 bool
38 depends on DRM
39
40config DRM_DEBUG_MM
41 bool "Insert extra checks and debug info into the DRM range managers"
42 default n
43 depends on DRM
44 depends on STACKTRACE_SUPPORT
45 select STACKDEPOT
46 help
47 Enable allocation tracking of memory manager and leak detection on
48 shutdown.
49
50 Recommended for driver developers only.
51
52 If in doubt, say "N".
53
54config DRM_USE_DYNAMIC_DEBUG
55 bool "use dynamic debug to implement drm.debug"
56 default n
57 depends on BROKEN
58 depends on DRM
59 depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE
60 depends on JUMP_LABEL
61 help
62 Use dynamic-debug to avoid drm_debug_enabled() runtime overheads.
63 Due to callsite counts in DRM drivers (~4k in amdgpu) and 56
64 bytes per callsite, the .data costs can be substantial, and
65 are therefore configurable.
66
67config DRM_KUNIT_TEST_HELPERS
68 tristate
69 depends on DRM && KUNIT
70 select DRM_KMS_HELPER
71 help
72 KUnit Helpers for KMS drivers.
73
74config DRM_KUNIT_TEST
75 tristate "KUnit tests for DRM" if !KUNIT_ALL_TESTS
76 depends on DRM && KUNIT && MMU
77 select DRM_BUDDY
78 select DRM_DISPLAY_DP_HELPER
79 select DRM_DISPLAY_HDMI_STATE_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_KUNIT_TEST_HELPERS
85 select DRM_LIB_RANDOM
86 select PRIME_NUMBERS
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 select FB_CORE if DRM_FBDEV_EMULATION
103 help
104 CRTC helpers for KMS drivers.
105
106config DRM_PANIC
107 bool "Display a user-friendly message when a kernel panic occurs"
108 depends on DRM
109 select FONT_SUPPORT
110 help
111 Enable a drm panic handler, which will display a user-friendly message
112 when a kernel panic occurs. It's useful when using a user-space
113 console instead of fbcon.
114 It will only work if your graphic driver supports this feature.
115 To support Hi-DPI Display, you can enable bigger fonts like
116 FONT_TER16x32
117
118config DRM_PANIC_FOREGROUND_COLOR
119 hex "Drm panic screen foreground color, in RGB"
120 depends on DRM_PANIC
121 default 0xffffff
122
123config DRM_PANIC_BACKGROUND_COLOR
124 hex "Drm panic screen background color, in RGB"
125 depends on DRM_PANIC
126 default 0x000000
127
128config DRM_PANIC_DEBUG
129 bool "Add a debug fs entry to trigger drm_panic"
130 depends on DRM_PANIC && DEBUG_FS
131 help
132 Add dri/[device]/drm_panic_plane_x in the kernel debugfs, to force the
133 panic handler to write the panic message to this plane scanout buffer.
134 This is unsafe and should not be enabled on a production build.
135 If in doubt, say "N".
136
137config DRM_PANIC_SCREEN
138 string "Panic screen formatter"
139 default "user"
140 depends on DRM_PANIC
141 help
142 This option enable to choose what will be displayed when a kernel
143 panic occurs. You can choose between "user", a short message telling
144 the user to reboot the system, or "kmsg" which will display the last
145 lines of kmsg.
146 This can also be overridden by drm.panic_screen=xxxx kernel parameter
147 or by writing to /sys/module/drm/parameters/panic_screen sysfs entry
148 Default is "user"
149
150config DRM_PANIC_SCREEN_QR_CODE
151 bool "Add a panic screen with a QR code"
152 depends on DRM_PANIC && RUST
153 select ZLIB_DEFLATE
154 help
155 This option adds a QR code generator, and a panic screen with a QR
156 code. The QR code will contain the last lines of kmsg and other debug
157 information. This should be easier for the user to report a kernel
158 panic, with all debug information available.
159 To use this panic screen, also set DRM_PANIC_SCREEN to "qr_code"
160
161config DRM_PANIC_SCREEN_QR_CODE_URL
162 string "Base URL of the QR code in the panic screen"
163 depends on DRM_PANIC_SCREEN_QR_CODE
164 help
165 This option sets the base URL to report the kernel panic. If it's set
166 the QR code will contain the URL and the kmsg compressed with zlib as
167 a URL parameter. If it's empty, the QR code will contain the kmsg as
168 uncompressed text only.
169 There is a demo code in javascript, to decode and uncompress the kmsg
170 data from the URL parameter at https://github.com/kdj0c/panic_report
171
172config DRM_PANIC_SCREEN_QR_VERSION
173 int "Maximum version (size) of the QR code."
174 depends on DRM_PANIC_SCREEN_QR_CODE
175 default 40
176 help
177 This option limits the version (or size) of the QR code. QR code
178 version ranges from Version 1 (21x21) to Version 40 (177x177).
179 Smaller QR code are easier to read, but will contain less debugging
180 data. Default is 40.
181
182config DRM_DEBUG_DP_MST_TOPOLOGY_REFS
183 bool "Enable refcount backtrace history in the DP MST helpers"
184 depends on STACKTRACE_SUPPORT
185 select STACKDEPOT
186 depends on DRM_KMS_HELPER
187 depends on DEBUG_KERNEL
188 depends on EXPERT
189 help
190 Enables debug tracing for topology refs in DRM's DP MST helpers. A
191 history of each topology reference/dereference will be printed to the
192 kernel log once a port or branch device's topology refcount reaches 0.
193
194 This has the potential to use a lot of memory and print some very
195 large kernel messages. If in doubt, say "N".
196
197config DRM_DEBUG_MODESET_LOCK
198 bool "Enable backtrace history for lock contention"
199 depends on STACKTRACE_SUPPORT
200 depends on DEBUG_KERNEL
201 depends on EXPERT
202 select STACKDEPOT
203 default y if DEBUG_WW_MUTEX_SLOWPATH
204 help
205 Enable debug tracing of failures to gracefully handle drm modeset lock
206 contention. A history of each drm modeset lock path hitting -EDEADLK
207 will be saved until gracefully handled, and the backtrace will be
208 printed when attempting to lock a contended lock.
209
210 If in doubt, say "N".
211
212config DRM_CLIENT
213 bool
214 depends on DRM
215 help
216 Enables support for DRM clients. DRM drivers that need
217 struct drm_client_dev and its interfaces should select this
218 option. Drivers that support the default clients should
219 select DRM_CLIENT_SELECTION instead.
220
221config DRM_CLIENT_LIB
222 tristate
223 depends on DRM
224 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION
225 select FB_CORE if DRM_FBDEV_EMULATION
226 help
227 This option enables the DRM client library and selects all
228 modules and components according to the enabled clients.
229
230config DRM_CLIENT_SELECTION
231 tristate
232 depends on DRM
233 select DRM_CLIENT_LIB if DRM_FBDEV_EMULATION
234 help
235 Drivers that support in-kernel DRM clients have to select this
236 option.
237
238config DRM_CLIENT_SETUP
239 bool
240 depends on DRM_CLIENT_SELECTION
241 help
242 Enables the DRM client selection. DRM drivers that support the
243 default clients should select DRM_CLIENT_SELECTION instead.
244
245menu "Supported DRM clients"
246 depends on DRM_CLIENT_SELECTION
247
248config DRM_FBDEV_EMULATION
249 bool "Enable legacy fbdev support for your modesetting driver"
250 depends on DRM_CLIENT_SELECTION
251 select DRM_CLIENT
252 select DRM_CLIENT_SETUP
253 select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
254 default FB
255 help
256 Choose this option if you have a need for the legacy fbdev
257 support. Note that this support also provides the linux console
258 support on top of your modesetting driver.
259
260 If in doubt, say "Y".
261
262config DRM_FBDEV_OVERALLOC
263 int "Overallocation of the fbdev buffer"
264 depends on DRM_FBDEV_EMULATION
265 default 100
266 help
267 Defines the fbdev buffer overallocation in percent. Default
268 is 100. Typical values for double buffering will be 200,
269 triple buffering 300.
270
271config DRM_FBDEV_LEAK_PHYS_SMEM
272 bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)"
273 depends on DRM_FBDEV_EMULATION && EXPERT
274 default n
275 help
276 In order to keep user-space compatibility, we want in certain
277 use-cases to keep leaking the fbdev physical address to the
278 user-space program handling the fbdev buffer.
279 This affects, not only, Amlogic, Allwinner or Rockchip devices
280 with ARM Mali GPUs using an userspace Blob.
281 This option is not supported by upstream developers and should be
282 removed as soon as possible and be considered as a broken and
283 legacy behaviour from a modern fbdev device driver.
284
285 Please send any bug reports when using this to your proprietary
286 software vendor that requires this.
287
288 If in doubt, say "N" or spread the word to your closed source
289 library vendor.
290
291endmenu
292
293config DRM_LOAD_EDID_FIRMWARE
294 bool "Allow to specify an EDID data set instead of probing for it"
295 depends on DRM
296 help
297 Say Y here, if you want to use EDID data to be loaded from the
298 /lib/firmware directory or one of the provided built-in
299 data sets. This may be necessary, if the graphics adapter or
300 monitor are unable to provide appropriate EDID data. Since this
301 feature is provided as a workaround for broken hardware, the
302 default case is N. Details and instructions how to build your own
303 EDID data are given in Documentation/admin-guide/edid.rst.
304
305source "drivers/gpu/drm/display/Kconfig"
306
307config DRM_TTM
308 tristate
309 depends on DRM && MMU
310 help
311 GPU memory management subsystem for devices with multiple
312 GPU memory types. Will be enabled automatically if a device driver
313 uses it.
314
315config DRM_TTM_KUNIT_TEST
316 tristate "KUnit tests for TTM" if !KUNIT_ALL_TESTS
317 default n
318 depends on DRM && KUNIT && MMU && (UML || COMPILE_TEST)
319 select DRM_TTM
320 select DRM_BUDDY
321 select DRM_EXPORT_FOR_TESTS if m
322 select DRM_KUNIT_TEST_HELPERS
323 default KUNIT_ALL_TESTS
324 help
325 Enables unit tests for TTM, a GPU memory manager subsystem used
326 to manage memory buffers. This option is mostly useful for kernel
327 developers. It depends on (UML || COMPILE_TEST) since no other driver
328 which uses TTM can be loaded while running the tests.
329
330 If in doubt, say "N".
331
332config DRM_EXEC
333 tristate
334 depends on DRM
335 help
336 Execution context for command submissions
337
338config DRM_GPUVM
339 tristate
340 depends on DRM
341 select DRM_EXEC
342 help
343 GPU-VM representation providing helpers to manage a GPUs virtual
344 address space
345
346config DRM_BUDDY
347 tristate
348 depends on DRM
349 help
350 A page based buddy allocator
351
352config DRM_VRAM_HELPER
353 tristate
354 depends on DRM
355 help
356 Helpers for VRAM memory management
357
358config DRM_TTM_HELPER
359 tristate
360 depends on DRM
361 select DRM_TTM
362 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION
363 select FB_CORE if DRM_FBDEV_EMULATION
364 select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION
365 help
366 Helpers for ttm-based gem objects
367
368config DRM_GEM_DMA_HELPER
369 tristate
370 depends on DRM
371 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION
372 select FB_CORE if DRM_FBDEV_EMULATION
373 select FB_DMAMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION
374 help
375 Choose this if you need the GEM DMA helper functions
376
377config DRM_GEM_SHMEM_HELPER
378 tristate
379 depends on DRM && MMU
380 select DRM_KMS_HELPER if DRM_FBDEV_EMULATION
381 select FB_CORE if DRM_FBDEV_EMULATION
382 select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION
383 help
384 Choose this if you need the GEM shmem helper functions
385
386config DRM_SUBALLOC_HELPER
387 tristate
388 depends on DRM
389
390config DRM_SCHED
391 tristate
392 depends on DRM
393
394source "drivers/gpu/drm/i2c/Kconfig"
395
396source "drivers/gpu/drm/arm/Kconfig"
397
398source "drivers/gpu/drm/radeon/Kconfig"
399
400source "drivers/gpu/drm/amd/amdgpu/Kconfig"
401
402source "drivers/gpu/drm/nouveau/Kconfig"
403
404source "drivers/gpu/drm/i915/Kconfig"
405
406source "drivers/gpu/drm/xe/Kconfig"
407
408source "drivers/gpu/drm/kmb/Kconfig"
409
410config DRM_VGEM
411 tristate "Virtual GEM provider"
412 depends on DRM && MMU
413 select DRM_GEM_SHMEM_HELPER
414 help
415 Choose this option to get a virtual graphics memory manager,
416 as used by Mesa's software renderer for enhanced performance.
417 If M is selected the module will be called vgem.
418
419source "drivers/gpu/drm/vkms/Kconfig"
420
421source "drivers/gpu/drm/exynos/Kconfig"
422
423source "drivers/gpu/drm/rockchip/Kconfig"
424
425source "drivers/gpu/drm/vmwgfx/Kconfig"
426
427source "drivers/gpu/drm/gma500/Kconfig"
428
429source "drivers/gpu/drm/udl/Kconfig"
430
431source "drivers/gpu/drm/ast/Kconfig"
432
433source "drivers/gpu/drm/mgag200/Kconfig"
434
435source "drivers/gpu/drm/armada/Kconfig"
436
437source "drivers/gpu/drm/atmel-hlcdc/Kconfig"
438
439source "drivers/gpu/drm/renesas/Kconfig"
440
441source "drivers/gpu/drm/sun4i/Kconfig"
442
443source "drivers/gpu/drm/omapdrm/Kconfig"
444
445source "drivers/gpu/drm/tilcdc/Kconfig"
446
447source "drivers/gpu/drm/qxl/Kconfig"
448
449source "drivers/gpu/drm/virtio/Kconfig"
450
451source "drivers/gpu/drm/msm/Kconfig"
452
453source "drivers/gpu/drm/fsl-dcu/Kconfig"
454
455source "drivers/gpu/drm/tegra/Kconfig"
456
457source "drivers/gpu/drm/stm/Kconfig"
458
459source "drivers/gpu/drm/panel/Kconfig"
460
461source "drivers/gpu/drm/bridge/Kconfig"
462
463source "drivers/gpu/drm/sti/Kconfig"
464
465source "drivers/gpu/drm/imx/Kconfig"
466
467source "drivers/gpu/drm/ingenic/Kconfig"
468
469source "drivers/gpu/drm/v3d/Kconfig"
470
471source "drivers/gpu/drm/vc4/Kconfig"
472
473source "drivers/gpu/drm/loongson/Kconfig"
474
475source "drivers/gpu/drm/etnaviv/Kconfig"
476
477source "drivers/gpu/drm/hisilicon/Kconfig"
478
479source "drivers/gpu/drm/logicvc/Kconfig"
480
481source "drivers/gpu/drm/mediatek/Kconfig"
482
483source "drivers/gpu/drm/mxsfb/Kconfig"
484
485source "drivers/gpu/drm/meson/Kconfig"
486
487source "drivers/gpu/drm/tiny/Kconfig"
488
489source "drivers/gpu/drm/pl111/Kconfig"
490
491source "drivers/gpu/drm/tve200/Kconfig"
492
493source "drivers/gpu/drm/xen/Kconfig"
494
495source "drivers/gpu/drm/vboxvideo/Kconfig"
496
497source "drivers/gpu/drm/lima/Kconfig"
498
499source "drivers/gpu/drm/panfrost/Kconfig"
500
501source "drivers/gpu/drm/panthor/Kconfig"
502
503source "drivers/gpu/drm/aspeed/Kconfig"
504
505source "drivers/gpu/drm/mcde/Kconfig"
506
507source "drivers/gpu/drm/tidss/Kconfig"
508
509source "drivers/gpu/drm/xlnx/Kconfig"
510
511source "drivers/gpu/drm/gud/Kconfig"
512
513source "drivers/gpu/drm/solomon/Kconfig"
514
515source "drivers/gpu/drm/sprd/Kconfig"
516
517source "drivers/gpu/drm/imagination/Kconfig"
518
519config DRM_HYPERV
520 tristate "DRM Support for Hyper-V synthetic video device"
521 depends on DRM && PCI && MMU && HYPERV
522 select DRM_CLIENT_SELECTION
523 select DRM_KMS_HELPER
524 select DRM_GEM_SHMEM_HELPER
525 help
526 This is a KMS driver for Hyper-V synthetic video device. Choose this
527 option if you would like to enable drm driver for Hyper-V virtual
528 machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so
529 that DRM driver is used by default.
530
531 If M is selected the module will be called hyperv_drm.
532
533config DRM_EXPORT_FOR_TESTS
534 bool
535
536# Separate option as not all DRM drivers use it
537config DRM_PANEL_BACKLIGHT_QUIRKS
538 tristate
539
540config DRM_LIB_RANDOM
541 bool
542 default n
543
544config DRM_PRIVACY_SCREEN
545 bool
546 default n
547
548config DRM_WERROR
549 bool "Compile the drm subsystem with warnings as errors"
550 depends on DRM && EXPERT
551 depends on !WERROR
552 default n
553 help
554 A kernel build should not cause any compiler warnings, and this
555 enables the '-Werror' flag to enforce that rule in the drm subsystem.
556
557 The drm subsystem enables more warnings than the kernel default, so
558 this config option is disabled by default.
559
560 If in doubt, say N.
561
562endif
563
564# Separate option because drm_panel_orientation_quirks.c is shared with fbdev
565config DRM_PANEL_ORIENTATION_QUIRKS
566 tristate