drm/vmwgfx/ttm_object.h

32  * Base- and reference object implementation for the various
50  * One entry per ttm object type.
73  * @hash: hash entry for the per-device object hash.
74  * @type: derived type this object is base class for.
75  * @shareable: Other ttm_object_files can access this object.
78  * NULL if the object was not created by a user request.
79  * (kernel object).
81  * @refcount: Number of references to this object, not
82  * including the hash entry. A reference to a base object can
83  * only be held by a ref object.
86  * no more references to this object. This function should
87  * destroy the object (or make sure destruction eventually happens),
88  * and when it is called, the object has
92  * @ref_obj_release: A function to be called when a reference object
114  * struct ttm_prime_object - Modified base object that is prime-aware
118  * @size: Size of the dma_buf associated with this object
119  * @real_type: Type of the underlying object. Needed since we're setting
122  * object.
123  * @refcount_release: The underlying object's release method. Needed since
141  * @shareable: This object is shareable with other applications.
143  * @type: The object type.
177  * caller doesn't yet have a reference to the base object.
188  * Decrements the base object refcount and clears the pointer pointed to by
199  * @base: The base object to reference.
201  * @existed: Upon completion, indicates that an identical reference object
202  * already existed, and the refcount was upped on that object instead.
203  * @require_existed: Fail with -EPERM if an identical ref object didn't
206  * Checks that the base object is shareable and adds a ref object to it.
208  * Adding a ref object to a base object is basically like referencing the
209  * base object, but a user-space application holds the reference. When the
211  * deleted. A reference object can have different types depending on what
212  * it's intended for. It can be refcounting to prevent object destruction,
213  * When user-space takes a lock, it can add a ref object to that lock to
214  * make sure the lock is released if the application dies. A ref object
215  * will hold a single reference on a base object.
225  * @key: Key representing the base object.
226  * @ref_type: Ref type of the ref object to be dereferenced.
228  * Unreference a ref object with type @ref_type
229  * on the base object identified by @key. If there are no duplicate
230  * references, the ref object will be destroyed and the base object
250  * @p_tfile: Pointer to pointer to the ttm_object_file object to release.
275  * @p_tdev: Pointer to pointer to the ttm_object_device object to release.