Add VDA supported profile to GPUInfo.

content/common/gpu/media/vaapi_video_decode_accelerator.cc

Index: content/common/gpu/media/vaapi_video_decode_accelerator.cc
diff --git a/content/common/gpu/media/vaapi_video_decode_accelerator.cc b/content/common/gpu/media/vaapi_video_decode_accelerator.cc
index df1f6443421d197b67aa31ef61634307175a242d..3009c53295a115f6c564857b97cdf20eeb9c517c 100644
--- a/content/common/gpu/media/vaapi_video_decode_accelerator.cc
+++ b/content/common/gpu/media/vaapi_video_decode_accelerator.cc
@@ -3,6 +3,7 @@
 // found in the LICENSE file.
 
 #include "base/bind.h"
+#include "base/cpu.h"
 #include "base/debug/trace_event.h"
 #include "base/logging.h"
 #include "base/metrics/histogram.h"
@@ -923,4 +924,18 @@ bool VaapiVideoDecodeAccelerator::CanDecodeOnIOThread() {
   return false;
 }
 
+// static
+media::VideoDecodeAccelerator::SupportedResolution
+VaapiVideoDecodeAccelerator::GetSupportedResolution() {
+  media::VideoDecodeAccelerator::SupportedResolution resolution;
+  resolution.min.SetSize(16, 16);
+  base::CPU cpu;
+  // Ivy Bridge+ platforms can support more than 1920x1080.
+  if ((cpu.vendor_name() == "GenuineIntel") && cpu.model() >= 55)

[piman, 2015/01/05 21:45:22]

NAK. Please pass this on the command line, or have VAAPI provide a way to query
this.

[henryhsu, 2015/01/13 05:40:44]

We have many devices using VAAPI and VAAPI doesn't support to query supported
resolution. Ivy Bridge+ supports 4K decode. So I think to use CPU detection only
for x86 CrOS is fine and it is used for a long time. We can keep it until VAAPI
supports resolution querying.

+    resolution.max.SetSize(4096, 2160);
+  else
+    resolution.max.SetSize(1920, 1088);
+  return resolution;
+}
+
 }  // namespace content