linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manish Mandlik <mmandlik@google.com>
To: marcel@holtmann.org, luiz.dentz@gmail.com
Cc: linux-bluetooth@vger.kernel.org,
	chromeos-bluetooth-upstreaming@chromium.org,
	Manish Mandlik <mmandlik@google.com>,
	Miao-chen Chou <mcchou@google.com>
Subject: [BlueZ PATCH v5 2/6] lib: Add definitions of the Adv Monitor Device Found/Lost events
Date: Wed, 17 Nov 2021 11:14:46 -0800	[thread overview]
Message-ID: <20211117110627.BlueZ.v5.2.Ied4afb8c4c882e573f4a23670fc060cbc3e319c9@changeid> (raw)
In-Reply-To: <20211117110627.BlueZ.v5.1.I7f6bdb9282c1e12ffc6c662674678f2b1cb69182@changeid>

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.

Reviewed-by: Miao-chen Chou <mcchou@google.com>
---

Changes in v5:
- Update the Adv Monitor Device Found event to include fields from the
  existing Device Found event.

Changes in v4:
- Add Advertisement Monitor Device Found event.

Changes in v3:
- Discard changes to the Device Found event and notify bluetoothd only
  when the controller stops monitoring the device via new Device Lost
  event.

Changes in v2:
- Instead of creating a new 'Device Tracking' event, add a flag '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.

 lib/mgmt.h | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/lib/mgmt.h b/lib/mgmt.h
index 0d1678f01..3bc35bc7c 100644
--- a/lib/mgmt.h
+++ b/lib/mgmt.h
@@ -1014,6 +1014,22 @@ struct mgmt_ev_controller_resume {
 	uint8_t wake_reason;
 } __packed;
 
+#define MGMT_EV_ADV_MONITOR_DEVICE_FOUND	0x002f
+struct mgmt_ev_adv_monitor_device_found {
+	uint16_t monitor_handle;
+	struct mgmt_addr_info addr;
+	int8_t rssi;
+	uint32_t flags;
+	uint16_t ad_data_len;
+	uint8_t ad_data[0];
+} __packed;
+
+#define MGMT_EV_ADV_MONITOR_DEVICE_LOST		0x0030
+struct mgmt_ev_adv_monitor_device_lost {
+	uint16_t monitor_handle;
+	struct mgmt_addr_info addr;
+} __packed;
+
 static const char *mgmt_op[] = {
 	"<0x0000>",
 	"Read Version",
@@ -1152,6 +1168,8 @@ static const char *mgmt_ev[] = {
 	"Advertisement Monitor Removed",
 	"Controller Suspend",
 	"Controller Resume",
+	"Advertisement Monitor Device Found",		/* 0x002f */
+	"Advertisement Monitor Device Lost",
 };
 
 static const char *mgmt_status[] = {
-- 
2.34.0.rc1.387.gb447b232ab-goog


  reply	other threads:[~2021-11-17 19:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 19:14 [BlueZ PATCH v5 1/6] doc: Introduce the Adv Monitor Device Found/Lost events Manish Mandlik
2021-11-17 19:14 ` Manish Mandlik [this message]
2021-11-17 19:14 ` [BlueZ PATCH v5 3/6] adv_monitor: Receive the " Manish Mandlik
2021-11-17 21:42   ` Luiz Augusto von Dentz
2021-11-17 19:14 ` [BlueZ PATCH v5 4/6] adv_monitor: Invoke DeviceFound/Lost on tracked monitors Manish Mandlik
2021-11-17 19:14 ` [BlueZ PATCH v5 5/6] adv_monitor: Change sampling period to uint16_t Manish Mandlik
2021-11-17 19:14 ` [BlueZ PATCH v5 6/6] core: Update default advmon Sampling_Period to 0xFF Manish Mandlik
2021-11-17 21:09   ` Luiz Augusto von Dentz
     [not found]     ` <CAGPPCLB9KSDG1LFYeeKnPjtD001Q00PXgkRnh8Xz_9N=zB+mqg@mail.gmail.com>
2021-11-19 19:40       ` Luiz Augusto von Dentz
2021-11-17 19:32 ` [BlueZ,v5,1/6] doc: Introduce the Adv Monitor Device Found/Lost events bluez.test.bot

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=20211117110627.BlueZ.v5.2.Ied4afb8c4c882e573f4a23670fc060cbc3e319c9@changeid \
    --to=mmandlik@google.com \
    --cc=chromeos-bluetooth-upstreaming@chromium.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=mcchou@google.com \
    /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).