iHD workaround for Y800 with JPEG decode

iHD v20.1.1 is unable to support Y800 format on gen 12 devices yet
- https://github.com/intel/media-driver/issues/941. As we
only care about NV12 and I420 images currently, this workaround
should be acceptable.

Bug: b:159896972
Test: On TGL tast run <IP_ADDR> graphics.VAAPIUnittest.jpeg_decoder
Signed-off-by: Sushma Venkatesh Reddy <sushma.venkatesh.reddy@intel.com>
Change-Id: Ic26f57f547b0a127c40cbe2a007068e57243feae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2294345Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#788793}

media/gpu/vaapi/vaapi_wrapper.cc

@@ -1306,11 +1306,12 @@ bool VaapiWrapper::GetJpegDecodeSuitableImageFourCC(unsigned int rt_format,
   } else if (GetImplementationType() == VAImplementation::kIntelIHD) {
     // TODO(b/155939640): iHD v19.4 fails to allocate AYUV surfaces for the VPP
     // on gen 9.5.
-    // (b/159896972): iHD v19.4 cannot create Y216 and Y416 images from a
-    // decoded JPEG on gen 12.
+    // (b/159896972): iHD v20.1.1 cannot create Y216 and Y416 images from a
+    // decoded JPEG on gen 12. It is also failing to support Y800 format.
     if (preferred_fourcc == VA_FOURCC_AYUV ||
         preferred_fourcc == VA_FOURCC_Y216 ||
-        preferred_fourcc == VA_FOURCC_Y416) {
+        preferred_fourcc == VA_FOURCC_Y416 ||
+        preferred_fourcc == VA_FOURCC_Y800) {
       preferred_fourcc = VA_FOURCC_I420;
     }
   }