Linux-Bluetooth Archive on lore.kernel.org
 help / color / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 200039] BT advertising packet wakes up the system from S3 and suspend-to-idle
Date: Wed, 17 Oct 2018 05:27:42 +0000
Message-ID: <bug-200039-62941-HlwIzCetOH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200039-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=200039

--- Comment #24 from AceLan Kao (acelan@gmail.com) ---
Setup 'HCI_AUTO_CONN_ALWAYS' flag and "Accept all advertisement" do not mean
the advertising packet should wake up the system. We even powered off the
paired device, but the system still be waken up by advertising packets from
other random BT4 devices.

I got some questions for you and would like to figure out a feasible solution
for the issue.
1. Do you have any idea about who decide to wake up the system when the
advertising packet is received? Firmware or driver?
2. Do you know how windows handle this? Does the advertising packet wake up
windows?
3. Is there any drawback if we remove 'HCI_AUTO_CONN_ALWAYS' flag when
suspending?
Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply index

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-200039-62941@https.bugzilla.kernel.org/>
2018-10-08  7:19 ` bugzilla-daemon
2018-10-08  7:21 ` bugzilla-daemon
2018-10-08  7:31 ` bugzilla-daemon
2018-10-09 10:53 ` bugzilla-daemon
2018-10-15  7:07 ` bugzilla-daemon
2018-10-15  8:43 ` bugzilla-daemon
2018-10-15 10:53 ` bugzilla-daemon
2018-10-15 11:25 ` bugzilla-daemon
2018-10-16  1:26 ` bugzilla-daemon
2018-10-16  6:28 ` bugzilla-daemon
2018-10-17  5:27 ` bugzilla-daemon [this message]
2018-10-27 19:22 ` bugzilla-daemon
2018-10-29  3:14 ` bugzilla-daemon
2018-11-16 15:17 ` bugzilla-daemon
2018-11-16 15:27 ` bugzilla-daemon
2019-02-27 15:22 ` bugzilla-daemon
2019-03-19  9:35 ` bugzilla-daemon
2019-03-19  9:43 ` bugzilla-daemon
2019-03-19  9:45 ` bugzilla-daemon
2019-09-11  8:29 ` bugzilla-daemon
2019-09-11 11:24 ` bugzilla-daemon
2019-09-11 16:05 ` bugzilla-daemon
2019-09-11 16:18 ` bugzilla-daemon
2019-09-19 14:45 ` bugzilla-daemon

Reply instructions:

You may reply publically 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=bug-200039-62941-HlwIzCetOH@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.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

Linux-Bluetooth Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
		linux-bluetooth@vger.kernel.org
	public-inbox-index linux-bluetooth

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git