linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>,
	Loic Poulain <loic.poulain@intel.com>
Cc: Frederic Danis <frederic.danis@intel.com>,
	linux-bluetooth@vger.kernel.org
Subject: Re: Bluetooth not working anymore due to too agressive PM in hci_bcm ? (was: [PATCH v5 5/5] Bluetooth: hci_bcm: Add suspend/resume runtime PM functions)
Date: Wed, 05 Oct 2016 23:18:19 +0200	[thread overview]
Message-ID: <1475702299.5992.5.camel@gmail.com> (raw)
In-Reply-To: <2647C028-4C38-4CC8-9B60-38EF619A06F3@holtmann.org>

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

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 #2: btmon.thinkpad8-init.btsnoop --]
[-- Type: application/octet-stream, Size: 53920 bytes --]

[-- Attachment #3: btmon.thinkpad8-connecting.btsnoop --]
[-- Type: application/octet-stream, Size: 4858 bytes --]

[-- Attachment #4: btmon.thinkpad8-not-connecting.btsnoop --]
[-- Type: application/octet-stream, Size: 342 bytes --]

  reply	other threads:[~2016-10-05 21:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 22:22 Bluetooth not working anymore due to too agressive PM in hci_bcm ? (was: [PATCH v5 5/5] Bluetooth: hci_bcm: Add suspend/resume runtime PM functions) Jérôme de Bretagne
2016-10-04  7:46 ` Loic Poulain
2016-10-04  8:38   ` Marcel Holtmann
2016-10-05 21:18     ` Jérôme de Bretagne [this message]
2016-10-05 21:16   ` Jérôme de Bretagne
2016-10-06  7:03     ` Jérôme de Bretagne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1475702299.5992.5.camel@gmail.com \
    --to=jerome.debretagne@gmail.com \
    --cc=frederic.danis@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=loic.poulain@intel.com \
    --cc=marcel@holtmann.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).