Hi Jaganath, >>> A new event is added in mgmt for remote device name updation. >>> This event will be sent to userspace whenever a remote name >>> event comes and mgmt_connected is already sent. >> >> for me it is pretty much unclear what this event is suppose to do. I am pretty much against sending out random events to just push data into userspace. This sounds more like the case where we should delay the connection setup and notification until the remote name request finished. >> > > Delaying the connection notification until remote name request completes will solve the problem here. > But is it ok not giving connection notification if l2cap connection happens before that? that depends on what our semantics are. The ACL connection state machine already has to do certain steps before it allows any establishment of any L2CAP connection. This mainly comes from the SSP requirements. So adding the name update to it might be a good idea. That way the L2CAP connection will only complete after the mgmt connect event has been send to userspace. If that really matters. I am not even sure we have such a semantic right now. 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
