Hi Oliver, > > > could somebody enlighten me, when exactly those timestamps are generated? > > > > they are normally stamped when they enter our internal queues. So the > > Bluetooth core stamps them when they come from the driver. > > Thanks. That means if they come from btusb on ehci they are > stamped in interrupt. > So it is not possible that an event is late because the work queue > was congested. not that I can tell. And yes, in case of USB they are stamped in interrupt. But with USB keep in mind that HCI events and HCI ACL data is on different endpoints. 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
