eb958c99f6
Use the regular fbdev helpers for framebuffer I/O instead of DRM's helpers. Armada does not use damage handling, so DRM's fbdev helpers are mere wrappers around the fbdev code. By using fbdev helpers directly within each DRM fbdev emulation, we can eventually remove DRM's wrapper functions entirely. v4: * use initializer macros for struct fb_ops v2: * use FB_IO_HELPERS option Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de> Acked-by: Sam Ravnborg <sam@ravnborg.org> Cc: Russell King <linux@armlinux.org.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20230530151228.22979-4-tzimmermann@suse.de
15 lines
589 B
Plaintext
15 lines
589 B
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
config DRM_ARMADA
|
|
tristate "DRM support for Marvell Armada SoCs"
|
|
depends on DRM && HAVE_CLK && ARM && MMU
|
|
select DRM_KMS_HELPER
|
|
select FB_IO_HELPERS if DRM_FBDEV_EMULATION
|
|
help
|
|
Support the "LCD" controllers found on the Marvell Armada 510
|
|
devices. There are two controllers on the device, each controller
|
|
supports graphics and video overlays.
|
|
|
|
This driver provides no built-in acceleration; acceleration is
|
|
performed by other IP found on the SoC. This driver provides
|
|
kernel mode setting and buffer management to userspace.
|