Drop unique audio thread ID requirement.

Drop unique audio thread ID requirement.

r391848 introduced the requirement that, once set, the audio thread ID
could not be changed. This is proving too burdensome a constraint to
keep, in case audio device threads do end up being stopped and new
ones created.

While r395182 took care of some cases where audio threads end up
stopping, carefully resetting the recordeed audio thread ID, other
cases remain (see associated bug.) While those could be similarly
handled, precisely tracking the current audio thread ID is proving
to not be worth the overhead. Hence, retire the constraint and let
the audio thread processing a render quantum set its thread ID as
part of executing, irrespective of what audio thread executed
the previous quantum.

This effectively reverts r395182.

R=
BUG=613902
Committed: https://crrev.com/94a98a7b9932aafbb3baeabfec458fcdeea16707
Cr-Commit-Position: refs/heads/master@{#395682}

[sof, 2016-05-24 14:14:31]

sigbjornf@opera.com changed reviewers:
+ hongchan@chromium.org, rtoy@chromium.org

[sof, 2016-05-24 14:14:32]

please take a look.

[haraken, 2016-05-24 14:18:36]

LGTM on my side.

[Raymond Toy, 2016-05-24 15:20:08]

lgtm

[hongchan, 2016-05-24 16:08:42]

lgtm

[sof, 2016-05-24 18:08:53]

The CQ bit was checked by sigbjornf@opera.com

[commit-bot: I haz the power, 2016-05-24 18:09:20]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2008903002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2008903002/1

[commit-bot: I haz the power, 2016-05-24 20:08:13]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-24 20:09:49]

Description was changed from

==========
Drop unique audio thread ID requirement.

r391848 introduced the requirement that, once set, the audio thread ID
could not be changed. This is proving too burdensome a constraint to
keep, in case audio device threads do end up being stopped and new
ones created.

While r395182 took care of some cases where audio threads end up
stopping, carefully resetting the recordeed audio thread ID, other
cases remain (see associated bug.) While those could be similarly
handled, precisely tracking the current audio thread ID is proving
to not be worth the overhead. Hence, retire the constraint and let
the audio thread processing a render quantum set its thread ID as
part of executing, irrespective of what audio thread executed
the previous quantum.

This effectively reverts r395182.

R=
BUG=613902
==========

to

==========
Drop unique audio thread ID requirement.

r391848 introduced the requirement that, once set, the audio thread ID
could not be changed. This is proving too burdensome a constraint to
keep, in case audio device threads do end up being stopped and new
ones created.

While r395182 took care of some cases where audio threads end up
stopping, carefully resetting the recordeed audio thread ID, other
cases remain (see associated bug.) While those could be similarly
handled, precisely tracking the current audio thread ID is proving
to not be worth the overhead. Hence, retire the constraint and let
the audio thread processing a render quantum set its thread ID as
part of executing, irrespective of what audio thread executed
the previous quantum.

This effectively reverts r395182.

R=
BUG=613902

Committed: https://crrev.com/94a98a7b9932aafbb3baeabfec458fcdeea16707
Cr-Commit-Position: refs/heads/master@{#395682}
==========

[commit-bot: I haz the power, 2016-05-24 20:09:50]

Patchset 1 (id:??) landed as
https://crrev.com/94a98a7b9932aafbb3baeabfec458fcdeea16707
Cr-Commit-Position: refs/heads/master@{#395682}