From: Miao-chen Chou <mcchou@chromium.org>
To: Bluetooth Kernel Mailing List <linux-bluetooth@vger.kernel.org>
Cc: Yoni Shavit <yshavit@chromium.org>,
Michael Sun <michaelfsun@google.com>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Alain Michaud <alainm@chromium.org>,
Marcel Holtmann <marcel@holtmann.org>,
Miao-chen Chou <mcchou@chromium.org>
Subject: [BlueZ PATCH v1] lib: Add definitions for advertisement monitor features
Date: Mon, 18 May 2020 16:53:54 -0700 [thread overview]
Message-ID: <20200518165301.BlueZ.v1.1.I6e499969d74a49ab2a152bf0484a18c08a07a267@changeid> (raw)
This adds the following command opcodes, event codes and the corresponding
structures.
- MGMT_OP_READ_ADV_MONITOR_FEATURES
- MGMT_OP_ADD_ADV_PATTERNS_MONITOR
- MGMT_OP_REMOVE_ADV_MONITOR
- MGMT_EV_ADV_MONITOR_ADDED
- MGMT_EV_ADV_MONITOR_REMOVED
---
lib/mgmt.h | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 51 insertions(+)
diff --git a/lib/mgmt.h b/lib/mgmt.h
index b4fc72069..9fc9c1717 100644
--- a/lib/mgmt.h
+++ b/lib/mgmt.h
@@ -628,6 +628,42 @@ struct mgmt_rp_set_exp_feature {
uint32_t flags;
} __packed;
+#define MGMT_ADV_MONITOR_FEATURE_MASK_OR_PATTERNS (1 << 0)
+
+#define MGMT_OP_READ_ADV_MONITOR_FEATURES 0x004B
+struct mgmt_rp_read_adv_monitor_features {
+ __u32 supported_features;
+ __u32 enabled_features;
+ __u16 max_num_handles;
+ __u8 max_num_patterns;
+ __16 num_handles;
+ __16 handles[0];
+} __packed;
+
+struct mgmt_adv_pattern {
+ __u8 ad_type;
+ __u8 offset;
+ __u8 length;
+ __u8 value[31];
+} __packed;
+
+#define MGMT_OP_ADD_ADV_PATTERNS_MONITOR 0x004C
+struct mgmt_cp_add_adv_patterns_monitor {
+ __u8 pattern_count;
+ struct mgmt_adv_pattern patterns[0];
+} __packed;
+struct mgmt_rp_add_adv_patterns_monitor {
+ __u16 monitor_handle;
+} __packed;
+
+#define MGMT_OP_REMOVE_ADV_MONITOR 0x004D
+struct mgmt_cp_remove_adv_monitor {
+ __u16 monitor_handle;
+} __packed;
+struct mgmt_rp_remove_adv_monitor {
+ __u16 monitor_handle;
+} __packed;
+
#define MGMT_EV_CMD_COMPLETE 0x0001
struct mgmt_ev_cmd_complete {
uint16_t opcode;
@@ -857,6 +893,16 @@ struct mgmt_ev_exp_feature_changed {
uint32_t flags;
} __packed;
+#define MGMT_EV_ADV_MONITOR_ADDED 0x0028
+struct mgmt_ev_adv_monitor_added {
+ __u16 monitor_handle;
+} __packed;
+
+#define MGMT_EV_ADV_MONITOR_REMOVED 0x0029
+struct mgmt_ev_adv_monitor_removed {
+ __u16 monitor_handle;
+} __packed;
+
static const char *mgmt_op[] = {
"<0x0000>",
"Read Version",
@@ -933,6 +979,9 @@ static const char *mgmt_op[] = {
"Read Security Information", /* 0x0048 */
"Read Experimental Features Information",
"Set Experimental Feature",
+ "Read Advertisement Monitor Features",
+ "Add Advertisement Patterns Monitor",
+ "Remove Advertisement Monitor",
};
static const char *mgmt_ev[] = {
@@ -976,6 +1025,8 @@ static const char *mgmt_ev[] = {
"Extended Controller Information Changed",
"PHY Configuration Changed",
"Experimental Feature Changed",
+ "Advertisement Monitor Added", /* 0x0028 */
+ "Advertisement Monitor Removed",
};
static const char *mgmt_status[] = {
--
2.26.2
next reply other threads:[~2020-05-18 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 23:53 Miao-chen Chou [this message]
2020-05-19 1:36 ` [BlueZ,v1] lib: Add definitions for advertisement monitor features 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=20200518165301.BlueZ.v1.1.I6e499969d74a49ab2a152bf0484a18c08a07a267@changeid \
--to=mcchou@chromium.org \
--cc=alainm@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=michaelfsun@google.com \
--cc=yshavit@chromium.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).