Lines Matching full:gem

49  * Similar to GEM global names, PRIME file descriptors are also used to share
52  * between applications, they can't be guessed like the globally unique GEM
60  * Reference Counting for GEM Drivers
66  * and stores the exporting GEM object in the &dma_buf.priv field. This
69  * GEM-based drivers, the &dma_buf should be exported using
73  * importing GEM object -> dma-buf -> exported GEM bo. A further complication
76  * is required to allow userspace to detect duplicated imports, since some GEM
83  * it will get a fd->handle request for a GEM object that it created.  Drivers
85  * dma-buf private. For GEM based drivers this is handled in
228  * drm_gem_dmabuf_export - &dma_buf export implementation for GEM
232  * This wraps dma_buf_export() for use by generic GEM drivers that are using
258  * drm_gem_dmabuf_release - &dma_buf release implementation for GEM
261  * Generic release function for dma_bufs exported as PRIME buffers. GEM drivers
279  * drm_gem_prime_fd_to_handle - PRIME import function for GEM drivers
285  * This is the PRIME import function which must be used mandatorily by GEM
286  * drivers to ensure correct lifetime management of the underlying GEM object.
287  * The actual importing of GEM object from the dma-buf is done through the
410  * drm_gem_prime_handle_to_dmabuf - PRIME export function for GEM drivers
416  * This is the PRIME export function which must be used mandatorily by GEM
417  * drivers to ensure correct lifetime management of the underlying GEM object.
418  * The actual exporting from GEM object to a dma-buf is done through the
479 	 * protection of dev->object_name_lock to ensure that a racing gem close  in drm_gem_prime_handle_to_dmabuf()
498  * drm_gem_prime_handle_to_fd - PRIME export function for GEM drivers
505  * This is the PRIME export function which must be used mandatorily by GEM
506  * drivers to ensure correct lifetime management of the underlying GEM object.
507  * The actual exporting from GEM object to a dma-buf is done through the
591  * drm_gem_map_attach - dma_buf attach implementation for GEM
629  * drm_gem_map_detach - dma_buf detach implementation for GEM
655  * drm_gem_map_dma_buf - map_dma_buf implementation for GEM
696  * drm_gem_unmap_dma_buf - unmap_dma_buf implementation for GEM
717  * drm_gem_dmabuf_vmap - dma_buf vmap implementation for GEM
736  * drm_gem_dmabuf_vunmap - dma_buf vunmap implementation for GEM
752  * drm_gem_prime_mmap - PRIME mmap function for GEM drivers
753  * @obj: GEM object
757  * the same codepath that is used for regular GEM buffer mapping on the DRM fd.
758  * The fake GEM offset is added to vma->vm_pgoff and &drm_driver->fops->mmap is
790 	/* Used by drm_gem_mmap() to lookup the GEM object */  in drm_gem_prime_mmap()
810  * drm_gem_dmabuf_mmap - dma_buf mmap implementation for GEM
909  * @obj: GEM object to export
912  * This is the implementation of the &drm_gem_object_funcs.export functions for GEM drivers
937  * checks if the DMA-BUF was exported from a GEM object belonging to @dev.
941  * Return: true if the DMA-BUF was exported from a GEM object belonging
979 		 * Importing dmabuf exported from our own gem increases  in drm_gem_prime_import_dev()
980 		 * refcount on gem itself instead of f_count of dmabuf.  in drm_gem_prime_import_dev()
1028  * This is the implementation of the gem_prime_import functions for GEM drivers
1098  * drm_prime_gem_destroy - helper to clean up a PRIME-imported GEM object
1099  * @obj: GEM object which was created from a dma-buf
1102  * This is the cleanup functions which GEM drivers need to call when they use