(NotForReview) Enable YUV video overlay on Skylake ChromeOS.

(NotForReview) Enable YUV video overlay on Skylake ChromeOS.

Add YUYV (i.e YUY2) for video decoder output and using those formats for
overlay

YUYV is only format supported by all linux stack such as kernel, mesa, and
minigbm, so ChromeOS IA prefer to use YUYV for video decoding.

This CL changes
1. make gpu decoder (only vaapi) decode on YUYV plane
2. make --enable-gpu-memory-buffer-video-frames choose YUYV if possible
3. make Ozone GBM prefer YUYV rather than UYUV

About 1, check the change of media/gpu/vaapi_video_decode_accelerator.cc
About 2, check the change of content/renderer/media/renderer_gpu_video_accelerator_factories.cc and gpu/command_buffer/service/feature_info.cc
About 3, check the change of ui/ozone/platform/drm/gpu/drm_overlay_validator.cc

This CL is based on Johnson Lin's implementaion
https://codereview.chromium.org/2636433003/

Test results of power consumption: 8.8% power save. Check more detail in crbug.com/683347

BUG=683347
TEST=run relevant unittests
run chrome on http://www.quirksmode.org/html5/tests/video.html with all possible configurations
* decoding configuration
 * gpu decoding: N/A
 * pure software decoding: --disable-accelerated-video-decode
 * GMB video frame: --disable-accelerated-video-decode --enable-native-gpu-memory-buffers --enable-gpu-memory-buffer-video-frames
* overlay configurations
 * atomic mode setting: --enable-hardware-overlays --enable-drm-atomic
 * legacy mode setting: --enable-hardware-overlays
 * no overlay: N/A
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

[dshwang, 2017-02-09 04:48:43]

Description was changed from

==========
(NotForReview) Enable YUV video overlay on Skylake ChromeOS.

Add YUYV (i.e YUY2) for video decoder output and using those formats for
overlay

YUYV is only format supported by all linux stack such as kernel, mesa, and
minigbm, so ChromeOS IA prefer to use YUYV for video decoding.

This CL changes
1. make gpu decoder (only vaapi) decode on YUYV plane
2. make --enable-gpu-memory-buffer-video-frames choose YUYV if possible
3. make Ozone GBM prefer YUYV rather than UYUV

About 1, check the change of media/gpu/vaapi_video_decode_accelerator.cc
About 2, check the change of
content/renderer/media/renderer_gpu_video_accelerator_factories.cc and
gpu/command_buffer/service/feature_info.cc
About 3, check the change of ui/ozone/platform/drm/gpu/drm_overlay_validator.cc

This CL is based on Johnson Lin's implementaion
https://codereview.chromium.org/2636433003/

Test results of power consumption: 8.8% power save. Check more detail in
crbug.com/683347

BUG=683347
TEST=run relevant unittests
run chrome on http://www.quirksmode.org/html5/tests/video.html with all possible
configurations
* decoding configuration
 * gpu decoding: N/A
 * pure software decoding: --disable-accelerated-video-decode
 * GMB video frame: --disable-accelerated-video-decode
--enable-native-gpu-memory-buffers --enable-gpu-memory-buffer-video-frames
* overlay configurations
 * atomic mode setting: --enable-hardware-overlays --enable-drm-atomic
 * legacy mode setting: --enable-hardware-overlays
 * no overlay: N/A
==========

to

==========
(NotForReview) Enable YUV video overlay on Skylake ChromeOS.

Add YUYV (i.e YUY2) for video decoder output and using those formats for
overlay

YUYV is only format supported by all linux stack such as kernel, mesa, and
minigbm, so ChromeOS IA prefer to use YUYV for video decoding.

This CL changes
1. make gpu decoder (only vaapi) decode on YUYV plane
2. make --enable-gpu-memory-buffer-video-frames choose YUYV if possible
3. make Ozone GBM prefer YUYV rather than UYUV

About 1, check the change of media/gpu/vaapi_video_decode_accelerator.cc
About 2, check the change of
content/renderer/media/renderer_gpu_video_accelerator_factories.cc and
gpu/command_buffer/service/feature_info.cc
About 3, check the change of ui/ozone/platform/drm/gpu/drm_overlay_validator.cc

