commit 7076423c4bd67ffee0ba2fbcb871b744ca86bdbe
author Hirokazu Honda <hiroh@chromium.org> Thu Oct 25 10:10:19 2018
committer Commit Bot <commit-bot@chromium.org> Thu Oct 25 10:10:19 2018
tree 06c021ca3beb662640308890d61d55880530c3c7
parent c7fbc03df13720f69ae263e815845b80c184ca58

media/video/VEA: Add storage type in VideoEncodeAccelerator Initialize Config

V4L2VEA negotiates and creates ImageProcessor in Initialize(). ImageProcessor
needs to know in what storage type of a video frame will be given in Encode().
Currently, video frame is always mapped in userspace and ImageProcessor is
created assuming it.
In the future, video frame will be given as DMA buf, in some cases, e.g., Chrome
video capture.
This adds storage type to VideoEncodeAccelerator Initialize Config, so that
ImageProcessor can know what storag type of a video frame is provided in Encode().

BUG=chromium:895230
TEST=Build chrome without any errors

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I172dede5e900856a2adcb9e6f91bcbd61cd5af44
Reviewed-on: https://chromium-review.googlesource.com/c/1280096
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#602661}