Lines Matching full:manager

37  * DOC: vma offset manager
39  * The vma-manager is responsible to map arbitrary driver-dependent memory
44  * Drivers shouldn't use this for object placement in VMEM. This manager should
55  * This offset manager works on page-based addresses. That is, every argument
62  * Additionally to offset management, the vma offset manager also handles access
71  * drm_vma_offset_manager_init - Initialize new offset-manager
72  * @mgr: Manager object
76  * Initialize a new offset-manager. The offset and area size available for the
77  * manager are given as @page_offset and @size. Both are interpreted as
80  * Adding/removing nodes from the manager is locked internally and protected
82  * for the caller. While calling into the vma-manager, a given node must
94  * drm_vma_offset_manager_destroy() - Destroy offset manager
95  * @mgr: Manager object
97  * Destroy an object manager which was previously created via
99  * before destroying the manager. Otherwise, drm_mm will refuse to free the
102  * The manager must not be accessed after this function is called.
112  * @mgr: Manager object
121  * Note that before lookup the vma offset manager lookup lock must be acquired
179  * drm_vma_offset_add() - Add offset node to manager
180  * @mgr: Manager object
184  * Add a node to the offset-manager. If the node was already added, this does
219  * drm_vma_offset_remove() - Remove offset node from manager
220  * @mgr: Manager object
223  * Remove a node from the offset manager. If the node wasn't added before, this
253  * not added to any offset-manager.