Lines Matching +full:key +full:- +full:release

3  * Copyright (c) 2006-2009 VMware, Inc., Palo Alto, CA., USA
20  * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
28  * Authors: Thomas Hellstrom <thellstrom-at-vmware-dot-com>
32  * Base- and reference object implementation for the various
34  * and release on file close.
69  * Device-specific types should use the
91  * @hash: hash entry for the per-device object hash.
107  * already been taken out of the per-device hash. The parameter
112  * This function may, for example, release a lock held by a user-space
116  * are visible to user-space. It provides a global name, race-safe
161  * @key: Hash key
163  * Looks up a struct ttm_base_object with the key @key.
169 						      *tfile, uint32_t key);
193  * base object, but a user-space application holds the reference. When the
197  * When user-space takes a lock, it can add a ref object to that lock to
207  * @key: Key representing the base object.
211  * on the base object identified by @key. If there are no duplicate
216 				     unsigned long key,
220  * ttm_object_file_init - initialize a struct ttm_object file
233  * ttm_object_file_release - release data held by a ttm_object_file
235  * @p_tfile: Pointer to pointer to the ttm_object_file object to release.
239  * Typically called from file_ops::release. The caller must
246  * ttm_object device init - initialize a struct ttm_object_device
258  * ttm_object_device_release - release data held by a ttm_object_device
260  * @p_tdev: Pointer to pointer to the ttm_object_device object to release.