This CL is based on Johnson Lin's implementaion
https://codereview.chromium.org/2636433003/

Test results of power consumption: 8.8% power save. Check more detail in
crbug.com/683347

BUG=683347
TEST=run relevant unittests
run chrome on http://www.quirksmode.org/html5/tests/video.html with all possible
configurations
* decoding configuration
 * gpu decoding: N/A
 * pure software decoding: --disable-accelerated-video-decode
 * GMB video frame: --disable-accelerated-video-decode
--enable-native-gpu-memory-buffers --enable-gpu-memory-buffer-video-frames
* overlay configurations
 * atomic mode setting: --enable-hardware-overlays --enable-drm-atomic
 * legacy mode setting: --enable-hardware-overlays
 * no overlay: N/A
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[dshwang, 2017-02-09 04:48:46]

Description was changed from

==========
(NotForReview) Enable YUV video overlay on Skylake ChromeOS.

Add YUYV (i.e YUY2) for video decoder output and using those formats for
overlay

YUYV is only format supported by all linux stack such as kernel, mesa, and
minigbm, so ChromeOS IA prefer to use YUYV for video decoding.

This CL changes
1. make gpu decoder (only vaapi) decode on YUYV plane
2. make --enable-gpu-memory-buffer-video-frames choose YUYV if possible
3. make Ozone GBM prefer YUYV rather than UYUV

About 1, check the change of media/gpu/vaapi_video_decode_accelerator.cc
About 2, check the change of
content/renderer/media/renderer_gpu_video_accelerator_factories.cc and
gpu/command_buffer/service/feature_info.cc
About 3, check the change of ui/ozone/platform/drm/gpu/drm_overlay_validator.cc

This CL is based on Johnson Lin's implementaion
https://codereview.chromium.org/2636433003/

Test results of power consumption: 8.8% power save. Check more detail in
crbug.com/683347

BUG=683347
TEST=run relevant unittests
run chrome on http://www.quirksmode.org/html5/tests/video.html with all possible
configurations
* decoding configuration
 * gpu decoding: N/A
 * pure software decoding: --disable-accelerated-video-decode
 * GMB video frame: --disable-accelerated-video-decode
--enable-native-gpu-memory-buffers --enable-gpu-memory-buffer-video-frames
* overlay configurations
 * atomic mode setting: --enable-hardware-overlays --enable-drm-atomic
 * legacy mode setting: --enable-hardware-overlays
 * no overlay: N/A
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

to

==========
(NotForReview) Enable YUV video overlay on Skylake ChromeOS.

Add YUYV (i.e YUY2) for video decoder output and using those formats for
overlay

YUYV is only format supported by all linux stack such as kernel, mesa, and
minigbm, so ChromeOS IA prefer to use YUYV for video decoding.

This CL changes
1. make gpu decoder (only vaapi) decode on YUYV plane
2. make --enable-gpu-memory-buffer-video-frames choose YUYV if possible
3. make Ozone GBM prefer YUYV rather than UYUV

About 1, check the change of media/gpu/vaapi_video_decode_accelerator.cc
About 2, check the change of
content/renderer/media/renderer_gpu_video_accelerator_factories.cc and
gpu/command_buffer/service/feature_info.cc
About 3, check the change of ui/ozone/platform/drm/gpu/drm_overlay_validator.cc

This CL is based on Johnson Lin's implementaion
https://codereview.chromium.org/2636433003/

Test results of power consumption: 8.8% power save. Check more detail in
crbug.com/683347

BUG=683347
TEST=run relevant unittests
run chrome on http://www.quirksmode.org/html5/tests/video.html with all possible
configurations
* decoding configuration
 * gpu decoding: N/A
 * pure software decoding: --disable-accelerated-video-decode
 * GMB video frame: --disable-accelerated-video-decode
--enable-native-gpu-memory-buffers --enable-gpu-memory-buffer-video-frames
* overlay configurations
 * atomic mode setting: --enable-hardware-overlays --enable-drm-atomic
 * legacy mode setting: --enable-hardware-overlays
 * no overlay: N/A
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
==========

[inactive_dshwang_plz_cc_intel, 2017-02-09 04:48:57]

