From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.dentz@gmail.com, brian.gix@intel.com, inga.stotland@intel.com
Subject: [PATCH BlueZ 2/4] lib: Add defines of new MGMT opcodes and events
Date: Thu, 22 Sep 2022 13:38:50 -0700 [thread overview]
Message-ID: <20220922203852.494315-3-brian.gix@intel.com> (raw)
In-Reply-To: <20220922203852.494315-1-brian.gix@intel.com>
Populated new opcodes and events into static mgmt_ev and mgmt_op string
arrays.
---
lib/mgmt.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/lib/mgmt.h b/lib/mgmt.h
index 79b77d31a..796190cd9 100644
--- a/lib/mgmt.h
+++ b/lib/mgmt.h
@@ -1170,6 +1170,10 @@ static const char *mgmt_op[] = {
"Add Extended Advertisement Parameters", /* 0x0054 */
"Add Extended Advertisement Data",
"Add Advertisement Patterns Monitor RSSI",
+ "Set Mesh Receiver",
+ "Read Mesh Features",
+ "Mesh Send",
+ "Mesh Send Cancel",
};
static const char *mgmt_ev[] = {
@@ -1222,6 +1226,8 @@ static const char *mgmt_ev[] = {
"Controller Resume",
"Advertisement Monitor Device Found", /* 0x002f */
"Advertisement Monitor Device Lost",
+ "Mesh Packet Found",
+ "Mesh Packet Complete",
};
static const char *mgmt_status[] = {
--
2.37.3
next prev parent reply other threads:[~2022-09-22 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:38 [PATCH BlueZ 0/4] Mesh demon switched to using kernel Mesh MGMT Brian Gix
2022-09-22 20:38 ` [PATCH BlueZ 1/4] mgmt: Add support for Mesh in the kernel Brian Gix
2022-09-22 21:32 ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-22 20:38 ` Brian Gix [this message]
2022-09-22 20:38 ` [PATCH BlueZ 3/4] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-22 20:38 ` [PATCH BlueZ 4/4] mesh: Add new kernel MGMT based IO transport Brian Gix
2022-09-22 21:20 ` [PATCH BlueZ 0/4] Mesh demon switched to using kernel Mesh MGMT patchwork-bot+bluetooth
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=20220922203852.494315-3-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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