Lines Matching full:gem
48 * Similar to GEM global names, PRIME file descriptors are also used to share
51 * between applications, they can't be guessed like the globally unique GEM
56 * GEM based drivers must use drm_gem_prime_handle_to_fd() and
57 * drm_gem_prime_fd_to_handle() to implement these. For GEM based drivers the
61 * &dma_buf_ops implementations for GEM drivers are all individually exported
64 * Reference Counting for GEM Drivers
70 * and stores the exporting GEM object in the &dma_buf.priv field. This
73 * GEM-based drivers, the &dma_buf should be exported using
77 * importing GEM object -> dma-buf -> exported GEM bo. A further complication
80 * is required to allow userspace to detect duplicated imports, since some GEM
87 * it will get a fd->handle request for a GEM object that it created. Drivers
89 * dma-buf private. For GEM based drivers this is handled in
236 * drm_gem_dmabuf_export - &dma_buf export implementation for GEM
240 * This wraps dma_buf_export() for use by generic GEM drivers that are using
266 * drm_gem_dmabuf_release - &dma_buf release implementation for GEM
269 * Generic release function for dma_bufs exported as PRIME buffers. GEM drivers
287 * drm_gem_prime_fd_to_handle - PRIME import function for GEM drivers
293 * This is the PRIME import function which must be used mandatorily by GEM
294 * drivers to ensure correct lifetime management of the underlying GEM object.
295 * The actual importing of GEM object from the dma-buf is done through the
417 * drm_gem_prime_handle_to_fd - PRIME export function for GEM drivers
424 * This is the PRIME export function which must be used mandatorily by GEM
425 * drivers to ensure correct lifetime management of the underlying GEM object.
426 * 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_fd()
493 * and that is invariant as long as a userspace gem handle exists. in drm_gem_prime_handle_to_fd()
571 * drm_gem_map_attach - dma_buf attach implementation for GEM
591 * drm_gem_map_detach - dma_buf detach implementation for GEM
609 * drm_gem_map_dma_buf - map_dma_buf implementation for GEM
650 * drm_gem_unmap_dma_buf - unmap_dma_buf implementation for GEM
671 * 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
746 /* Used by drm_gem_mmap() to lookup the GEM object */ in drm_gem_prime_mmap()
766 * drm_gem_dmabuf_mmap - dma_buf mmap implementation for GEM
874 * @obj: GEM object to export
877 * This is the implementation of the &drm_gem_object_funcs.export functions for GEM drivers
926 * Importing dmabuf exported from out own gem increases in drm_gem_prime_import_dev()
927 * refcount on gem itself instead of f_count of dmabuf. in drm_gem_prime_import_dev()
975 * This is the implementation of the gem_prime_import functions for GEM drivers
1045 * drm_prime_gem_destroy - helper to clean up a PRIME-imported GEM object
1046 * @obj: GEM object which was created from a dma-buf
1049 * This is the cleanup functions which GEM drivers need to call when they use