Assume the 1st USB device configuration has been selected on Android.

Assume the 1st USB device configuration has been selected on Android.

Linux will almost always select the first configuration and this avoids
apps issuing a SetConfiguration request which may fail if the system
thinks the device is busy.

A better option is to look into whether I can read the currently
selected configuration out of sysfs on Android but that is a much larger
patch so this is a good stop-gap measure.

BUG=692861
Review-Url: https://codereview.chromium.org/2700713002
Cr-Commit-Position: refs/heads/master@{#451054}
Committed: https://chromium.googlesource.com/chromium/src/+/3ab86ccb569cff38b362457b7a12762dc9cbab82

[Reilly Grant (use Gerrit), 2017-02-16 01:19:40]

reillyg@chromium.org changed reviewers:
+ juncai@chromium.org

[Reilly Grant (use Gerrit), 2017-02-16 01:19:41]

PTAL

[Reilly Grant (use Gerrit), 2017-02-16 01:22:21]

The CQ bit was checked by reillyg@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-02-16 01:23:53]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-16 03:26:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-02-16 03:26:49]

Dry run: Try jobs failed on following builders:
  chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_TIMED_OUT, no build URL)
  linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT,
no build URL)

[juncai, 2017-02-16 19:08:50]

LGTM.

[Reilly Grant (use Gerrit), 2017-02-16 19:21:36]

The CQ bit was checked by reillyg@chromium.org

[commit-bot: I haz the power, 2017-02-16 19:23:05]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-16 19:38:26]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1487272896049230, "parent_rev":
"1dfd572206baea1bcb468bfe7ca33ff8736dabd4", "commit_rev":
"3ab86ccb569cff38b362457b7a12762dc9cbab82"}

[commit-bot: I haz the power, 2017-02-16 19:39:01]

Description was changed from

==========
Assume the 1st USB device configuration has been selected on Android.

Linux will almost always select the first configuration and this avoids
apps issuing a SetConfiguration request which may fail if the system
thinks the device is busy.

A better option is to look into whether I can read the currently
selected configuration out of sysfs on Android but that is a much larger
patch so this is a good stop-gap measure.

BUG=692861
==========

to

==========
Assume the 1st USB device configuration has been selected on Android.

Linux will almost always select the first configuration and this avoids
apps issuing a SetConfiguration request which may fail if the system
thinks the device is busy.

A better option is to look into whether I can read the currently
selected configuration out of sysfs on Android but that is a much larger
patch so this is a good stop-gap measure.

BUG=692861

Review-Url: https://codereview.chromium.org/2700713002
Cr-Commit-Position: refs/heads/master@{#451054}
Committed:
https://chromium.googlesource.com/chromium/src/+/3ab86ccb569cff38b362457b7a12...
==========

[commit-bot: I haz the power, 2017-02-16 19:39:02]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/3ab86ccb569cff38b362457b7a12...