video_VideoEncodeAccelerator: Start NV12 test cases on intel devices
crrev.com/c/1293254 enables VaapiVEA to encode NV12 input buffers.
This starts to run NV12 test cases on intel devices.
BUG=chromium:894381
TEST=video_VideoEncodeAccelerator.h264.bvt on eve
Change-Id: I99b1ba36b8d700475fdaffce6befb634bf9dbe43
Reviewed-on: https://chromium-review.googlesource.com/1297874
Commit-Ready: Hirokazu Honda <hiroh@chromium.org>
Tested-by: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Chih-Yu Huang <akahuang@chromium.org>
diff --git a/client/site_tests/video_VideoEncodeAccelerator/video_VideoEncodeAccelerator.py b/client/site_tests/video_VideoEncodeAccelerator/video_VideoEncodeAccelerator.py
index c4216ae..3e4d1fc 100644
--- a/client/site_tests/video_VideoEncodeAccelerator/video_VideoEncodeAccelerator.py
+++ b/client/site_tests/video_VideoEncodeAccelerator/video_VideoEncodeAccelerator.py
@@ -93,14 +93,6 @@
There are devices that cannot encode NV12 input buffer because of chromium
code base or driver issue.
"""
-
- # TODO(crbug.com/894381): Remove this once VaapiVEA supports
- # non I420 pixel format.
- # Skip NV12 input buffer case, VaapiVEA doesn't support YUV
- # format except I420.
- if _run_on_intel_cpu():
- return False
-
# Although V4L2VEA supports NV12, some devices cannot encode NV12 probably
# due to a driver issue.
nv12_black_list = [