Lines Matching refs:buffers

87      * stream buffers before using buffers from that stream in a request.
92 * buffers for it must be freed after the configureStreams() call returns.
98 * module to allocate the gralloc buffers for each stream.
100 * Newly allocated buffers may be included in a capture request at any time
111 * all in-flight input and output buffers have been returned and their
164 * each stream, including maximum buffers, the usage flags, and the
180 * request and its associated buffers are available. In a normal preview
194 * buffers may simply provide sync fences to wait on. Multiple requests are
200 * is responsible for waiting on and closing the buffers' fences and
210 * The input/output buffers provided by the framework in each request
229 * allowed, there are 0 output buffers, etc) and capture processing
233 * stream buffers' fences and the buffer handles; the HAL must not
234 * close the fences or return these buffers with
286 * Flush all currently in-process captures and all buffers in the pipeline
290 * No buffers are required to be successfully returned, so every buffer
293 * to return valid (CAMERA3_BUFFER_STATUS_OK) buffers during this call,
315 * and processCaptureResult and buffers as normal.
319 * buffers with processCaptureResult in the error state
325 * CAMERA3_MSG_SHUTTER but won't be producing any metadata/valid buffers
327 * processCaptureResults with buffers in CAMERA3_BUFFER_STATUS_ERROR
332 * output buffers or perhaps missing metadata, the HAL must follow
343 * before any buffers/metadata are returned with
350 * 3.5. Valid buffers/metadata must be passed to the framework as
353 * 3.6. Failed buffers must be returned to the framework as described
354 * for case 2. But failed buffers do not have to follow the strict
355 * ordering valid buffers do, and may be out-of-order with respect
356 * to valid buffers. For example, if buffers A, B, C, D, E are sent,
371 * flush() must only return when there are no more outstanding buffers or