1. so do you suggest to just remove the client->dev = NULL statement in
headset_setup_complete() and headset_resume_complete() ?
2. for the file descriptor sending issue have you any suggestion ?
(a hint to trigger this is repeatly run aplay, what i found is while
finishing aplay the hcidump still takes some time to make traffics
settle down (about 3-7 secs), if i repeat aplay in this period it's easy
to trigger the problem)
Thanks,
Sam Lin
Luiz Augusto von Dentz 提到:
yep, client->dev = NULL seems to be a bug, although by looking the log
it seems there is another problem, the sco connection doesn't succeed
but it still attempt to send the file descriptor. The logic on a2dp is
a little different, since it doesn't start the stream on
BT_SETCONFIGURATION_REQ and unlock the sep in any possible error.
Btw, I couldn't reproduce the problem here by using aplay, arecord or
even both together.
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
