2019-05-19 13:07:45 +01:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2005-04-16 15:20:36 -07:00
|
|
|
#
|
|
|
|
|
# Drm device configuration
|
|
|
|
|
#
|
|
|
|
|
# This driver provides support for the
|
|
|
|
|
# Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher.
|
|
|
|
|
#
|
2007-10-16 01:29:39 -07:00
|
|
|
menuconfig DRM
|
2005-04-16 15:20:36 -07:00
|
|
|
tristate "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)"
|
2017-01-04 10:12:57 +01:00
|
|
|
depends on (AGP || AGP=n) && !EMULATED_CMPXCHG && HAS_DMA
|
2017-11-25 20:35:49 +01:00
|
|
|
select DRM_PANEL_ORIENTATION_QUIRKS
|
2023-07-19 10:15:38 +02:00
|
|
|
select DRM_KMS_HELPER if DRM_FBDEV_EMULATION
|
|
|
|
|
select FB_CORE if DRM_FBDEV_EMULATION
|
2023-07-29 21:26:47 +02:00
|
|
|
select FB_SYSMEM_HELPERS_DEFERRED if DRM_FBDEV_EMULATION
|
2012-11-21 15:31:35 +01:00
|
|
|
select HDMI
|
2008-12-13 18:21:08 +10:00
|
|
|
select I2C
|
2011-11-25 15:21:02 +00:00
|
|
|
select DMA_SHARED_BUFFER
|
2016-11-15 22:06:39 +09:00
|
|
|
select SYNC_FILE
|
2021-02-05 22:00:12 +00:00
|
|
|
# gallium uses SYS_kcmp for os_same_file_description() to de-duplicate
|
|
|
|
|
# device and dmabuf fd. Let's make sure that is available for our userspace.
|
|
|
|
|
select KCMP
|
2023-02-09 14:55:06 +01:00
|
|
|
select VIDEO_CMDLINE
|
2022-11-11 14:30:23 +01:00
|
|
|
select VIDEO_NOMODESET
|
2005-04-16 15:20:36 -07:00
|
|
|
help
|
|
|
|
|
Kernel-level support for the Direct Rendering Infrastructure (DRI)
|
|
|
|
|
introduced in XFree86 4.0. If you say Y here, you need to select
|
|
|
|
|
the module that's right for your graphics card from the list below.
|
|
|
|
|
These modules provide support for synchronization, security, and
|
|
|
|
|
DMA transfers. Please see <http://dri.sourceforge.net/> for more
|
|
|
|
|
details. You should also select and configure AGP
|
2010-05-27 13:40:25 -06:00
|
|
|
(/dev/agpgart) support if it is available for your platform.
|
2005-04-16 15:20:36 -07:00
|
|
|
|
2019-07-22 12:43:11 +02:00
|
|
|
config DRM_MIPI_DBI
|
|
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
2022-08-22 17:42:43 -07:00
|
|
|
select DRM_KMS_HELPER
|
2019-07-22 12:43:11 +02:00
|
|
|
|
2013-12-04 16:35:12 +01:00
|
|
|
config DRM_MIPI_DSI
|
|
|
|
|
bool
|
|
|
|
|
depends on DRM
|
|
|
|
|
|
2016-10-31 09:08:06 +00:00
|
|
|
config DRM_DEBUG_MM
|
|
|
|
|
bool "Insert extra checks and debug info into the DRM range managers"
|
|
|
|
|
default n
|
2016-11-08 13:19:17 +00:00
|
|
|
depends on DRM=y
|
2016-11-09 14:39:06 +00:00
|
|
|
depends on STACKTRACE_SUPPORT
|
2016-10-31 09:08:06 +00:00
|
|
|
select STACKDEPOT
|
|
|
|
|
help
|
|
|
|
|
Enable allocation tracking of memory manager and leak detection on
|
|
|
|
|
shutdown.
|
|
|
|
|
|
|
|
|
|
Recommended for driver developers only.
|
|
|
|
|
|
|
|
|
|
If in doubt, say "N".
|
|
|
|
|
|
2022-09-11 23:28:47 -06:00
|
|
|
config DRM_USE_DYNAMIC_DEBUG
|
|
|
|
|
bool "use dynamic debug to implement drm.debug"
|
2023-02-07 16:33:37 +02:00
|
|
|
default n
|
|
|
|
|
depends on BROKEN
|
2022-09-11 23:28:47 -06:00
|
|
|
depends on DRM
|
|
|
|
|
depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE
|
|
|
|
|
depends on JUMP_LABEL
|
|
|
|
|
help
|
|
|
|
|
Use dynamic-debug to avoid drm_debug_enabled() runtime overheads.
|
|
|
|
|
Due to callsite counts in DRM drivers (~4k in amdgpu) and 56
|
|
|
|
|
bytes per callsite, the .data costs can be substantial, and
|
|
|
|
|
are therefore configurable.
|
|
|
|
|
|
2022-12-01 16:11:33 +01:00
|
|
|
config DRM_KUNIT_TEST_HELPERS
|
|
|
|
|
tristate
|
|
|
|
|
depends on DRM && KUNIT
|
|
|
|
|
help
|
|
|
|
|
KUnit Helpers for KMS drivers.
|
|
|
|
|
|
2022-06-20 18:06:39 +02:00
|
|
|
config DRM_KUNIT_TEST
|
|
|
|
|
tristate "KUnit tests for DRM" if !KUNIT_ALL_TESTS
|
2022-07-08 17:30:44 -03:00
|
|
|
depends on DRM && KUNIT
|
|
|
|
|
select PRIME_NUMBERS
|
|
|
|
|
select DRM_DISPLAY_DP_HELPER
|
|
|
|
|
select DRM_DISPLAY_HELPER
|
|
|
|
|
select DRM_LIB_RANDOM
|
2022-06-20 18:06:39 +02:00
|
|
|
select DRM_KMS_HELPER
|
2022-07-08 17:30:44 -03:00
|
|
|
select DRM_BUDDY
|
|
|
|
|
select DRM_EXPORT_FOR_TESTS if m
|
2022-12-01 16:11:33 +01:00
|
|
|
select DRM_KUNIT_TEST_HELPERS
|
2022-04-13 16:09:00 +02:00
|
|
|
select DRM_EXEC
|
2022-06-20 18:06:39 +02:00
|
|
|
default KUNIT_ALL_TESTS
|
|
|
|
|
help
|
|
|
|
|
This builds unit tests for DRM. This option is not useful for
|
|
|
|
|
distributions or general kernels, but only for kernel
|
|
|
|
|
developers working on DRM and associated drivers.
|
|
|
|
|
|
|
|
|
|
For more information on KUnit and unit tests in general,
|
|
|
|
|
please refer to the KUnit documentation in
|
|
|
|
|
Documentation/dev-tools/kunit/.
|
|
|
|
|
|
|
|
|
|
If in doubt, say "N".
|
|
|
|
|
|
2009-09-08 11:08:32 +10:00
|
|
|
config DRM_KMS_HELPER
|
2009-09-07 15:45:33 +10:00
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
2013-10-08 17:44:47 +02:00
|
|
|
help
|
|
|
|
|
CRTC helpers for KMS drivers.
|
|
|
|
|
|
2019-06-20 17:59:25 -04:00
|
|
|
config DRM_DEBUG_DP_MST_TOPOLOGY_REFS
|
|
|
|
|
bool "Enable refcount backtrace history in the DP MST helpers"
|
2019-12-02 05:36:50 -08:00
|
|
|
depends on STACKTRACE_SUPPORT
|
2019-06-20 17:59:25 -04:00
|
|
|
select STACKDEPOT
|
|
|
|
|
depends on DRM_KMS_HELPER
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
depends on EXPERT
|
|
|
|
|
help
|
|
|
|
|
Enables debug tracing for topology refs in DRM's DP MST helpers. A
|
|
|
|
|
history of each topology reference/dereference will be printed to the
|
|
|
|
|
kernel log once a port or branch device's topology refcount reaches 0.
|
|
|
|
|
|
|
|
|
|
This has the potential to use a lot of memory and print some very
|
|
|
|
|
large kernel messages. If in doubt, say "N".
|
|
|
|
|
|
2021-10-01 12:14:44 +03:00
|
|
|
config DRM_DEBUG_MODESET_LOCK
|
|
|
|
|
bool "Enable backtrace history for lock contention"
|
|
|
|
|
depends on STACKTRACE_SUPPORT
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
depends on EXPERT
|
|
|
|
|
select STACKDEPOT
|
|
|
|
|
default y if DEBUG_WW_MUTEX_SLOWPATH
|
|
|
|
|
help
|
|
|
|
|
Enable debug tracing of failures to gracefully handle drm modeset lock
|
|
|
|
|
contention. A history of each drm modeset lock path hitting -EDEADLK
|
|
|
|
|
will be saved until gracefully handled, and the backtrace will be
|
|
|
|
|
printed when attempting to lock a contended lock.
|
|
|
|
|
|
|
|
|
|
If in doubt, say "N".
|
|
|
|
|
|
2015-08-05 12:28:57 +05:30
|
|
|
config DRM_FBDEV_EMULATION
|
|
|
|
|
bool "Enable legacy fbdev support for your modesetting driver"
|
2023-07-19 10:15:38 +02:00
|
|
|
depends on DRM
|
2021-04-15 13:00:40 +02:00
|
|
|
select FRAMEBUFFER_CONSOLE_DETECT_PRIMARY if FRAMEBUFFER_CONSOLE
|
2015-08-05 12:28:57 +05:30
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Choose this option if you have a need for the legacy fbdev
|
|
|
|
|
support. Note that this support also provides the linux console
|
|
|
|
|
support on top of your modesetting driver.
|
|
|
|
|
|
|
|
|
|
If in doubt, say "Y".
|
|
|
|
|
|
2017-02-15 17:19:08 +01:00
|
|
|
config DRM_FBDEV_OVERALLOC
|
|
|
|
|
int "Overallocation of the fbdev buffer"
|
|
|
|
|
depends on DRM_FBDEV_EMULATION
|
|
|
|
|
default 100
|
|
|
|
|
help
|
|
|
|
|
Defines the fbdev buffer overallocation in percent. Default
|
|
|
|
|
is 100. Typical values for double buffering will be 200,
|
|
|
|
|
triple buffering 300.
|
|
|
|
|
|
2018-09-28 14:05:55 +02:00
|
|
|
config DRM_FBDEV_LEAK_PHYS_SMEM
|
|
|
|
|
bool "Shamelessly allow leaking of fbdev physical address (DANGEROUS)"
|
|
|
|
|
depends on DRM_FBDEV_EMULATION && EXPERT
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
In order to keep user-space compatibility, we want in certain
|
|
|
|
|
use-cases to keep leaking the fbdev physical address to the
|
|
|
|
|
user-space program handling the fbdev buffer.
|
|
|
|
|
This affects, not only, Amlogic, Allwinner or Rockchip devices
|
|
|
|
|
with ARM Mali GPUs using an userspace Blob.
|
|
|
|
|
This option is not supported by upstream developers and should be
|
|
|
|
|
removed as soon as possible and be considered as a broken and
|
|
|
|
|
legacy behaviour from a modern fbdev device driver.
|
|
|
|
|
|
|
|
|
|
Please send any bug reports when using this to your proprietary
|
|
|
|
|
software vendor that requires this.
|
|
|
|
|
|
|
|
|
|
If in doubt, say "N" or spread the word to your closed source
|
|
|
|
|
library vendor.
|
|
|
|
|
|
2012-03-18 22:37:33 +01:00
|
|
|
config DRM_LOAD_EDID_FIRMWARE
|
|
|
|
|
bool "Allow to specify an EDID data set instead of probing for it"
|
drm: handle override and firmware EDID at drm_do_get_edid() level
Handle debugfs override edid and firmware edid at the low level to
transparently and completely replace the real edid. Previously, we
practically only used the modes from the override EDID, and none of the
other data, such as audio parameters.
This change also prevents actual EDID reads when the EDID is to be
overridden, but retains the DDC probe. This is useful if the reason for
preferring override EDID are problems with reading the data, or
corruption of the data.
Move firmware EDID loading from helper to core, as the functionality
moves to lower level as well. This will result in a change of module
parameter from drm_kms_helper.edid_firmware to drm.edid_firmware, which
arguably makes more sense anyway.
Some future work remains related to override and firmware EDID
validation. Like before, no validation is done for override EDID. The
firmware EDID is validated separately in the loader. Some unification
and deduplication would be in order, to validate all of them at the
drm_do_get_edid() level, like "real" EDIDs.
v2: move firmware loading to core
v3: rebase, commit message refresh
Cc: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Tested-by: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Acked-by: Dave Airlie <airlied@gmail.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/1e8a710bcac46e5136c1a7b430074893c81f364a.1505203831.git.jani.nikula@intel.com
2017-09-12 11:19:26 +03:00
|
|
|
depends on DRM
|
2012-03-18 22:37:33 +01:00
|
|
|
help
|
|
|
|
|
Say Y here, if you want to use EDID data to be loaded from the
|
|
|
|
|
/lib/firmware directory or one of the provided built-in
|
|
|
|
|
data sets. This may be necessary, if the graphics adapter or
|
|
|
|
|
monitor are unable to provide appropriate EDID data. Since this
|
|
|
|
|
feature is provided as a workaround for broken hardware, the
|
|
|
|
|
default case is N. Details and instructions how to build your own
|
2020-04-14 18:48:35 +02:00
|
|
|
EDID data are given in Documentation/admin-guide/edid.rst.
|
2012-03-18 22:37:33 +01:00
|
|
|
|
2022-04-21 09:31:03 +02:00
|
|
|
source "drivers/gpu/drm/display/Kconfig"
|
2018-07-11 15:29:07 +02:00
|
|
|
|
2009-06-10 15:20:19 +02:00
|
|
|
config DRM_TTM
|
2009-06-05 14:42:42 +02:00
|
|
|
tristate
|
2017-01-04 10:12:57 +01:00
|
|
|
depends on DRM && MMU
|
2009-06-10 15:20:19 +02:00
|
|
|
help
|
|
|
|
|
GPU memory management subsystem for devices with multiple
|
|
|
|
|
GPU memory types. Will be enabled automatically if a device driver
|
|
|
|
|
uses it.
|
|
|
|
|
|
2023-08-08 11:51:12 +02:00
|
|
|
config DRM_TTM_KUNIT_TEST
|
|
|
|
|
tristate "KUnit tests for TTM" if !KUNIT_ALL_TESTS
|
|
|
|
|
default n
|
2023-08-11 13:36:49 +02:00
|
|
|
depends on DRM && KUNIT && MMU
|
2023-08-08 11:51:12 +02:00
|
|
|
select DRM_TTM
|
|
|
|
|
select DRM_EXPORT_FOR_TESTS if m
|
|
|
|
|
select DRM_KUNIT_TEST_HELPERS
|
|
|
|
|
default KUNIT_ALL_TESTS
|
|
|
|
|
help
|
|
|
|
|
Enables unit tests for TTM, a GPU memory manager subsystem used
|
|
|
|
|
to manage memory buffers. This option is mostly useful for kernel
|
|
|
|
|
developers.
|
|
|
|
|
|
|
|
|
|
If in doubt, say "N".
|
|
|
|
|
|
2022-04-07 08:17:51 +02:00
|
|
|
config DRM_EXEC
|
|
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
|
|
|
|
help
|
|
|
|
|
Execution context for command submissions
|
|
|
|
|
|
2022-01-18 16:14:59 +05:30
|
|
|
config DRM_BUDDY
|
|
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
|
|
|
|
help
|
|
|
|
|
A page based buddy allocator
|
|
|
|
|
|
2019-05-08 10:26:11 +02:00
|
|
|
config DRM_VRAM_HELPER
|
|
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
|
|
|
|
help
|
|
|
|
|
Helpers for VRAM memory management
|
|
|
|
|
|
2019-09-04 07:47:35 +02:00
|
|
|
config DRM_TTM_HELPER
|
|
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
|
|
|
|
select DRM_TTM
|
|
|
|
|
help
|
|
|
|
|
Helpers for ttm-based gem objects
|
|
|
|
|
|
2022-08-02 02:04:03 +02:00
|
|
|
config DRM_GEM_DMA_HELPER
|
2021-10-20 15:19:41 +02:00
|
|
|
tristate
|
2016-01-20 15:02:05 -08:00
|
|
|
depends on DRM
|
2023-07-29 21:26:48 +02:00
|
|
|
select FB_DMAMEM_HELPERS if DRM_FBDEV_EMULATION
|
2012-06-27 15:30:18 +02:00
|
|
|
help
|
2022-08-02 02:04:03 +02:00
|
|
|
Choose this if you need the GEM DMA helper functions
|
2012-06-27 15:30:18 +02:00
|
|
|
|
2019-03-12 19:43:44 -05:00
|
|
|
config DRM_GEM_SHMEM_HELPER
|
2021-10-20 15:19:41 +02:00
|
|
|
tristate
|
drm/shmem-helper: Switch to vmf_insert_pfn
We want to stop gup, which isn't the case if we use vmf_insert_page
and VM_MIXEDMAP, because that does not set pte_special.
The motivation here is to stop get_user_pages from working on buffer
object mmaps in general. Quoting some discussion with Thomas:
On Thu, Jul 22, 2021 at 08:22:43PM +0200, Thomas Zimmermann wrote:
> Am 13.07.21 um 22:51 schrieb Daniel Vetter:
> > We want to stop gup, which isn't the case if we use vmf_insert_page
>
> What is gup?
get_user_pages. It pins memory wherever it is, which badly wreaks at least
ttm and could also cause trouble with cma allocations. In both cases
becaue we can't move/reuse these pages anymore.
Now get_user_pages fails when the memory isn't considered "normal", like
with VM_PFNMAP and using vm_insert_pfn. For consistency across all dma-buf
I'm trying (together with Christian König) to roll this out everywhere,
for fewer surprises.
E.g. for 5.14 iirc we merged a patch to do the same for ttm, where it
closes an actual bug (ttm gets really badly confused when there's suddenly
pinned pages where it thought it can move them).
cma allcoations already use VM_PFNMAP (because that's what dma_mmap is
using underneath), as is anything that's using remap_pfn_range. Worst case
we have to revert this patch for shmem helpers if it breaks something, but
I hope that's not the case. On the ttm side we've also had some fallout
that we needed to paper over with clever tricks.
v2: With this shmem gem helpers now definitely need CONFIG_MMU (0day)
v3: add more depends on MMU. For usb drivers this is a bit awkward,
but really it's correct: To be able to provide a contig mapping of
buffers to userspace on !MMU platforms we'd need to use the cma
helpers for these drivers on those platforms. As-is this wont work.
Also not exactly sure why vm_insert_page doesn't go boom, because that
definitely wont fly in practice since the pages are non-contig to
begin with.
v4: Explain the entire motivation a lot more (Thomas)
Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20210812131412.2487363-2-daniel.vetter@ffwll.ch
2021-08-12 15:14:10 +02:00
|
|
|
depends on DRM && MMU
|
2019-03-12 19:43:44 -05:00
|
|
|
help
|
|
|
|
|
Choose this if you need the GEM shmem helper functions
|
|
|
|
|
|
2023-02-24 10:51:50 +01:00
|
|
|
config DRM_SUBALLOC_HELPER
|
|
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
|
|
|
|
|
2017-12-06 17:49:39 +01:00
|
|
|
config DRM_SCHED
|
|
|
|
|
tristate
|
|
|
|
|
depends on DRM
|
|
|
|
|
|
2013-01-24 21:46:07 +00:00
|
|
|
source "drivers/gpu/drm/i2c/Kconfig"
|
|
|
|
|
|
2015-04-02 19:48:39 +01:00
|
|
|
source "drivers/gpu/drm/arm/Kconfig"
|
|
|
|
|
|
2010-02-01 11:35:47 +10:00
|
|
|
source "drivers/gpu/drm/radeon/Kconfig"
|
|
|
|
|
|
2015-04-20 16:55:21 -04:00
|
|
|
source "drivers/gpu/drm/amd/amdgpu/Kconfig"
|
2015-09-22 17:05:20 -04:00
|
|
|
|
2012-03-16 18:19:14 +10:00
|
|
|
source "drivers/gpu/drm/nouveau/Kconfig"
|
|
|
|
|
|
2013-10-09 09:18:51 +02:00
|
|
|
source "drivers/gpu/drm/i915/Kconfig"
|
2013-08-13 16:23:17 -07:00
|
|
|
|
2020-11-04 17:15:31 -08:00
|
|
|
source "drivers/gpu/drm/kmb/Kconfig"
|
|
|
|
|
|
2015-03-04 16:33:41 -08:00
|
|
|
config DRM_VGEM
|
|
|
|
|
tristate "Virtual GEM provider"
|
2021-08-12 15:14:12 +02:00
|
|
|
depends on DRM && MMU
|
|
|
|
|
select DRM_GEM_SHMEM_HELPER
|
2015-03-04 16:33:41 -08:00
|
|
|
help
|
|
|
|
|
Choose this option to get a virtual graphics memory manager,
|
|
|
|
|
as used by Mesa's software renderer for enhanced performance.
|
|
|
|
|
If M is selected the module will be called vgem.
|
|
|
|
|
|
2018-05-14 17:33:46 +03:00
|
|
|
config DRM_VKMS
|
2018-05-16 20:56:40 -03:00
|
|
|
tristate "Virtual KMS (EXPERIMENTAL)"
|
2021-08-12 15:14:12 +02:00
|
|
|
depends on DRM && MMU
|
2018-07-09 17:48:18 +02:00
|
|
|
select DRM_KMS_HELPER
|
2020-10-13 13:10:27 +02:00
|
|
|
select DRM_GEM_SHMEM_HELPER
|
2019-09-23 09:24:43 +08:00
|
|
|
select CRC32
|
2018-05-16 20:56:40 -03:00
|
|
|
default n
|
2018-05-14 17:33:46 +03:00
|
|
|
help
|
2018-05-16 20:56:40 -03:00
|
|
|
Virtual Kernel Mode-Setting (VKMS) is used for testing or for
|
|
|
|
|
running GPU in a headless machines. Choose this option to get
|
|
|
|
|
a VKMS.
|
|
|
|
|
|
2018-05-14 17:33:46 +03:00
|
|
|
If M is selected the module will be called vkms.
|
2015-03-04 16:33:41 -08:00
|
|
|
|
2011-10-11 10:42:51 +02:00
|
|
|
source "drivers/gpu/drm/exynos/Kconfig"
|
|
|
|
|
|
2014-08-22 18:36:26 +08:00
|
|
|
source "drivers/gpu/drm/rockchip/Kconfig"
|
|
|
|
|
|
2011-10-11 10:42:51 +02:00
|
|
|
source "drivers/gpu/drm/vmwgfx/Kconfig"
|
2011-11-03 18:22:48 +00:00
|
|
|
|
|
|
|
|
source "drivers/gpu/drm/gma500/Kconfig"
|
|
|
|
|
|
2010-12-15 07:14:24 +10:00
|
|
|
source "drivers/gpu/drm/udl/Kconfig"
|
drm: Initial KMS driver for AST (ASpeed Technologies) 2000 series (v2)
This is the initial driver for the Aspeed Technologies chips found in
servers. This driver supports the AST 2000, 2100, 2200, 2150 and 2300. It
doesn't support the AST11xx due to lack of hw to test it on, and them requiring
different codepaths.
This driver is intended to be used with xf86-video-modesetting in userspace.
This driver has a slightly different design than other KMS drivers, but
future server chips will probably share similiar setup. As these GPUs commonly
have low video RAM, it doesn't make sense to put the kms console in VRAM
always. This driver places the kms console into system RAM, and does dirty
updates to a copy in video RAM. When userspace sets a new scanout buffer,
it forcefully evicts the video RAM console, and X can create a framebuffer
that can use all of of video RAM.
This driver uses TTM but in a very simple fashion to control the eviction
to system RAM of the console, and multiple servers.
v2: add s/r support, fix Kconfig.
Signed-off-by: Dave Airlie <airlied@redhat.com>
2012-02-29 13:40:04 +00:00
|
|
|
|
|
|
|
|
source "drivers/gpu/drm/ast/Kconfig"
|
|
|
|
|
|
2012-04-17 15:01:25 +01:00
|
|
|
source "drivers/gpu/drm/mgag200/Kconfig"
|
2012-04-17 14:12:29 +01:00
|
|
|
|
2012-08-15 13:59:49 +01:00
|
|
|
source "drivers/gpu/drm/armada/Kconfig"
|
|
|
|
|
|
2015-01-06 11:13:28 +01:00
|
|
|
source "drivers/gpu/drm/atmel-hlcdc/Kconfig"
|
|
|
|
|
|
2023-05-02 11:09:08 +01:00
|
|
|
source "drivers/gpu/drm/renesas/Kconfig"
|
2012-11-15 21:28:22 +00:00
|
|
|
|
2015-10-29 09:36:23 +01:00
|
|
|
source "drivers/gpu/drm/sun4i/Kconfig"
|
|
|
|
|
|
2013-02-11 12:43:09 -05:00
|
|
|
source "drivers/gpu/drm/omapdrm/Kconfig"
|
2013-02-21 09:31:47 +10:00
|
|
|
|
2013-01-08 15:04:28 -06:00
|
|
|
source "drivers/gpu/drm/tilcdc/Kconfig"
|
drm: add new QXL driver. (v1.4)
QXL is a paravirtual graphics device used by the Spice virtual desktop
interface.
The drivers uses GEM and TTM to manage memory, the qxl hw fencing however
is quite different than normal TTM expects, we have to keep track of a number
of non-linear fence ids per bo that we need to have released by the hardware.
The releases are freed from a workqueue that wakes up and processes the
release ring.
releases are suballocated from a BO, there are 3 release categories, drawables,
surfaces and cursor cmds. The hw also has 3 rings for commands, cursor and release handling.
The hardware also have a surface id tracking mechnaism and the driver encapsulates it completely inside the kernel, userspace never sees the actual hw surface
ids.
This requires a newer version of the QXL userspace driver, so shouldn't be
enabled until that has been placed into your distro of choice.
Authors: Dave Airlie, Alon Levy
v1.1: fixup some issues in the ioctl interface with padding
v1.2: add module device table
v1.3: fix nomodeset, fbcon leak, dumb bo create, release ring irq,
don't try flush release ring (broken hw), fix -modesetting.
v1.4: fbcon cpu usage reduction + suitable accel flags.
Signed-off-by: Alon Levy <alevy@redhat.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
2013-02-25 14:47:55 +10:00
|
|
|
|
|
|
|
|
source "drivers/gpu/drm/qxl/Kconfig"
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
|
2013-09-09 10:02:56 +10:00
|
|
|
source "drivers/gpu/drm/virtio/Kconfig"
|
|
|
|
|
|
drm/msm: basic KMS driver for snapdragon
The snapdragon chips have multiple different display controllers,
depending on which chip variant/version. (As far as I can tell, current
devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And
then external to the display controller are HDMI, DSI, etc. blocks which
may be shared across devices which have different display controller
blocks.
To more easily add support for different display controller blocks, the
display controller specific bits are split out into a "kms" module,
which provides the kms plane/crtc/encoder objects.
The external HDMI, DSI, etc. blocks are part encoder, and part connector
currently. But I think I will pull in the drm_bridge patches from
chromeos tree, and split them into a bridge+connector, with the
registers that need to be set in modeset handled by the bridge. This
would remove the 'msm_connector' base class. But some things need to be
double checked to make sure I could get the correct ON/OFF sequencing..
This patch adds support for mdp4 crtc (including hw cursor), dtv encoder
(part of MDP4 block), and hdmi.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-06-26 12:44:06 -04:00
|
|
|
source "drivers/gpu/drm/msm/Kconfig"
|
2013-10-09 10:32:49 +02:00
|
|
|
|
2015-08-19 22:19:49 -04:00
|
|
|
source "drivers/gpu/drm/fsl-dcu/Kconfig"
|
|
|
|
|
|
2013-10-09 10:32:49 +02:00
|
|
|
source "drivers/gpu/drm/tegra/Kconfig"
|
2013-08-30 13:36:43 +02:00
|
|
|
|
2017-04-14 12:13:34 +02:00
|
|
|
source "drivers/gpu/drm/stm/Kconfig"
|
|
|
|
|
|
2013-08-30 13:36:43 +02:00
|
|
|
source "drivers/gpu/drm/panel/Kconfig"
|
2014-07-30 18:20:56 +02:00
|
|
|
|
2015-07-21 17:01:19 +02:00
|
|
|
source "drivers/gpu/drm/bridge/Kconfig"
|
|
|
|
|
|
2014-07-30 18:20:56 +02:00
|
|
|
source "drivers/gpu/drm/sti/Kconfig"
|
2014-07-16 21:08:55 +03:00
|
|
|
|
2014-11-24 16:33:34 +01:00
|
|
|
source "drivers/gpu/drm/imx/Kconfig"
|
2015-03-02 13:01:12 -08:00
|
|
|
|
2019-06-03 17:23:31 +02:00
|
|
|
source "drivers/gpu/drm/ingenic/Kconfig"
|
|
|
|
|
|
2018-04-30 11:10:58 -07:00
|
|
|
source "drivers/gpu/drm/v3d/Kconfig"
|
|
|
|
|
|
2015-03-02 13:01:12 -08:00
|
|
|
source "drivers/gpu/drm/vc4/Kconfig"
|
2015-12-03 18:21:29 +01:00
|
|
|
|
drm: Add kms driver for loongson display controller
Loongson display controller IP has been integrated in both Loongson north
bridge chipset (ls7a1000/ls7a2000) and Loongson SoCs (ls2k1000/ls2k2000).
It has even been included in Loongson's BMC products. It has two display
pipes, and each display pipe supports a primary plane and a cursor plane.
For the DC in the LS7a1000, each display pipe has a DVO output interface,
which is able to support 1920x1080@60Hz. For the DC in the LS7A2000, each
display pipe is equipped with a built-in HDMI encoder, which is compliant
with the HDMI 1.4 specification. The first display pipe is also equipped
with a transparent VGA encoder, which is parallel with the HDMI encoder.
To get a decent performance for writing framebuffer data to the VRAM, the
write combine support should be enabled.
v1 -> v2:
1) Use hpd status reg when polling for ls7a2000.
2) Fix all warnings that emerged when compiling with W=1.
v2 -> v3:
1) Add COMPILE_TEST to Kconfig and make the driver off by default
2) Alphabetical sorting headers (Thomas)
3) Untangle register access functions as much as possible (Thomas)
4) Switch to TTM-based memory manager (Thomas)
5) Add the chip ID detection function which can be used to distinguish
chip models
6) Revise the built-in HDMI phy driver, nearly all main stream mode below
4K@30Hz is tested, and this driver supports clone(mirror) display mode
and extend(joint) display mode.
v3 -> v4:
1) Quickly fix a small mistake.
v4 -> v5:
1) Add per display pipe debugfs support to the builtin HDMI encoder.
v5 -> v6:
1) Remove stray code which didn't get used, say lsdc_of_get_reserved_ram
2) Fix all typos I could found, make sentences and code more readable
3) Untangle lsdc_hdmi*_connector_detect() function according to the pipe
4) Rename this driver as loongson.
v6 -> v7:
1) Add prime support for buffer self-sharing, sharing buffer with
drm/etnaviv is also tested and it works with limitations.
2) Implement buffer object tracking with list_head.
3) Add S3(sleep to RAM) support
4) Rewrite lsdc_bo_move since TTM core stop allocating resources
during BO creation. Patch V1 ~ V6 of this series no longer work.
Thus, we send V7.
v7 -> v8:
1) Zero a compile warning on a 32-bit platform, compile with W=1
2) Revise lsdc_bo_gpu_offset() and make minor cleanups.
3) Pageflip tested on the virtual terminal with the following commands:
modetest -M loongson -s 32:1920x1080 -v
modetest -M loongson -s 34:1920x1080 -v -F tiles
It works like a charm, when running the pageflip test with dual screens
configuration, another two additional BOs were created by the modetest,
VRAM usage up to 40+ MB, well we have at least 64MB, still enough.
# cat bos
bo[0000]: size: 8112kB VRAM
bo[0001]: size: 16kB VRAM
bo[0002]: size: 16kB VRAM
bo[0003]: size: 16208kB VRAM
bo[0004]: size: 8112kB VRAM
bo[0005]: size: 8112kB VRAM
v8 -> v9:
1) Select I2C and I2C_ALGOBIT in Kconfig, should depend on MMU.
2) Using pci_get_domain_bus_and_slot to get the GPU device.
v9 -> v10:
1) Revise lsdc_drm_freeze() to implement S3 correctly. We realized that
the pinned BO could not be moved, the VRAM lost power when sleeping
to RAM. Thus, the data in the buffer who is pinned in VRAM will get
lost when resumed. Yet it's not a big problem because this driver
relies on the CPU to update the front framebuffer. We can see the
garbage data when resume from S3, but the screen will show the right
image as I move the cursor. This is due to the CPU repaint. v10 of
this patch makes S3 perfect by unpin all of the BOs in VRAM, evict
them all to system RAM in lsdc_drm_freeze().
v10 -> v11:
1) On a double-screen case, The buffer object backing the single giant
framebuffer is referenced by two GEM objects; hence, it will be
pinned at least twice by prepare_fb() function. This causes its pin
count > 1. V10 of this patch only unpins VRAM BOs once when suspend,
which is not correct on double-screen case. V11 of this patch unpin
the BOs until its pin count reaches zero when suspend. Then, we make
the S3 support complete finally. With v11, I can't see any garbage
data when resume.
2) Fix vblank wait timeout when disable CRTC.
3) Test against IGT, at least fbdev test and kms_flip test passed.
4) Rewrite pixel PLL update function, magic numbers eliminated (Emil)
5) Drop a few common hardware features description in lsdc_desc (Emil)
6) Drop lsdc_mode_config_mode_valid(), instead add restrictions in dumb
create function. (Emil)
7) Untangle the ls7a1000 case and ls7a2000 case completely (Thomas)
v11 -> v12:
none
v12 -> v13:
1) Add benchmarks to figure out the bandwidth of the hardware platform.
Usage:
# cd /sys/kernel/debug/dri/0/
# cat benchmark
2) VRAM is filled with garbage data if uninitialized, add a buffer
clearing procedure (lsdc_bo_clear), clear the BO on creation time.
3) Update copyrights and adjust coding style (Huacai)
v13 -> v14:
1) Trying to add async update support for cursor plane.
v14 -> v15:
1) Add lsdc_vga_set_decode() funciton, which allow us remove multi-video
cards workaround, now it allow drm/loongson, drm/amdgpu, drm/etnaviv
co-exist in the system, more is also possible (Emil and Xuerui)
2) Fix typos and grammar mistakes as much as possible (Xuerui)
3) Unify copyrights as GPL-2.0+ (Xuerui)
4) Fix a bug introduce since V13, TTM may import BO from other drivers,
we shouldn't clear it on such a case.
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel@ffwll.ch>
Cc: Sumit Semwal <sumit.semwal@linaro.org>
Cc: "Christian König" <christian.koenig@amd.com>
Cc: Nathan Chancellor <nathan@kernel.org>
Cc: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: loongson-kernel@lists.loongnix.cn
Tested-by: Liu Peibao <liupeibao@loongson.cn>
Tested-by: Li Yi <liyi@loongson.cn>
Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
Signed-off-by: Sui Jingfeng <suijingfeng@loongson.cn>
Link: https://patchwork.freedesktop.org/patch/msgid/20230615143613.1236245-2-15330273260@189.cn
2023-06-15 22:36:12 +08:00
|
|
|
source "drivers/gpu/drm/loongson/Kconfig"
|
|
|
|
|
|
2015-12-03 18:21:29 +01:00
|
|
|
source "drivers/gpu/drm/etnaviv/Kconfig"
|
2016-02-19 15:30:26 +03:00
|
|
|
|
2015-10-09 18:00:56 +08:00
|
|
|
source "drivers/gpu/drm/hisilicon/Kconfig"
|
2016-01-04 18:36:34 +01:00
|
|
|
|
2022-05-20 16:15:55 +02:00
|
|
|
source "drivers/gpu/drm/logicvc/Kconfig"
|
|
|
|
|
|
2016-01-04 18:36:34 +01:00
|
|
|
source "drivers/gpu/drm/mediatek/Kconfig"
|
2016-08-04 10:06:56 +02:00
|
|
|
|
2016-08-18 20:23:01 +02:00
|
|
|
source "drivers/gpu/drm/mxsfb/Kconfig"
|
|
|
|
|
|
2016-11-10 15:29:37 +01:00
|
|
|
source "drivers/gpu/drm/meson/Kconfig"
|
|
|
|
|
|
2019-07-25 12:51:31 +02:00
|
|
|
source "drivers/gpu/drm/tiny/Kconfig"
|
2017-01-22 00:15:00 +01:00
|
|
|
|
drm/pl111: Initial drm/kms driver for pl111
This is a modesetting driver for the pl111 CLCD display controller
found on various ARM platforms such as the Versatile Express. The
driver has only been tested on the bcm911360_entphn platform so far,
with PRIME-based buffer sharing between vc4 and clcd.
It reuses the existing devicetree binding, while not using quite as
many of its properties as the fbdev driver does (those are left for
future work).
v2: Nearly complete rewrite by anholt, cutting 2/3 of the code thanks
to DRM core's excellent new helpers.
v3: Don't match pl110 any more, don't attach if we don't have a DRM
panel, use DRM_GEM_CMA_FOPS, update MAINTAINERS, use the simple
display helper, use drm_gem_cma_dumb_create (same as our wrapper).
v4: Change the driver's .name to not clash with fbdev in sysfs, drop
platform alias, drop redundant "drm" in DRM driver name, hook up
.prepare_fb to the CMA helper so that DMA fences should work.
v5: Move register definitions inside the driver directory, fix build
in COMPILE_TEST and !AMBA mode.
v6: Drop TIM2_CLKSEL for now to be consistent with existing DT
bindings, switch back to external register definitions.
Signed-off-by: Tom Cooksey <tom.cooksey@arm.com>
Signed-off-by: Eric Anholt <eric@anholt.net>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org> (v5)
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/20170413031746.12921-2-eric@anholt.net
2017-04-12 20:17:46 -07:00
|
|
|
source "drivers/gpu/drm/pl111/Kconfig"
|
|
|
|
|
|
2017-08-20 12:05:55 +02:00
|
|
|
source "drivers/gpu/drm/tve200/Kconfig"
|
|
|
|
|
|
drm/xen-front: Add support for Xen PV display frontend
Add support for Xen para-virtualized frontend display driver.
Accompanying backend [1] is implemented as a user-space application
and its helper library [2], capable of running as a Weston client
or DRM master.
Configuration of both backend and frontend is done via
Xen guest domain configuration options [3].
Driver limitations:
1. Only primary plane without additional properties is supported.
2. Only one video mode supported which resolution is configured
via XenStore.
3. All CRTCs operate at fixed frequency of 60Hz.
1. Implement Xen bus state machine for the frontend driver according to
the state diagram and recovery flow from display para-virtualized
protocol: xen/interface/io/displif.h.
2. Read configuration values from Xen store according
to xen/interface/io/displif.h protocol:
- read connector(s) configuration
- read buffer allocation mode (backend/frontend)
3. Handle Xen event channels:
- create for all configured connectors and publish
corresponding ring references and event channels in Xen store,
so backend can connect
- implement event channels interrupt handlers
- create and destroy event channels with respect to Xen bus state
4. Implement shared buffer handling according to the
para-virtualized display device protocol at xen/interface/io/displif.h:
- handle page directories according to displif protocol:
- allocate and share page directories
- grant references to the required set of pages for the
page directory
- allocate xen balllooned pages via Xen balloon driver
with alloc_xenballooned_pages/free_xenballooned_pages
- grant references to the required set of pages for the
shared buffer itself
- implement pages map/unmap for the buffers allocated by the
backend (gnttab_map_refs/gnttab_unmap_refs)
5. Implement kernel modesetiing/connector handling using
DRM simple KMS helper pipeline:
- implement KMS part of the driver with the help of DRM
simple pipepline helper which is possible due to the fact
that the para-virtualized driver only supports a single
(primary) plane:
- initialize connectors according to XenStore configuration
- handle frame done events from the backend
- create and destroy frame buffers and propagate those
to the backend
- propagate set/reset mode configuration to the backend on display
enable/disable callbacks
- send page flip request to the backend and implement logic for
reporting backend IO errors on prepare fb callback
- implement virtual connector handling:
- support only pixel formats suitable for single plane modes
- make sure the connector is always connected
- support a single video mode as per para-virtualized driver
configuration
6. Implement GEM handling depending on driver mode of operation:
depending on the requirements for the para-virtualized environment,
namely requirements dictated by the accompanying DRM/(v)GPU drivers
running in both host and guest environments, number of operating
modes of para-virtualized display driver are supported:
- display buffers can be allocated by either
frontend driver or backend
- display buffers can be allocated to be contiguous
in memory or not
Note! Frontend driver itself has no dependency on contiguous memory for
its operation.
6.1. Buffers allocated by the frontend driver.
The below modes of operation are configured at compile-time via
frontend driver's kernel configuration.
6.1.1. Front driver configured to use GEM CMA helpers
This use-case is useful when used with accompanying DRM/vGPU driver
in guest domain which was designed to only work with contiguous
buffers, e.g. DRM driver based on GEM CMA helpers: such drivers can
only import contiguous PRIME buffers, thus requiring frontend driver
to provide such. In order to implement this mode of operation
para-virtualized frontend driver can be configured to use
GEM CMA helpers.
6.1.2. Front driver doesn't use GEM CMA
If accompanying drivers can cope with non-contiguous memory then, to
lower pressure on CMA subsystem of the kernel, driver can allocate
buffers from system memory.
Note! If used with accompanying DRM/(v)GPU drivers this mode of operation
may require IOMMU support on the platform, so accompanying DRM/vGPU
hardware can still reach display buffer memory while importing PRIME
buffers from the frontend driver.
6.2. Buffers allocated by the backend
This mode of operation is run-time configured via guest domain
configuration through XenStore entries.
For systems which do not provide IOMMU support, but having specific
requirements for display buffers it is possible to allocate such buffers
at backend side and share those with the frontend.
For example, if host domain is 1:1 mapped and has DRM/GPU hardware
expecting physically contiguous memory, this allows implementing
zero-copying use-cases.
Note, while using this scenario the following should be considered:
a) If guest domain dies then pages/grants received from the backend
cannot be claimed back
b) Misbehaving guest may send too many requests to the
backend exhausting its grant references and memory
(consider this from security POV).
Note! Configuration options 1.1 (contiguous display buffers) and 2
(backend allocated buffers) are not supported at the same time.
7. Handle communication with the backend:
- send requests and wait for the responses according
to the displif protocol
- serialize access to the communication channel
- time-out used for backend communication is set to 3000 ms
- manage display buffers shared with the backend
[1] https://github.com/xen-troops/displ_be
[2] https://github.com/xen-troops/libxenbe
[3] https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=docs/man/xl.cfg.pod.5.in;h=a699367779e2ae1212ff8f638eff0206ec1a1cc9;hb=refs/heads/master#l1257
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20180403112317.28751-2-andr2000@gmail.com
2018-04-03 14:23:17 +03:00
|
|
|
source "drivers/gpu/drm/xen/Kconfig"
|
|
|
|
|
|
2019-03-04 17:47:24 +01:00
|
|
|
source "drivers/gpu/drm/vboxvideo/Kconfig"
|
|
|
|
|
|
2019-03-09 20:20:12 +08:00
|
|
|
source "drivers/gpu/drm/lima/Kconfig"
|
|
|
|
|
|
2018-09-10 14:27:58 -05:00
|
|
|
source "drivers/gpu/drm/panfrost/Kconfig"
|
|
|
|
|
|
2019-04-03 10:49:08 +10:30
|
|
|
source "drivers/gpu/drm/aspeed/Kconfig"
|
|
|
|
|
|
2019-05-24 11:20:19 +02:00
|
|
|
source "drivers/gpu/drm/mcde/Kconfig"
|
|
|
|
|
|
drm/tidss: New driver for TI Keystone platform Display SubSystem
This patch adds a new DRM driver for Texas Instruments DSS IPs used on
Texas Instruments Keystone K2G, AM65x, and J721e SoCs. The new DSS IP is
a major change to the older DSS IP versions, which are supported by
the omapdrm driver. While on higher level the Keystone DSS resembles
the older DSS versions, the registers are completely different and the
internal pipelines differ a lot.
DSS IP found on K2G is an "ultra-light" version, and has only a single
plane and a single output. The K3 DSS IPs are found on AM65x and J721E
SoCs. AM65x DSS has two video ports, one full video plane, and another
"lite" plane without scaling support. J721E has 4 video ports, 2 video
planes and 2 lite planes. AM65x DSS has also an integrated OLDI (LVDS)
output.
Version history:
v2: - rebased on top of drm-next-2019-11-27
- sort all include lines in all files
- remove all include <drm/drmP.h>
- remove select "select VIDEOMODE_HELPERS"
- call dispc_vp_setup() later in tidss_crtc_atomic_flush() (there is no
to call it in new modeset case as it is also called in vp_enable())
- change probe sequence and drm_device allocation (follow example in
drm_drv.c)
- use __maybe_unused instead of #ifdef for pm functions
- remove "struct drm_fbdev_cma *fbdev;" from driver data
- check panel connector type before connecting it
v3: no change
v4: no change
v5: - remove fifo underflow irq handling, it is not an error and
it should be used for debug purposes only
- memory tuning, prefetch plane fifo up to high-threshold value to
minimize possibility of underflows.
v6: - Check CTM and gamma support from dispc_features when creating crtc
- Implement CTM support for k2g and fix k3 CTM implementation
- Remove gamma property persistence and always write color properties
in a new modeset
v7: - Fix checkpatch.pl --strict issues
- Rebase on top of drm-misc-next-2020-01-10
v8: - Remove idle debug prints from dispc_init()
- Add Reviewed-by: Benoit Parrot <bparrot@ti.com>
v9: - Rename dispc_write_irqenable() to dispc_set_irqenable() to avoid
conflict exported omapfb function with same name
- Add Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Co-developed-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: Jyri Sarha <jsarha@ti.com>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Reviewed-by: Benoit Parrot <bparrot@ti.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Link: https://patchwork.freedesktop.org/patch/msgid/925fbfad58ff828e8e07fdff7073a0ee65750c3d.1580129724.git.jsarha@ti.com
2019-11-08 09:45:28 +02:00
|
|
|
source "drivers/gpu/drm/tidss/Kconfig"
|
|
|
|
|
|
2018-07-07 19:05:34 -07:00
|
|
|
source "drivers/gpu/drm/xlnx/Kconfig"
|
|
|
|
|
|
drm: Add GUD USB Display driver
This adds a USB display driver with the intention that it can be
used with future USB interfaced low end displays/adapters. The Linux
gadget device driver will serve as the canonical device implementation.
The following DRM properties are supported:
- Plane rotation
- Connector TV properties
There is also support for backlight brightness exposed as a backlight
device.
Display modes can be made available to the host driver either as DRM
display modes or through EDID. If both are present, EDID is just passed
on to userspace.
Performance is preferred over color depth, so if the device supports
RGB565, DRM_CAP_DUMB_PREFERRED_DEPTH will return 16.
If the device transfer buffer can't fit an uncompressed framebuffer
update, the update is split up into parts that do fit.
Optimal user experience is achieved by providing damage reports either by
setting FB_DAMAGE_CLIPS on pageflips or calling DRM_IOCTL_MODE_DIRTYFB.
LZ4 compression is used if the device supports it.
The driver supports a one bit monochrome transfer format: R1. This is not
implemented in the gadget driver. It is added in preparation for future
monochrome e-ink displays.
The driver is MIT licensed to smooth the path for any BSD port of the
driver.
v2:
- Use devm_drm_dev_alloc() and drmm_mode_config_init()
- drm_fbdev_generic_setup: Use preferred_bpp=0, 16 was a copy paste error
- The drm_backlight_helper is dropped, copy in the code
- Support protocol version backwards compatibility for device
v3:
- Use donated Openmoko USB pid
- Use direct compression from framebuffer when pitch matches, not only on
full frames, so split updates can benefit
- Use __le16 in struct gud_drm_req_get_connector_status
- Set edid property when the device only provides edid
- Clear compression fields in struct gud_drm_req_set_buffer
- Fix protocol version negotiation
- Remove mode->vrefresh, it's calculated
v4:
- Drop the status req polling which was a workaround for something that
turned out to be a dwc2 udc driver problem
- Add a flag for the Linux gadget to require a status request on
SET operations. Other devices will only get status req on STALL errors
- Use protocol specific error codes (Peter)
- Add a flag for devices that want to receive the entire framebuffer on
each flush (Lubomir)
- Retry a failed framebuffer flush
- If mode has changed wait for worker and clear pending damage before
queuing up new damage, fb width/height might have changed
- Increase error counter on bulk transfer failures
- Use DRM_MODE_CONNECTOR_USB
- Handle R1 kmalloc error (Peter)
- Don't try and replicate the USB get descriptor request standard for the
display descriptor (Peter)
- Make max_buffer_size optional (Peter), drop the pow2 requirement since
it's not necessary anymore.
- Don't pre-alloc a control request buffer, it was only 4k
- Let gud.h describe the whole protocol explicitly and don't let DRM
leak into it (Peter)
- Drop display mode .hskew and .vscan from the protocol
- Shorten names: s/GUD_DRM_/GUD_/ s/gud_drm_/gud_/ (Peter)
- Fix gud_pipe_check() connector picking when switching connector
- Drop gud_drm_driver_gem_create_object() cached is default now
- Retrieve USB device from struct drm_device.dev instead of keeping a
pointer
- Honour fb->offsets[0]
- Fix mode fetching when connector status is forced
- Check EDID length reported by the device
- Use drm_do_get_edid() so userspace can overrride EDID
- Set epoch counter to signal connector status change
- gud_drm_driver can be const now
v5:
- GUD_DRM_FORMAT_R1: Use non-human ascii values (Daniel)
- Change name to: GUD USB Display (Thomas, Simon)
- Change one __u32 -> __le32 in protocol header
- Always log fb flush errors, unless the previous one failed
- Run backlight update in a worker to avoid upsetting lockdep (Daniel)
- Drop backlight_ops.get_brightness, there's no readback from the device
so it doesn't really add anything.
- Set dma mask, needed by dma-buf importers
v6:
- Use obj-y in Makefile (Peter)
- Fix missing le32_to_cpu() when using GUD_DISPLAY_MAGIC (Peter)
- Set initial brightness on backlight device
v7:
- LZ4_compress_default() can return zero, check for that
- Fix memory leak in gud_pipe_check() error path (Peter)
- Improve debug and error messages (Peter)
- Don't pass length in protocol structs (Peter)
- Pass USB interface to gud_usb_control_msg() et al. (Peter)
- Improve gud_connector_fill_properties() (Peter)
- Add GUD_PIXEL_FORMAT_RGB111 (Peter)
- Remove GUD_REQ_SET_VERSION (Peter)
- Fix DRM_IOCTL_MODE_OBJ_SETPROPERTY and the rotation property
- Fix dma-buf import (Thomas)
v8:
- Forgot to filter RGB111 from reaching userspace
- Handle a device that only returns unknown device properties (Peter)
- s/GUD_PIXEL_FORMAT_RGB111/GUD_PIXEL_FORMAT_XRGB1111/ (Peter)
- Fix R1 and XRGB1111 format conversion
- Add FIXME about Big Endian being broken (Peter, Ilia)
Cc: Lubomir Rintel <lkundrak@v3.sk>
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Peter Stuge <peter@stuge.se>
Tested-by: Peter Stuge <peter@stuge.se>
Signed-off-by: Noralf Trønnes <noralf@tronnes.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20210313112545.37527-4-noralf@tronnes.org
2021-03-13 12:25:45 +01:00
|
|
|
source "drivers/gpu/drm/gud/Kconfig"
|
|
|
|
|
|
2022-02-14 14:37:07 +01:00
|
|
|
source "drivers/gpu/drm/solomon/Kconfig"
|
|
|
|
|
|
2021-12-07 22:27:13 +08:00
|
|
|
source "drivers/gpu/drm/sprd/Kconfig"
|
|
|
|
|
|
2021-05-27 04:22:28 -07:00
|
|
|
config DRM_HYPERV
|
|
|
|
|
tristate "DRM Support for Hyper-V synthetic video device"
|
|
|
|
|
depends on DRM && PCI && MMU && HYPERV
|
|
|
|
|
select DRM_KMS_HELPER
|
|
|
|
|
select DRM_GEM_SHMEM_HELPER
|
|
|
|
|
help
|
|
|
|
|
This is a KMS driver for Hyper-V synthetic video device. Choose this
|
|
|
|
|
option if you would like to enable drm driver for Hyper-V virtual
|
|
|
|
|
machine. Unselect Hyper-V framebuffer driver (CONFIG_FB_HYPERV) so
|
|
|
|
|
that DRM driver is used by default.
|
|
|
|
|
|
|
|
|
|
If M is selected the module will be called hyperv_drm.
|
|
|
|
|
|
2016-08-04 10:06:56 +02:00
|
|
|
# Keep legacy drivers last
|
|
|
|
|
|
|
|
|
|
menuconfig DRM_LEGACY
|
|
|
|
|
bool "Enable legacy drivers (DANGEROUS)"
|
2017-01-12 09:57:36 +01:00
|
|
|
depends on DRM && MMU
|
2016-08-04 10:06:56 +02:00
|
|
|
help
|
|
|
|
|
Enable legacy DRI1 drivers. Those drivers expose unsafe and dangerous
|
|
|
|
|
APIs to user-space, which can be used to circumvent access
|
|
|
|
|
restrictions and other security measures. For backwards compatibility
|
|
|
|
|
those drivers are still available, but their use is highly
|
|
|
|
|
inadvisable and might harm your system.
|
|
|
|
|
|
|
|
|
|
You are recommended to use the safe modeset-only drivers instead, and
|
|
|
|
|
perform 3D emulation in user-space.
|
|
|
|
|
|
|
|
|
|
Unless you have strong reasons to go rogue, say "N".
|
|
|
|
|
|
|
|
|
|
if DRM_LEGACY
|
2022-12-03 18:22:59 +08:00
|
|
|
# leave here to list legacy drivers
|
2016-08-04 10:06:56 +02:00
|
|
|
endif # DRM_LEGACY
|
2016-12-22 08:36:08 +00:00
|
|
|
|
2020-03-05 17:26:10 -08:00
|
|
|
config DRM_EXPORT_FOR_TESTS
|
|
|
|
|
bool
|
|
|
|
|
|
2018-01-17 09:10:32 +01:00
|
|
|
# Separate option because drm_panel_orientation_quirks.c is shared with fbdev
|
|
|
|
|
config DRM_PANEL_ORIENTATION_QUIRKS
|
|
|
|
|
tristate
|
|
|
|
|
|
2016-12-22 08:36:08 +00:00
|
|
|
config DRM_LIB_RANDOM
|
|
|
|
|
bool
|
|
|
|
|
default n
|
2021-10-05 22:23:14 +02:00
|
|
|
|
|
|
|
|
config DRM_PRIVACY_SCREEN
|
|
|
|
|
bool
|
|
|
|
|
default n
|