Hi, On Mon, Feb 13, 2012 at 12:38 PM, Mohanan, Rajmohan <rajmohan.mohanan@xxxxxxxxx> wrote: > Hi > With Lenovo T500laptop, > whenever after bonding Lenovo T500 is initiating a SDP search Request which collides our SDP request(from Bluez we are initiator we are starting SDP query immediately and if we are responder we are delaying for 2 seconds for starting SDP query). > > > For solving this IOP issue I have made a change that if we are initiator also we will delay for 1 second and starting SDP query after bonding. Why not check whether we are master or not? So the master has priority to do the sdp right away and if we found we are slave then we fallback to reverse service discover. This should avoid an extra 1 sec when pairing normally, since this is not exactly an usual case where both sides init an sdp simultaneously. It is not clear what stack are you running in T500? Is it pairing being triggered simultaneously in both sides? Btw, I sugegst you to take a look at git format-patch + git send-email for sending patches, just google it in doubt this is the preferable format since we can review your patches inline. -- 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
