Lines Matching defs:buffer
50 // of the buffer in virtual memory. The caller should only access/modify the
55 // buffer.
58 // Gets a blob buffer that was created with BufferProducer::CreateBlob.
63 // Gets a blob buffer that was created with BufferProducer::CreateBlob.
71 // memory gralloc buffers to GPU buffer objects.
73 // Current GPU vendor puts the buffer allocation in one FD. If we change GPU
76 // a GL context in the pose service to allocate this buffer or to use the
107 IonBuffer* buffer() { return &buffer_; }
108 const IonBuffer* buffer() const { return &buffer_; }
112 // Returns the buffer buffer state.
115 // A state mask which is unique to a buffer hub client among all its siblings
116 // sharing the same concrete graphic buffer.
119 // The following methods return settings of the first buffer. Currently,
120 // it is only possible to create multi-buffer BufferHubBuffers with the same
169 // Global id for the buffer that is consistent across processes. It is meant
178 // This represents a writable buffer. Calling Post notifies all clients and
179 // makes the buffer read-only. Call Gain to acquire write access. A buffer
185 // metadata when acquiring the buffer. The API guarantees that a Post() with a
196 // Asynchronously posts a buffer. The fence and metadata are passed to
201 // Post this buffer, passing |ready_fence| to the consumers. The bytes in
203 // the buffer until it is re-gained.
219 // Attempt to re-gain the buffer for writing. If |release_fence| is valid, it
220 // must be waited on before using the buffer. If it is not valid then the
221 // buffer is free for immediate use. This call will only succeed if the buffer
227 // Asynchronously marks a released buffer as gained. This method is similar to
231 // the buffer is in an incorrect state. Returns zero if sending the message
236 // be called when a producer buffer has exclusive access to the buffer (i.e.
238 // LocalChannelHandle representing a detached buffer will be returned and all
250 // Constructs a buffer with the given geometry and parameters.
254 // Constructs a blob (flat) buffer with the given usage flags.
266 // This is a connection to a producer buffer, which can be located in another
267 // application. When that buffer is Post()ed, this fd will be signaled and
279 // Attempt to retrieve a post event from buffer hub. If successful,
280 // |ready_fence| will be set to a fence to wait on until the buffer is ready.
288 // Attempt to retrieve a post event from buffer hub. If successful,
289 // |ready_fence| is set to a fence signaling that the contents of the buffer
290 // are available. This call will only succeed if the buffer is in the posted
295 // Attempt to retrieve a post event from buffer hub. If successful,
296 // |ready_fence| is set to a fence to wait on until the buffer is ready. This
308 // valid the fence determines the buffer usage, otherwise the buffer is
314 // Asynchronously releases a buffer. Similar to the synchronous version above,
322 // does not need to access the buffer this cycle. This returns zero or a
326 // When set, this consumer is no longer notified when this buffer is
328 // whenever the buffer is posted. If ignore is set to true while a buffer is