Lines Matching full:drivers

23 identified common code between drivers and created a support library to
31 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_module.c
43 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_device.c
58 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_resource.c
67 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_tt.c
76 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_pool.c
85 operations to userspace and a set of helper functions to drivers, and
86 let drivers implement hardware-specific operations with their own
119 Drivers that use GEM must set the DRIVER_GEM bit in the struct
126 In a KMS configuration, drivers need to allocate and initialize a
141 drm_gem_object <drm_gem_object>`. Drivers usually need to
160 Drivers are responsible for the actual physical pages allocation by
169 often the case in embedded devices. Drivers can create GEM objects with
172 private GEM objects must be managed by drivers.
183 operation. That operation is mandatory for GEM-enabled drivers and must
186 void (\*free) (struct drm_gem_object \*obj); Drivers are
205 To create a handle for a GEM object drivers call drm_gem_handle_create(). The
207 locally unique handle.  When the handle is no longer needed drivers delete it
213 avoid leaking GEM objects, drivers must make sure they drop the
218 drivers must drop the initial reference to the GEM object before
230 PRIME. GEM-based drivers must use the provided helpers functions to
252 dubious, seems to be discouraged for new GEM-enabled drivers, and will
259 object must thus be associated with a fake offset. To do so, drivers
274 To use drm_gem_mmap(), drivers must fill the struct :c:type:`struct drm_driver
290 count. Drivers can use the drm_gem_vm_open() and drm_gem_vm_close() helper
295 allocation scheme, drivers can allocate pages at fault time, or can
299 Drivers that want to map the GEM object upfront instead of handling page
306 To use drm_gem_dma_get_unmapped_area(), drivers must fill the struct
355 .. kernel-doc:: drivers/gpu/drm/drm_gem.c
361 .. kernel-doc:: drivers/gpu/drm/drm_gem_dma_helper.c
367 .. kernel-doc:: drivers/gpu/drm/drm_gem_dma_helper.c
373 .. kernel-doc:: drivers/gpu/drm/drm_gem_shmem_helper.c
379 .. kernel-doc:: drivers/gpu/drm/drm_gem_shmem_helper.c
385 .. kernel-doc:: drivers/gpu/drm/drm_gem_vram_helper.c
391 .. kernel-doc:: drivers/gpu/drm/drm_gem_vram_helper.c
397 .. kernel-doc:: drivers/gpu/drm/drm_gem_ttm_helper.c
400 .. kernel-doc:: drivers/gpu/drm/drm_gem_ttm_helper.c
406 .. kernel-doc:: drivers/gpu/drm/drm_vma_manager.c
412 .. kernel-doc:: drivers/gpu/drm/drm_vma_manager.c
427 .. kernel-doc:: drivers/gpu/drm/drm_prime.c
433 .. kernel-doc:: drivers/gpu/drm/drm_prime.c
442 .. kernel-doc:: drivers/gpu/drm/drm_prime.c
451 .. kernel-doc:: drivers/gpu/drm/drm_mm.c
457 .. kernel-doc:: drivers/gpu/drm/drm_mm.c
466 .. kernel-doc:: drivers/gpu/drm/drm_mm.c
477 .. kernel-doc:: drivers/gpu/drm/drm_gpuvm.c
483 .. kernel-doc:: drivers/gpu/drm/drm_gpuvm.c
491 .. kernel-doc:: drivers/gpu/drm/drm_gpuvm.c
497 .. kernel-doc:: drivers/gpu/drm/drm_gpuvm.c
506 .. kernel-doc:: drivers/gpu/drm/drm_gpuvm.c
515 .. kernel-doc:: drivers/gpu/drm/drm_buddy.c
521 .. kernel-doc:: drivers/gpu/drm/drm_cache.c
529 .. kernel-doc:: drivers/gpu/drm/drm_syncobj.c
535 .. kernel-doc:: drivers/gpu/drm/drm_syncobj.c
541 .. kernel-doc:: drivers/gpu/drm/drm_exec.c
547 .. kernel-doc:: drivers/gpu/drm/drm_exec.c
556 .. kernel-doc:: drivers/gpu/drm/scheduler/sched_main.c
562 .. kernel-doc:: drivers/gpu/drm/scheduler/sched_main.c
571 .. kernel-doc:: drivers/gpu/drm/scheduler/sched_main.c
574 .. kernel-doc:: drivers/gpu/drm/scheduler/sched_entity.c