drm/ttm: remove special handling for non GEM drivers

vmwgfx is the only driver actually using this. Move the handling into
the driver instead.

Signed-off-by: Christian König <christian.koenig@amd.com>
Acked-by: Huang Rui <ray.huang@amd.com>
Reviewed-by: Zack Rusin <zackr@vmware.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20210419092853.1605-1-christian.koenig@amd.com
This commit is contained in:
Christian König
2021-04-17 19:09:30 +02:00
parent 13ea9aa1e7
commit d02117f8ef
3 changed files with 10 additions and 30 deletions

View File

@@ -562,25 +562,6 @@ ssize_t ttm_bo_io(struct ttm_device *bdev, struct file *filp,
int ttm_bo_swapout(struct ttm_buffer_object *bo, struct ttm_operation_ctx *ctx,
gfp_t gfp_flags);
/**
* ttm_bo_uses_embedded_gem_object - check if the given bo uses the
* embedded drm_gem_object.
*
* Most ttm drivers are using gem too, so the embedded
* ttm_buffer_object.base will be initialized by the driver (before
* calling ttm_bo_init). It is also possible to use ttm without gem
* though (vmwgfx does that).
*
* This helper will figure whenever a given ttm bo is a gem object too
* or not.
*
* @bo: The bo to check.
*/
static inline bool ttm_bo_uses_embedded_gem_object(struct ttm_buffer_object *bo)
{
return bo->base.dev != NULL;
}
/**
* ttm_bo_pin - Pin the buffer object.
* @bo: The buffer object to pin