cc: Make scheduling be driven by vsync for android webview.

cc/output/begin_frame_args.h

 // Copyright 2013 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 CC_OUTPUT_BEGIN_FRAME_ARGS_H_
 #define CC_OUTPUT_BEGIN_FRAME_ARGS_H_
 
 #include "base/location.h"
 #include "base/memory/ref_counted.h"
 #include "base/time/time.h"
@@ skipping 22 matching lines @@
 #else
 #define BEGINFRAME_FROM_HERE FROM_HERE
 #endif
 
 namespace cc {
 
 struct CC_EXPORT BeginFrameArgs {
   enum BeginFrameArgsType {
     INVALID,
     NORMAL,
-    SYNCHRONOUS,

[brianderson, 2015/03/25 23:10:37]

If we kept this around, could it help get rid of the
using_synchronous_renderer_compositor from SchedulerSettings?

[sunnyps, 2015/03/27 00:52:48]

I would prefer not keeping this around - it seems like the wrong place to store
whether we're in webview mode or not. Also having this in SchedulerSettings
means that it's a static flag - we don't have to worry about it changing from
frame to frame.

     MISSED,
     // Not a real type, but used by the IPC system. Should always remain the
     // *last* value in this enum.
     BEGIN_FRAME_ARGS_TYPE_MAX,
   };
   static const char* TypeToString(BeginFrameArgsType type);
 
   // Creates an invalid set of values.
   BeginFrameArgs();
 
@@ skipping 34 matching lines @@
  private:
   BeginFrameArgs(base::TimeTicks frame_time,
                  base::TimeTicks deadline,
                  base::TimeDelta interval,
                  BeginFrameArgsType type);
 };
 
 }  // namespace cc
 
 #endif  // CC_OUTPUT_BEGIN_FRAME_ARGS_H_