New issue
Advanced search Search tips

Issue 917798 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature

Blocked on:
issue 907767



Sign in to add a comment

Remove image_processor_device_ from V4L2VideoDecodeAccelerator

Project Member Reported by deanliao@chromium.org, Dec 26

Issue description

Currently V4L2VideoDecodeAccelerator has a V4L2Device instance, which is stored in |image_processor_device_| member variable, designed for V4L2ImageProcessor to use. And it is used before V4L2ImageProcessor is created so we cannot create an V4L2Device instance in V4L2ImageProcessor factory method. Instead V4L2ImageProcessor has to obtain V4L2Device instance from its caller.

To make V4L2VideoDecodeAccelerator use platform agnostic method, ImageProcessorFactory::Create(), to obtain image processor, we shall remove |image_processor_device_| from V4L2VideoDecodeAccelerator.
 
Blockedon: 907767
I considered this and WIP CL is crrev.com/c/1391653.
ImageProcessor needs to run on IMPORT mode for this, crbug.com/907767.

Sign in to add a comment