Lines Matching full:gem

45  * Similar to GEM global names, PRIME file descriptors are also used to share
48  * between applications, they can't be guessed like the globally unique GEM
53  * GEM based drivers must use drm_gem_prime_handle_to_fd() and
54  * drm_gem_prime_fd_to_handle() to implement these. For GEM based drivers the
58  * &dma_buf_ops implementations for GEM drivers are all individually exported
61  * Reference Counting for GEM Drivers
67  * and stores the exporting GEM object in the &dma_buf.priv field. This
70  * GEM-based drivers, the &dma_buf should be exported using
74  * importing GEM object -> dma-buf -> exported GEM bo. A further complication
77  * is required to allow userspace to detect duplicated imports, since some GEM
84  * it will get a fd->handle request for a GEM object that it created.  Drivers
86  * dma-buf private. For GEM based drivers this is handled in
233  * drm_gem_dmabuf_export - &dma_buf export implementation for GEM
237  * This wraps dma_buf_export() for use by generic GEM drivers that are using
263  * drm_gem_dmabuf_release - &dma_buf release implementation for GEM
266  * Generic release function for dma_bufs exported as PRIME buffers. GEM drivers
284  * drm_gem_prime_fd_to_handle - PRIME import function for GEM drivers
290  * This is the PRIME import function which must be used mandatorily by GEM
291  * drivers to ensure correct lifetime management of the underlying GEM object.
292  * The actual importing of GEM object from the dma-buf is done through the
416  * drm_gem_prime_handle_to_fd - PRIME export function for GEM drivers
423  * This is the PRIME export function which must be used mandatorily by GEM
424  * drivers to ensure correct lifetime management of the underlying GEM object.
425  * The actual exporting from GEM object to a dma-buf is done through the
478 	 * protection of dev->object_name_lock to ensure that a racing gem close  in drm_gem_prime_handle_to_fd()
492 	 * and that is invariant as long as a userspace gem handle exists.  in drm_gem_prime_handle_to_fd()
570  * drm_gem_map_attach - dma_buf attach implementation for GEM
590  * drm_gem_map_detach - dma_buf detach implementation for GEM
608  * drm_gem_map_dma_buf - map_dma_buf implementation for GEM
647  * drm_gem_unmap_dma_buf - unmap_dma_buf implementation for GEM
668  * drm_gem_dmabuf_vmap - dma_buf vmap implementation for GEM
690  * drm_gem_dmabuf_vunmap - dma_buf vunmap implementation for GEM
706  * drm_gem_prime_mmap - PRIME mmap function for GEM drivers
707  * @obj: GEM object
711  * the same codepath that is used for regular GEM buffer mapping on the DRM fd.
712  * The fake GEM offset is added to vma->vm_pgoff and &drm_driver->fops->mmap is
744 	/* Used by drm_gem_mmap() to lookup the GEM object */  in drm_gem_prime_mmap()
764  * drm_gem_dmabuf_mmap - dma_buf mmap implementation for GEM
873  * @obj: GEM object to export
876  * This is the implementation of the &drm_gem_object_funcs.export functions for GEM drivers
925 			 * Importing dmabuf exported from out own gem increases  in drm_gem_prime_import_dev()
926 			 * refcount on gem itself instead of f_count of dmabuf.  in drm_gem_prime_import_dev()
974  * This is the implementation of the gem_prime_import functions for GEM drivers
1030  * drm_prime_gem_destroy - helper to clean up a PRIME-imported GEM object
1031  * @obj: GEM object which was created from a dma-buf
1034  * This is the cleanup functions which GEM drivers need to call when they use