Lines Matching full:fence
249 you can control. <li> Allow userspace to explicitly create or signal a fence.
269 dependencies. A fence is a promise from the kernel that it gives upon accepting
276 kernel-space to user-space. For instance, a fence can contain two sync_points
278 the fence is signaled, the image producers know both consumers are done
286 Membership in the sync_fence is immutable once the fence is created. And since
287 a sync_pt can be in only one fence, it is included as a copy. Even if two
289 fence.
291 To get more than one point in a fence, a merge operation is conducted. In the
292 merge, the points from two distinct fences are added to a third fence. If one
293 of those points was signaled in the originating fence, and the other was not,
294 the third fence will also not be in a signaled state.</p>
300 a particular piece of hardware. Drivers that need to be fence-aware are
314 <code>EGL_ANDROID_wait_sync</code>, along with incorporating fence support into
332 While putting a buffer on display, you associate it with a fence that says when
334 once the fence clears.</p>
337 own fence, which is a guarantee of when the buffer will be off of the display.
343 * will display buf when fence is signaled. returns immediately with a fence
347 *fence); </pre>
362 <ul> <li> if you receive a fence file descriptor from the sync framework, you
363 must close it. <li> if you return a fence file descriptor to the sync
365 fence file descriptor, you must duplicate the descriptor. </ul>
367 <p>Every time a fence is passed through BufferQueue - such as for a window that
368 passes a fence to BufferQueue saying when its new contents will be ready - the
369 fence object is renamed. Since kernel fence support allows fences to have
371 that is being queued to name the fence, for example:
380 <p>ANativeWindow is fence aware. <code>dequeueBuffer</code>,
381 <code>queueBuffer</code>, and <code>cancelBuffer</code> have fence
389 wrap or create native Android fence file descriptors in EGLSyncKHR objects.
405 native fence EGLSync object type so extensions that apply to existing EGLSync
410 fence file descriptor attribute that can be set only at creation time and
414 <ul> <li> A valid fence file descriptor - wraps an existing native Android
415 fence file descriptor in an EGLSyncKHR object. <li> -1 - creates a native
416 Android fence file descriptor from an EGLSyncKHR object. </ul>
419 from the native Android fence file descriptor. This has the same result as
421 recipient closes the fence (hence the duplicate operation). Finally, destroying
422 the EGLSync object should close the internal fence attribute.</p>
428 <ul> <li> <em>Acquire fence</em> - one per layer, this is set before calling
430 <em>Release fence</em> - one per layer, this is filled in by the driver in
433 <em>Retire fence</em> - one per the entire frame, this is filled in by the
436 operation has completed. The retire fence signals when the next set operation
439 <p>The retire fence can be used to determine how long each frame appears on the
491 VSYNC <li> <em>Feedback</em> - Retire fence signal timestamps from Hardware
500 <p>?Smart? panels often have a delta. Retire fence is the end of direct memory
506 characteristics. Time from retire fence timestamp to HW Vsync signal is
536 Hardware Composer writes output to a buffer and provides the completion fence.
