Hi Marcel, > > Using out-of-band gpio/irq which are retrieved from the ACPI device. > > wakeup can be initiated by host or controller depending which one wants > > to transfer hci data. > > I am actually curious if HCI remote wakeup might not work. So the HID > mouse (I assume Classic here) will initiate a HCI Create Connection which > will result in a HCI Connection Request. So that wakeup event needs to be > allowed. I am curious if we might not set that correctly. That's correct, my HID mouse is using standard Bluetooth BR/EDR, not LE. > I would need to see the btmon trace from the controller initialization > (start btmon before calling btattach). I am no longer sure that this has > been tested with UART based controllers. On USB the remote wakeup works. Here you go, I'm attaching traces taken with btmon: 1/ btmon.thinkpad8-init: the one you've asked, showing the controller init and 2 other ones, just in case: 2/ btmon.thinkpad8-connecting: showing the mouse connecting right after the init 1/ so still properly detected at that time and doing some cursor moves 3/ btmon.thinkpad8-not-connecting: traces taken if the mouse is not switched on during the controller initialization, but only a bit later (roughly 30s or 1min). Switching on the mouse then shows simply no trace at all. > If the events for connection creation and remote wakeup set correctly, > then it is some GPIO or Broadcom vendor specific thing. >From the attached traces 1/, do the events seem to be set up correctly according to you? Regards, Jérôme
Attachment:
btmon.thinkpad8-init.btsnoop
Description: Binary data
Attachment:
btmon.thinkpad8-connecting.btsnoop
Description: Binary data
Attachment:
btmon.thinkpad8-not-connecting.btsnoop
Description: Binary data
