Hi Marcel, > 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? I was thinking the Mode Change event would carry a LMP response timeout or link supervision (LS) timeout status when the two devices lose synchronization while in sniff just after sending exit sniff LMP PDU (only baseband ACK). It is more clear when the LS timeout is greater than the 30 second (immutable) LMP response timeout. But reading the LMP spec (2.4.1) I conclude that the former cannot occur in the exit sniff scenario and the Disconnection Complete event is the only required event in the latter. I agree to wait until we have a clear and real scenario and then discuss further with those logs. Best regards, -Matt Employee of the Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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
