uapi/drm/drm.h

94  * backwards-compatibility reasons.
125  * The lock structure is a simple cache-line aligned integer.  To avoid
146 	char __user *date;	  /**< User-space buffer to hold date */
148 	char __user *desc;	  /**< User-space buffer to hold desc */
162 	int count;		  /**< Length of user-space structures */
201 	_DRM_RESTRICTED = 0x01,	     /**< Cannot be mapped to user-virtual */
205 	_DRM_WRITE_COMBINING = 0x10, /**< use write-combining if available */
227 	void *handle;		 /**< User-space: "Handle" to pass to mmap() */
228 				 /**< Kernel-space: kernel-virtual address */
254 	_DRM_STAT_COUNT,	/**< Generic non-byte counter (1000/k) */
285 	   -- they will be used to support the
286 	   full-screen DGA-like mode. */
315 				       * been processed by the hardware --
326 	_DRM_DMA_SMALLER_OK = 0x20,   /**< Smaller-than-requested buffers OK */
327 	_DRM_DMA_LARGER_OK = 0x40     /**< Larger-than-requested buffers OK */
345 		_DRM_PCI_BUFFER_RO = 0x10 /**< Map PCI DMA buffer read-only */
389 	void __user *virtual;		/**< Mmap'd area in user-virtual */
480 	/* bits 1-6 are reserved for high crtcs */
485 	_DRM_VBLANK_SECONDARY = 0x20000000,	/**< Secondary display controller */
545 	unsigned long size;	/**< In bytes -- will round to page boundary */
558 	unsigned long offset;	/**< In bytes -- will round to page boundary */
586 	unsigned long size;	/**< In bytes -- will round to page boundary */
679  * PRIME buffers are exposed as dma-buf file descriptors.
717  * page-flips.
727  * Note that the cross-driver contract is to merely return a valid size;
821  * If the driver doesn't support atomic mode-setting, enabling this capability
822  * will fail with -EOPNOTSUPP.
825  * kernel version 4.2, this capability is always supported for atomic-capable
848  * This capability is always supported for atomic-capable drivers starting from
856  * Drivers for para-virtualized hardware (e.g. vmwgfx, qxl, virtio and
869  * cursor planes (i.e. non-virtualized drivers) will return
873  * This capability is always supported for atomic-capable virtualized
889 	/** Flags.. only applicable for handle->fd */
939 	 * @deadline_nsec - fence deadline hint
941 	 * Deadline hint, in absolute CLOCK_MONOTONIC, to set on backing
959 	 * @deadline_nsec - fence deadline hint
961 	 * Deadline hint, in absolute CLOCK_MONOTONIC, to set on backing
1014  * when the first pixel of the refresh cycle leaves the display engine
1015  * for the display
1053  * DRM_IOCTL_GEM_CLOSE - Close a GEM handle.
1055  * GEM handles are not reference-counted by the kernel. User-space is
1056  * responsible for managing their lifetime. For example, if user-space imports
1058  * handle is returned by both imports, and user-space needs to ensure
1106  * DRM_IOCTL_PRIME_HANDLE_TO_FD - Convert a GEM handle to a DMA-BUF FD.
1108  * User-space sets &drm_prime_handle.handle with the GEM handle to export and
1109  * &drm_prime_handle.flags, and gets back a DMA-BUF file descriptor in
1112  * The export can fail for any driver-specific reason, e.g. because export is
1115  * Support for exporting DMA-BUFs is advertised via &DRM_PRIME_CAP_EXPORT.
1119  * DRM_IOCTL_PRIME_FD_TO_HANDLE - Convert a DMA-BUF FD to a GEM handle.
1121  * User-space sets &drm_prime_handle.fd with a DMA-BUF file descriptor to
1125  * If an existing GEM handle refers to the memory object backing the DMA-BUF,
1126  * that GEM handle is returned. Therefore user-space which needs to handle
1127  * arbitrary DMA-BUFs must have a user-space lookup data structure to manually
1128  * reference-count duplicated GEM handles. For more information see
1131  * The import can fail for any driver-specific reason, e.g. because import is
1132  * only supported for DMA-BUFs allocated on this DRM device.
1134  * Support for importing DMA-BUFs is advertised via &DRM_PRIME_CAP_IMPORT.
1174  * DRM_IOCTL_MODE_RMFB - Remove a framebuffer.
1179  * Warning: removing a framebuffer currently in-use on an enabled plane will
1188  * DRM_IOCTL_MODE_CREATE_DUMB - Create a new dumb buffer object.
1192  * not suitable for hardware-accelerated rendering nor video decoding. KMS dumb
1199  * User-space is expected to create a KMS dumb buffer via this IOCTL, then add
1240  * DRM_IOCTL_MODE_GETFB2 - Get framebuffer metadata.
1242  * This queries metadata about a framebuffer. User-space fills
1252  * memory object. Planes are valid until one has a zero handle -- this can be
1260  * modifier. Otherwise, user-space must ignore &drm_mode_fb_cmd2.modifier.
1262  * To obtain DMA-BUF FDs for each plane without leaking GEM handles, user-space
1265  * double-close handles which are specified multiple times in the array.
1272  * DRM_IOCTL_MODE_CLOSEFB - Close a framebuffer.
1283  * This is useful to implement flicker-free transitions between two processes.
1285  * Depending on the threat model, user-space may want to ensure that the
1303  * struct drm_event - Header for DRM events
1307  * This struct is a header for events written back to user-space on the DRM FD.
1312  * Event types 0 - 0x7fffffff are generic DRM events, 0x80000000 and
1322  * DRM_EVENT_VBLANK - vertical blanking event
1331  * DRM_EVENT_FLIP_COMPLETE - page-flip completion event
1333  * This event is sent in response to an atomic commit or legacy page-flip with
1340  * DRM_EVENT_CRTC_SEQUENCE - CRTC sequence event
1358  * of the refresh cycle leaves the display engine for the display