audio/msm8660: Move fsync to LPA event thread

- Sometimes while LPA playback seek to last second, music lose
  control and "Music not responding" message pop-up to close.
- In last buffer case, call to fsync by releasing mutex lock
  after write to driver; meanwhile write done event is reached
  and EOS is triggered in event thread. Due to this LPA session
  reset is called and mutex lock goes out of scope. Due to this
  session is blocked on mutex as it is not able to acquire lock
  after fsync call in write.
- Call to fsync code is moved just before trigger to EOS after
  write done event in event thread so that EOS is posted only
  after complete playback of last buffer.

Change-Id: I48bc7f887b287957bf9d13ae00b94221295a7efd
CRs-Fixed: 457668
1 file changed
tree: 9dcdf9e94f179867b813d5eb6feb040ec8365b94
  1. alsa_sound/
  2. audiod/
  3. libalsa-intf/
  4. mm-audio/
  5. msm7x30/
  6. msm8660/