Searched refs:updates (Results 1 – 18 of 18) sorted by relevance
14 on an "as-is" basis. No further updates to this software should be15 expected. Although updates may occur, no commitment exists.
21 to evolve, so minor updates are needed to keep in sync with binary
23 Simultaneous output updates X X
41 More specific information and updates are available from
210 struct fence *updates) in amdgpu_vm_flush() argument219 else if (!updates) in amdgpu_vm_flush()222 is_later = fence_is_later(updates, flushed_updates); in amdgpu_vm_flush()227 vm_id->flushed_updates = fence_get(updates); in amdgpu_vm_flush()
990 struct fence *updates);
45 More specific information and updates are available from
238 int ring, struct radeon_fence *updates) in radeon_vm_flush() argument244 radeon_fence_is_earlier(vm_id->flushed_updates, updates)) { in radeon_vm_flush()248 vm_id->flushed_updates = radeon_fence_ref(updates); in radeon_vm_flush()
58 bool "BTT: Block Translation Table (atomic sector updates)"
73 More specific information and updates are available from
146 standard. It is used, for example, by automatic firmware updates used
129 More specific information and updates are available from
153 This driver updates the state panel (LED and/or LCD) upon system
38 bool "Load CIS updates from userspace"
93 You can also check for updates at <http://pegasus2.sourceforge.net/>.
2373 serial updates, reducing the number of possible frames per second.2381 concurrent updates, making higher frames per second possible.
791 updates are done via IPC calls to the system controller FW.
328 * list updates. We also record the SCB's