The CQ bit was checked by dongseong.hwang@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-02-09 04:49:50]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-09 06:28:52]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-02-09 06:28:54]

Dry run: This issue passed the CQ dry run.

[dshwang, 2017-03-07 23:08:59]

Description was changed from

==========
(NotForReview) Enable YUV video overlay on Skylake ChromeOS.

Add YUYV (i.e YUY2) for video decoder output and using those formats for
overlay

YUYV is only format supported by all linux stack such as kernel, mesa, and
minigbm, so ChromeOS IA prefer to use YUYV for video decoding.

This CL changes
1. make gpu decoder (only vaapi) decode on YUYV plane
2. make --enable-gpu-memory-buffer-video-frames choose YUYV if possible
3. make Ozone GBM prefer YUYV rather than UYUV

About 1, check the change of media/gpu/vaapi_video_decode_accelerator.cc
About 2, check the change of
content/renderer/media/renderer_gpu_video_accelerator_factories.cc and
gpu/command_buffer/service/feature_info.cc
About 3, check the change of ui/ozone/platform/drm/gpu/drm_overlay_validator.cc

This CL is based on Johnson Lin's implementaion
https://codereview.chromium.org/2636433003/

Test results of power consumption: 8.8% power save. Check more detail in
crbug.com/683347

BUG=683347
TEST=run relevant unittests
run chrome on http://www.quirksmode.org/html5/tests/video.html with all possible
configurations
* decoding configuration
 * gpu decoding: N/A
 * pure software decoding: --disable-accelerated-video-decode
 * GMB video frame: --disable-accelerated-video-decode
--enable-native-gpu-memory-buffers --enable-gpu-memory-buffer-video-frames
* overlay configurations
 * atomic mode setting: --enable-hardware-overlays --enable-drm-atomic
 * legacy mode setting: --enable-hardware-overlays
 * no overlay: N/A
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel
==========

to

==========
(NotForReview) Enable YUV video overlay on Skylake ChromeOS.

Add YUYV (i.e YUY2) for video decoder output and using those formats for
overlay

YUYV is only format supported by all linux stack such as kernel, mesa, and
minigbm, so ChromeOS IA prefer to use YUYV for video decoding.

This CL changes
1. make gpu decoder (only vaapi) decode on YUYV plane
2. make --enable-gpu-memory-buffer-video-frames choose YUYV if possible
3. make Ozone GBM prefer YUYV rather than UYUV

About 1, check the change of media/gpu/vaapi_video_decode_accelerator.cc
About 2, check the change of
content/renderer/media/renderer_gpu_video_accelerator_factories.cc and
gpu/command_buffer/service/feature_info.cc
About 3, check the change of ui/ozone/platform/drm/gpu/drm_overlay_validator.cc

This CL is based on Johnson Lin's implementaion
https://codereview.chromium.org/2636433003/

Test results of power consumption: 8.8% power save. Check more detail in
crbug.com/683347

BUG=683347
TEST=run relevant unittests
run chrome on http://www.quirksmode.org/html5/tests/video.html with all possible
configurations
* decoding configuration
 * gpu decoding: N/A
 * pure software decoding: --disable-accelerated-video-decode
 * GMB video frame: --disable-accelerated-video-decode
--enable-native-gpu-memory-buffers --enable-gpu-memory-buffer-video-frames
* overlay configurations
 * atomic mode setting: --enable-hardware-overlays --enable-drm-atomic
 * legacy mode setting: --enable-hardware-overlays
 * no overlay: N/A
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
==========

[inactive_dshwang_plz_cc_intel, 2017-03-07 23:11:05]

The CQ bit was checked by dongseong.hwang@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-03-07 23:11:56]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-07 23:26:33]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-07 23:26:34]

Dry run: Try jobs failed on following builders:
  linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_optional_gpu_tests_rel on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_optional_...)

[inactive_dshwang_plz_cc_intel, 2017-03-07 23:28:01]

The CQ bit was checked by dongseong.hwang@chromium.org to run a CQ dry run

[dshwang, 2017-03-07 23:28:06]

Patchset #2 (id:20001) has been deleted

[commit-bot: I haz the power, 2017-03-07 23:29:08]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-08 02:15:07]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-08 02:15:08]

Dry run: This issue passed the CQ dry run.