Hi Matt, > > is there really a problem? The LMP will send an error via HCI. So we do > > get the mode changed event, but just with an error. And since we are not > > checking the error at all, we just go ahead with the SCO setup attempt > > in that case. > > > > The attempt to start SCO after the related ACL is no longer present > makes no sense. > > Either after mode change event with no success or disconnection complete > event the result is the same; there is no valid ACL to attempt > SCO/eSCO. > > Error code 0x02 "unknown connection identifier" may apply for the > command status event for setup synchronous connection command but the > spec does not require it. I see the point the the disconnect event and in that case we need to check if we have an pending SCO setup and remove that. However what is up with the mode change. If that fails, we are still in sniff mode and can just proceed with the SCO setup attempt. With the broken hardware it will fail for sure, but with good behaving LM on the remote side it might just get the device out of sniff mode at that point and SCO setup can succeed. Why do you imply that a mode change event with a failure means that the ACL is no longer present? Regards Marcel -- 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
