[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220429084253.1085911-2-javierm@redhat.com>
Date: Fri, 29 Apr 2022 10:42:43 +0200
From: Javier Martinez Canillas <javierm@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: dri-devel@...ts.freedesktop.org,
Daniel Vetter <daniel.vetter@...ll.ch>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
Javier Martinez Canillas <javierm@...hat.com>,
Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...ux.ie>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>
Subject: [RFC PATCH v4 01/11] drm: Add a capability flag for simple framebuffer drivers
The DRIVER_FIRMWARE flag denotes that a DRM driver uses a framebuffer
that was initialized and provided by the system firmware for scanout.
Signed-off-by: Javier Martinez Canillas <javierm@...hat.com>
---
(no changes since v1)
include/drm/drm_drv.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h
index f6159acb8856..abab51705e36 100644
--- a/include/drm/drm_drv.h
+++ b/include/drm/drm_drv.h
@@ -94,6 +94,12 @@ enum drm_driver_feature {
* synchronization of command submission.
*/
DRIVER_SYNCOBJ_TIMELINE = BIT(6),
+ /**
+ * @DRIVER_FIRMWARE:
+ *
+ * Denote a driver using a system framebuffer provided by the firmware.
+ */
+ DRIVER_FIRMWARE = BIT(7),
/* IMPORTANT: Below are all the legacy flags, add new ones above. */
--
2.35.1
Powered by blists - more mailing lists