tree ffd8b08c83845d87d04f7e04760b895092f518c7
parent 9ad46087066dbeda8def8ba0fbda32b4ea7074ba
author Jaikumar Ganesh <jaikumar@google.com> 1247191512 -0700
committer Jaikumar Ganesh <jaikumar@google.com> 1306348554 -0700

Add A2DP_INIT command and state.

In bluez4, when a device is unpaired the socket end is freed and
so we will get a EPIPE when we write to it, this causes us to call
bluetooth_close. On the next write, we don't call bluetooth_init.

The logic here is thati, if the state is A2DP_STATE_NONE and we
are waiting for BLUETOOTH_START state, we need to call bluetooth_init.
The ENODEV case is where the other end, doesn't exist, and we are
trying to write repeatedly, which means the problem is elsewhere.
When we start initially (i.e the first time) when a2dp_set_sink is called,
we used to directly set the command to configure and the a2dp_thread used to
call bluetooth_init. This fix makes this a separate state and step.
Tested:
  1. A2DP music playing, turn BT off. Turn BT open, A2DP should work.
  2. A2DP music playing, disconnect. On reconnection, it should work.
  3. A2DP music playing, cause a crash in bluetoothd. On restart, it should
     work.
  4. A2DP music playing, remote end powers down. On power up, it should work.
  5. A2DP music playing, disconnect and unpair. On repair and reconnect,
     it should work.
Tested with 2 headsets and with the troublesome HBH-DS790.