[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180918133813.1845-2-kraxel@redhat.com>
Date: Tue, 18 Sep 2018 15:38:12 +0200
From: Gerd Hoffmann <kraxel@...hat.com>
To: Kirti Wankhede <kwankhede@...dia.com>,
intel-gvt-dev@...ts.freedesktop.org,
Alex Williamson <alex.williamson@...hat.com>
Cc: kvm@...r.kernel.org, Gerd Hoffmann <kraxel@...hat.com>,
linux-kernel@...r.kernel.org (open list)
Subject: [PATCH v2 1/2] vfio: add edid api for display (vgpu) devices.
Signed-off-by: Gerd Hoffmann <kraxel@...hat.com>
---
include/uapi/linux/vfio.h | 39 +++++++++++++++++++++++++++++++++++++++
1 file changed, 39 insertions(+)
diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
index 1aa7b82e81..78e5a37d83 100644
--- a/include/uapi/linux/vfio.h
+++ b/include/uapi/linux/vfio.h
@@ -301,6 +301,45 @@ struct vfio_region_info_cap_type {
#define VFIO_REGION_SUBTYPE_INTEL_IGD_HOST_CFG (2)
#define VFIO_REGION_SUBTYPE_INTEL_IGD_LPC_CFG (3)
+#define VFIO_REGION_TYPE_PCI_GFX (1)
+#define VFIO_REGION_SUBTYPE_GFX_EDID (1)
+
+/**
+ * Set display link state and edid blob.
+ *
+ * For the edid blob spec look here:
+ * https://en.wikipedia.org/wiki/Extended_Display_Identification_Data
+ *
+ * The guest should be notified about edid changes, for example by
+ * setting the link status to down temporarely (emulate monitor
+ * hotplug).
+ *
+ * @link_state:
+ * VFIO_DEVICE_GFX_LINK_STATE_UP: Monitor is turned on.
+ * VFIO_DEVICE_GFX_LINK_STATE_DOWN: Monitor is turned off.
+ *
+ * @edid_size: Size of the edid data blob.
+ * @edid_blob: The actual edid data.
+ *
+ * Returns 0 on success, error code (such as -EINVAL) on failure.
+ */
+struct vfio_region_gfx_edid {
+ /* device capability hints (read only) */
+ __u32 max_xres;
+ __u32 max_yres;
+ __u32 __reserved1[6];
+
+ /* device state (read/write) */
+ __u32 link_state;
+#define VFIO_DEVICE_GFX_LINK_STATE_UP 1
+#define VFIO_DEVICE_GFX_LINK_STATE_DOWN 2
+ __u32 edid_size;
+ __u32 __reserved2[6];
+
+ /* edid blob (read/write) */
+ __u8 edid_blob[512];
+};
+
/*
* The MSIX mappable capability informs that MSIX data of a BAR can be mmapped
* which allows direct access to non-MSIX registers which happened to be within
--
2.9.3
Powered by blists - more mailing lists