Hi Peter, On Fri, Aug 12, 2011 at 6:00 PM, Peter Hurley <peter@xxxxxxxxxxxxxxxxxx> wrote: > AVDTP_CONNECT_TIMEOUT controls the delay between HSP/HFP > connection establishment and AVDTP signal channel establishment. > The original value of 1 sec. is too short to avoid racing for AVDTP > connection establishment (eg., if the device continues to configure > the HFP service level connection with add'l AT cmds). > > Some devices have broken AVDTP implementations that just cannot > handle the race conditions that arise if both devices are attempting > stream establishment at the same time. However, these conditions arise > only when the remote device is the ACL initiator (and in practice, the > RFCOMM initiator as well). This fix bumps out the timeout value only > when the headset has initiated the link. > --- > > v2: Follow established naming convention How about if we add some retry logic? I think it would be more efficient since it would not add an extra delay for devices that do not have such problem, perhaps we can even eliminate the 1 sec we currently have and just retry if we detect a collision has happened. -- Luiz Augusto von Dentz -- 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
