Add 4 VP9 profiles to the media::VideoCodecProfile enum.

media/cdm/ppapi/ppapi_cdm_adapter.cc

Index: media/cdm/ppapi/ppapi_cdm_adapter.cc
diff --git a/media/cdm/ppapi/ppapi_cdm_adapter.cc b/media/cdm/ppapi/ppapi_cdm_adapter.cc
index d3a143a44aed157f8eee1474e0f6b74caacac6cd..dc3ad250e768487b4b26590abbdc7a7e75096374 100644
--- a/media/cdm/ppapi/ppapi_cdm_adapter.cc
+++ b/media/cdm/ppapi/ppapi_cdm_adapter.cc
@@ -196,6 +196,15 @@ cdm::VideoDecoderConfig::VideoCodecProfile PpVCProfileToCdmVCProfile(
       return cdm::VideoDecoderConfig::kH264ProfileHigh422;
     case PP_VIDEOCODECPROFILE_H264_HIGH_444_PREDICTIVE:
       return cdm::VideoDecoderConfig::kH264ProfileHigh444Predictive;
+    // TODO(servolk): See crbug.com/592074. We'll need to update this code to

[ddorwin, 2016/03/28 18:45:46]

We might need to be smarter about how we implement this and changes in
content_decryption_module.h [1] to avoid causing problems for older CDMs.

This should probably be part of
https://bugs.chromium.org/p/chromium/issues/detail?id=570216.

[1] https://codereview.chromium.org/1782483002/

[servolk, 2016/03/28 19:03:02]

Acknowledged.

+    // handle different VP9 profiles properly after adding VP9 profiles in
+    // media/cdm/api/content_decryption_module.h in a separate CL.
+    // For now return kProfileNotNeeded to avoid breaking unit tests.

[ddorwin, 2016/03/28 18:45:45]

Which unit tests? How does this avoid breaking them? It changes the return value
for VP9 from kUnknownVideoCodecProfile to kProfileNotNeeded.

[servolk, 2016/03/28 19:03:01]

In earlier patchsets #7,#8 of this CL trybots indicated failures of
PPAPINaClPNaClTest.VideoEncoder, PPAPINaClNewlibTest.VideoEncoder and
OutOfProcessPPAPITest.VideoEncoder (It's been ~3 weeks ago, so not all trybot
results are available now, but for example take a look at
https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_dbg...).
If I remember correctly the problem was that we used to return
kUnknownVideoCodecProfile here when trying to initialialize PPAPI VP9 decoders
and that failed. But returning kProfileNotNeeded is fine, since then the profile
value is just ignored in PPAPI. And later we'll replace it with proper VP9
profiles once we add them to CDM interface.

+    case PP_VIDEOCODECPROFILE_VP9_PROFILE0:
+    case PP_VIDEOCODECPROFILE_VP9_PROFILE1:
+    case PP_VIDEOCODECPROFILE_VP9_PROFILE2:
+    case PP_VIDEOCODECPROFILE_VP9_PROFILE3:
+      return cdm::VideoDecoderConfig::kProfileNotNeeded;
     default:
       return cdm::VideoDecoderConfig::kUnknownVideoCodecProfile;
   }