Implemented parsing of HEVC codec ids

gpu/config/gpu_info.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef GPU_CONFIG_GPU_INFO_H_
 #define GPU_CONFIG_GPU_INFO_H_
 
 // Provides access to the GPU information for the system
 // on which chrome is currently running.
 
@@ skipping 22 matching lines @@
   kCollectInfoSuccess = 1,
   kCollectInfoNonFatalFailure = 2,
   kCollectInfoFatalFailure = 3
 };
 
 // Video profile.  This *must* match media::VideoCodecProfile.
 enum VideoCodecProfile {
   VIDEO_CODEC_PROFILE_UNKNOWN = -1,
   VIDEO_CODEC_PROFILE_MIN = VIDEO_CODEC_PROFILE_UNKNOWN,
   H264PROFILE_BASELINE = 0,
-  H264PROFILE_MAIN = 1,
-  H264PROFILE_EXTENDED = 2,
-  H264PROFILE_HIGH = 3,
-  H264PROFILE_HIGH10PROFILE = 4,
-  H264PROFILE_HIGH422PROFILE = 5,
-  H264PROFILE_HIGH444PREDICTIVEPROFILE = 6,
-  H264PROFILE_SCALABLEBASELINE = 7,
-  H264PROFILE_SCALABLEHIGH = 8,
-  H264PROFILE_STEREOHIGH = 9,
-  H264PROFILE_MULTIVIEWHIGH = 10,
-  VP8PROFILE_ANY = 11,
-  VP9PROFILE_ANY = 12,
-  VIDEO_CODEC_PROFILE_MAX = VP9PROFILE_ANY,
+  H264PROFILE_MAIN,
+  H264PROFILE_EXTENDED,
+  H264PROFILE_HIGH,
+  H264PROFILE_HIGH10PROFILE,
+  H264PROFILE_HIGH422PROFILE,
+  H264PROFILE_HIGH444PREDICTIVEPROFILE,
+  H264PROFILE_SCALABLEBASELINE,
+  H264PROFILE_SCALABLEHIGH,
+  H264PROFILE_STEREOHIGH,
+  H264PROFILE_MULTIVIEWHIGH,
+  VP8PROFILE_ANY,
+  VP9PROFILE_ANY,
+  // 4 profile values are reserved for VP9 profiles.
+  HEVCPROFILE_MAIN = VP9PROFILE_ANY + 4, //=16

[ddorwin, 2016/03/02 01:36:38]

Just remove the 16 entirely. It could rot (although that is more unlikely in
this case.

[servolk, 2016/03/02 01:47:45]

I'm starting to think that maybe it would be best to just add the 4 VP9 profiles
in various enum already, even if they are going to be just reserved, but unused
for now (kinda like I did in histograms.xml per asvitkine@ suggestion). WDYT?

[ddorwin, 2016/03/03 22:00:21]

I'm hesitant to define things we don't use, though +4 is also weird. I also
wonder whether we would want ANY to be separate from PROFILE0. That might vary
based on the API.

Perhaps sandersd or dalecurtis@ have thoughts.

[DaleCurtis, 2016/03/03 22:05:32]

Sergey, you say "the 4 VP9 profiles" above. Do we know those are set in stone?
Or did you just make that value up? Does the vp9 team have any insight for us?

If those are legit, I'm fine with adding them here now and removing the _ANY
designator in place of MIN/MAX variants if endpoints don't want to check the
values explicitly.

[DaleCurtis, 2016/03/03 22:17:20]

Thanks for the link. Lets just include those here then.

[ddorwin, 2016/03/03 22:21:17]

VP9PROFILE_ANY appears 23 times [1]. We should probably add these as a separate
CL and make sure we get the code correct. For example, some are just be the
these definitions, but I worry about demuxers, etc. (i.e. webm_video_client.cc).

[1]
https://code.google.com/p/chromium/codesearch#search/&q=VP9PROFILE_ANY&sq=pac...

+  HEVCPROFILE_MAIN10,
+  HEVCPROFILE_MAIN_STILL_PICTURE,
+  VIDEO_CODEC_PROFILE_MAX = HEVCPROFILE_MAIN_STILL_PICTURE,
 };
 
 // Specification of a decoding profile supported by a hardware decoder.
 struct GPU_EXPORT VideoDecodeAcceleratorSupportedProfile {
   VideoCodecProfile profile;
   gfx::Size max_resolution;
   gfx::Size min_resolution;
 };
 
 using VideoDecodeAcceleratorSupportedProfiles =
@@ skipping 211 matching lines @@
     virtual ~Enumerator() {}
   };
 
   // Outputs the fields in this structure to the provided enumerator.
   void EnumerateFields(Enumerator* enumerator) const;
 };
 
 }  // namespace gpu
 
 #endif  // GPU_CONFIG_GPU_INFO_H_