Gamepad API support for chrome on android

content/browser/gamepad/gamepad_provider.cc

Index: content/browser/gamepad/gamepad_provider.cc
diff --git a/content/browser/gamepad/gamepad_provider.cc b/content/browser/gamepad/gamepad_provider.cc
index 1cc7aab73f5daba2e6984c3e626275c27fbf06b8..dab5451b7a878c9b4e4ef2020566da2dbd7a07c2 100644
--- a/content/browser/gamepad/gamepad_provider.cc
+++ b/content/browser/gamepad/gamepad_provider.cc
@@ -113,7 +113,7 @@ void GamepadProvider::Initialize(scoped_ptr<GamepadDataFetcher> fetcher) {
   memset(hwbuf, 0, sizeof(GamepadHardwareBuffer));
 
   polling_thread_.reset(new base::Thread("Gamepad polling thread"));
-#if defined(OS_LINUX)
+#if defined(OS_LINUX) || defined(OS_ANDROID)

[kbalazs, 2014/03/26 19:24:53]

I think we should use base::MessageLoop::TYPE_DEFAULT on Android because there
is no need for an io loop and I guess a default loop is the cheapest (at least
in terms of dependencies).

[SaurabhK, 2014/03/27 13:32:31]

On 2014/03/26 19:24:53, kbalazs wrote:

Thanks, changing it now.

   // On Linux, the data fetcher needs to watch file descriptors, so the message
   // loop needs to be a libevent loop.
   const base::MessageLoop::Type kMessageLoopType = base::MessageLoop::TYPE_IO;