android: camera_stream: Plumb process() with Camera3RequestDescriptor
Data (or broader context) required for post processing of a camera request is saved via Camera3RequestDescriptor. Instead of passing individual arguments to CameraStream::process(), pass the Camera3RequestDescriptor pointer to it. All the arguments necessary to run the post-processor can be accessed from the descriptor. Signed-off-by: Umang Jain <umang.jain@ideasonboard.com> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Jacopo Mondi <jacopo@jmondi.org> Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
This commit is contained in:
parent
1abdcf803d
commit
1976179623
8 changed files with 15 additions and 20 deletions
|
@ -144,8 +144,7 @@ int CameraStream::waitFence(int fence)
|
|||
|
||||
int CameraStream::process(const FrameBuffer &source,
|
||||
camera3_stream_buffer_t &camera3Dest,
|
||||
const CameraMetadata &requestMetadata,
|
||||
CameraMetadata *resultMetadata)
|
||||
Camera3RequestDescriptor *request)
|
||||
{
|
||||
/* Handle waiting on fences on the destination buffer. */
|
||||
int fence = camera3Dest.acquire_fence;
|
||||
|
@ -175,7 +174,7 @@ int CameraStream::process(const FrameBuffer &source,
|
|||
return -EINVAL;
|
||||
}
|
||||
|
||||
return postProcessor_->process(source, &dest, requestMetadata, resultMetadata);
|
||||
return postProcessor_->process(source, &dest, request);
|
||||
}
|
||||
|
||||
FrameBuffer *CameraStream::getBuffer()
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue