Hi Andrei, > The code adds AMP HCI commands from A2MP protocol. HCI events are handled > similar way as mgmt interface. amp_pending is a kind of copy of mgmt_pending. this is all kernel internal code with no interface to user space. I do not see the need for such a complex infrastructure. Can not just have proper callbacks or event callback table like with L2CAP. Or just something similar. As far as I see it, we get an A2MP command over L2CAP fixed channel, we have to issue a HCI command or do some other task based on this and then respond to it. We only have one user of this first of all. And second of all, I think we can not really have pending A2MP commands anyway. This is pretty much one command at a time (per ACL link). If I am mistaken here, please correct here. It has been a while since I read that specification. 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
