CRAS: audio_thread - Increase sleep fuzz.

If there are two output threads that wake up close to each other, the
first to wake can cause the second to wait.  This changes the how close
to the wakeup time a stream has to be before it is processed.  Making
this longer will ensure that either the two streams are processed at the
same time, or the first finishes before the second needs to run.

BUG=none
TEST=play music and youtube videos.

Change-Id: I115eedf6ff05525a46907595f68bc043c0f200ff
Signed-off-by: Dylan Reid <dgreid@chromium.org>
CRAS: audio_thread - Only skip mixing a stream if it is empty.

Don't skip mixing a stream just because it times out.  If there are
still some samples, mix them.

BUG=none
TEST=play music, youtube, and pandora.

Change-Id: I34249f5d6b865b72a45f3678c1770cfacd32af29
Signed-off-by: Dylan Reid <dgreid@chromium.org>
CRAS: Dump audio thread info to test client.

Instead of leaving audio info in syslog, print it from the test client.
This will allow it to be included in feedback logs.  Doing this did
require that the nominal message size be increased, this won't affect
anything other than a slight increase in stack usage on the rare
occasion the server sends the client a message.

BUG=chromium:338965
TEST=cras_test_client --dump_a

Change-Id: I1b96af85845a0c3d78c7f46ff8728ce3dc4ca971
Signed-off-by: Dylan Reid <dgreid@chromium.org>
CRAS: audio_thread - move message definitions to c file

These aren't used outside of audio_thread.c.

BUG=none
TEST=still compiles.

Change-Id: I226ac57ca924d55f539b27a99df36ad5c586c17d
Signed-off-by: Dylan Reid <dgreid@chromium.org>
RFC: add audio log

This is still rough, need to do some work to make the print prettier.

Are there other audio thread events I should be logging?

I think getting this info into feedback reports might make more of
them actionable.

Change-Id: I67453c141603df529e339f10f9c54db53c9501cf