Lines Matching full:object

32  * Base- and reference object implementation for the various
52  * Describes what type of reference a ref object holds.
54  * TTM_REF_USAGE is a simple refcount on a base object.
57  * buffer object.
60  * buffer object.
74  * One entry per ttm object type.
98  * @hash: hash entry for the per-device object hash.
99  * @type: derived type this object is base class for.
100  * @shareable: Other ttm_object_files can access this object.
103  * NULL if the object was not created by a user request.
104  * (kernel object).
106  * @refcount: Number of references to this object, not
107  * including the hash entry. A reference to a base object can
108  * only be held by a ref object.
111  * no more references to this object. This function should
112  * destroy the object (or make sure destruction eventually happens),
113  * and when it is called, the object has
117  * @ref_obj_release: A function to be called when a reference object
141  * struct ttm_prime_object - Modified base object that is prime-aware
145  * @size: Size of the dma_buf associated with this object
146  * @real_type: Type of the underlying object. Needed since we're setting
149  * object.
150  * @refcount_release: The underlying object's release method. Needed since
168  * @shareable: This object is shareable with other applcations.
170  * @type: The object type.
208  * caller doesn't yet have a reference to the base object.
219  * Decrements the base object refcount and clears the pointer pointed to by
230  * @base: The base object to reference.
232  * @existed: Upon completion, indicates that an identical reference object
233  * already existed, and the refcount was upped on that object instead.
234  * @require_existed: Fail with -EPERM if an identical ref object didn't
237  * Checks that the base object is shareable and adds a ref object to it.
239  * Adding a ref object to a base object is basically like referencing the
240  * base object, but a user-space application holds the reference. When the
242  * deleted. A reference object can have different types depending on what
243  * it's intended for. It can be refcounting to prevent object destruction,
244  * When user-space takes a lock, it can add a ref object to that lock to
245  * make sure the lock is released if the application dies. A ref object
246  * will hold a single reference on a base object.
259  * @key: Key representing the base object.
260  * @ref_type: Ref type of the ref object to be dereferenced.
262  * Unreference a ref object with type @ref_type
263  * on the base object identified by @key. If there are no duplicate
264  * references, the ref object will be destroyed and the base object
287  * @p_tfile: Pointer to pointer to the ttm_object_file object to release.
316  * @p_tdev: Pointer to pointer to the ttm_object_device object to release.
357  * Extra memory required by the base object's idr storage, which is allocated
358  * separately from the base object itself. We estimate an on-average 128 bytes
367  * ttm_base_object_noref_release - release a base object pointer looked up
370  * Releases a base object pointer looked up with ttm_base_object_noref_lookup().