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: Fri, 16 Nov 2018 15:17:59 +0000 [thread overview]
Message-ID: <bug-200039-62941-SFYfma67vM@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 #27 from Raghuram Hegde (raghuram.hegde@intel.com) ---
In Bluetooth 4.1(LE Privacy 1.1), the Private address Resolving List is
maintained in the Host. Address resolution is also done by the Host.
This requires Host intervention every time an advertisement packet with an RPA
is received.
In Bluetooth 4.2(LE Privacy 1.2),
the Resolving List is maintained in the Controller. Since the Controller
resolves the private address, the Host does not need to wake up in devices
where the Host is implemented using a separate CPU. This lowers overall power
consumption.
Having said that, Intel controller does support LE Privacy v1.2 feature.
However Linux kernel need to enable to make use of the Link Layer privacy
to avoid this kind of issues.
This is generic problem/behavior observed on other vendors BT controller as
well that does not support LE privacy 1.2 feature.
We highly recommend to enable LE privacy 1.2 to solve the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-11-16 15:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-200039-62941@https.bugzilla.kernel.org/>
2018-10-08 7:19 ` [Bug 200039] BT advertising packet wakes up the system from S3 and suspend-to-idle 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
2018-10-27 19:22 ` bugzilla-daemon
2018-10-29 3:14 ` bugzilla-daemon
2018-11-16 15:17 ` bugzilla-daemon [this message]
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
2022-05-14 22:33 ` bugzilla-daemon
2022-05-14 23:42 ` bugzilla-daemon
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=bug-200039-62941-SFYfma67vM@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
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).