Hi Luiz, > This enables btusb to inform the polling interval used for receiving > packets, the interval is then used wih rx_work which has been changed > to be a delayed work. > > The interval is then used as a time window where frames received from > different endpoints are considered to be arrived at same time. > > In order to resolve potential conflicts between endpoints a dedicated > queue for events was introduced and it is now processed before the ACL > packets. > > It worth noting though that priorizing events over ACL data may result > in inverting the order of the packets over the air, for instance there > may be packets received before a disconnect event that will be > discarded and unencrypted packets received before encryption change > which would considered encrypted, because of these potential inversions > the support for polling interval is not enabled by default so platforms > have the following means to enable it: we can not touch the core that impacts all transport layers even if they are not broken. So adding the second queue is not something that I think is a good idea. And again, we are just papering over a hole. However if you want to queue within btusb driver before sending it to the core, then maybe. Regards Marcel
