From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.dentz@gmail.com, brian.gix@intel.com, tedd.an@intel.com
Subject: [PATCH BlueZ] tools: mgmt-tester - Test for HCI cmd after static addr set
Date: Thu, 6 Oct 2022 15:53:26 -0700 [thread overview]
Message-ID: <20221006225326.641765-1-brian.gix@intel.com> (raw)
This change checks for the expected HCI command after Static Address
change requested.
---
tools/mgmt-tester.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/tools/mgmt-tester.c b/tools/mgmt-tester.c
index 5747ab84b..7bb219953 100644
--- a/tools/mgmt-tester.c
+++ b/tools/mgmt-tester.c
@@ -4065,6 +4065,9 @@ static const struct generic_data set_static_addr_success_test = {
.expect_param = set_static_addr_settings,
.expect_len = sizeof(set_static_addr_settings),
.expect_settings_set = MGMT_SETTING_STATIC_ADDRESS,
+ .expect_hci_command = BT_HCI_CMD_LE_SET_RANDOM_ADDRESS,
+ .expect_hci_param = set_static_addr_valid_param,
+ .expect_hci_len = sizeof(set_static_addr_valid_param),
};
static const char set_static_addr_settings_dual[] = { 0x80, 0x00, 0x00, 0x00 };
@@ -4076,6 +4079,9 @@ static const struct generic_data set_static_addr_success_test_2 = {
.expect_status = MGMT_STATUS_SUCCESS,
.expect_param = set_static_addr_settings_dual,
.expect_len = sizeof(set_static_addr_settings_dual),
+ .expect_hci_command = BT_HCI_CMD_LE_SET_RANDOM_ADDRESS,
+ .expect_hci_param = set_static_addr_valid_param,
+ .expect_hci_len = sizeof(set_static_addr_valid_param),
};
static const struct generic_data set_static_addr_failure_test = {
--
2.37.3
next reply other threads:[~2022-10-06 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 22:53 Brian Gix [this message]
2022-10-07 0:22 ` [BlueZ] tools: mgmt-tester - Test for HCI cmd after static addr set bluez.test.bot
2022-10-07 15:10 ` [PATCH BlueZ] " 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=20221006225326.641765-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=tedd.an@intel.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