[PW_SID:569881] Add Advertisement Monitor Device Found/Lost events #1052
Conversation
This patch adds workflow files for ci:
[schedule_work.yml]
- runs every 30 mins.
- sync repo with upstream repo and rebase workflow branch to tip of
master.
- creates PR after reading patches from patchwork.kernel.org
[ci.yml]
- Tests the following checks:
- checkpatch
- gitlint
- make
- make check
[code_scan.yml]
- Static code checker: Coverity and Clang
- Coverity: Submit the result to the coverity website
- Clang Code Scan: Send email with result file to the internal team
To simplify the history, new change will amend to this patch without
creating new patch.
This patch introduces new MGMT events to indicate that the controller has started/stopped tracking a particular device matching one of the already added Advertisement Monitor.
This patch adds definitions of the new Advertisement Monitor Device Found and Device Lost events to indicate that the controller has started/stopped tracking a particular device.
This patch registers callback finctions to receive the Advertisement Monitor Device Found and Device Lost events. Test performed: - verified by logs that the MSFT Monitor Device is received from the controller and the bluetoothd is notified whenever the controller starts/stops monitoring a device.
|
CheckPatch |
|
GitLint |
|
Prep - Setup ELL |
|
Build - Prep |
|
Build - Configure |
|
Build - Make |
|
Make Check |
|
Make Distcheck |
|
Build w/ext ELL - Configure |
|
Build w/ext ELL - Make |
github-actions
bot
force-pushed
the
workflow
branch
3 times, most recently
from
42a749b
to
a55d828
Compare
github-actions
bot
force-pushed
the
workflow
branch
2 times, most recently
from
98f0f5f
to
6479aae
Compare
Hello Bt-Maintainers,
Bluetooth Advertisement Monitor API was introduced to support background
scanning and proximity detection based on the application specified RSSI
thresholds and content filters on LE advertisement packets.
To optimize the power consumption, the API offloads the content
filtering and RSSI tracking to the controller if the controller
offloading support is available. However, this monitoring is not
completely offloaded as the bluetoothd also handles RSSI thresholds and
timeouts in order to fulfill high/low thresholds/timeouts filtering with
D-bus clients.
There is further room to achieve better power optimization by supporting
the controller event HCI_VS_MSFT_LE_Monitor_Device_Event to fulfill true
monitor offloading. This is currently not supported as it was originally
desired to minimize the changes to the MGMT interface and reuse the
existing MGMT event - MGMT_EV_DEVICE_FOUND to pass advertisements to
bluetoothd and let bluetoothd handle the RSSI thresholds and timeouts in
order to fulfill the D-bus API requirements for the client.
This patch series introduces MGMT event MGMT_EV_ADV_MONITOR_DEVICE_FOUND
and MGMT_EV_ADV_MONITOR_DEVICE_LOST to indicate that the controller has
started/stopped monitoring a particular device.
Please let me know what you think about this or if you have any further
questions.
Thanks,
Manish.
Changes in v4:
reserved.
Changes in v3:
when the controller stops monitoring the device via new Device Lost
event.
when the controller stops monitoring the device via new Device Lost
event.
it's arguments.
Changes in v2:
Tracked' in the existing 'Device Found' event and add a new 'Device
Lost' event to indicate that the controller has stopped tracking that
device.
Tracked' in the existing 'Device Found' event and add a new 'Device
Lost' event to indicate that the controller has stopped tracking that
device.
adv_monitor_device_lost_callback() as it will receive only Device Lost
event.
Manish Mandlik (3):
doc: Introduce the Adv Monitor Device Found/Lost events
lib: Add definitions of the Adv Monitor Device Found/Lost events
adv_monitor: Receive the Device Found/Lost events
doc/mgmt-api.txt | 50 ++++++++++++++++++++++++++++++++++++++++++++++-
lib/mgmt.h | 14 +++++++++++++
src/adv_monitor.c | 50 +++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 113 insertions(+), 1 deletion(-)