From: Bharat Bhusan Panda <bharat.b.panda@intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v3] Bluetooth: Support fast advertising interval
Date: Mon, 4 Feb 2019 14:37:47 +0530 [thread overview]
Message-ID: <1549271267-12393-1-git-send-email-bharat.b.panda@intel.com> (raw)
Changes made to add support for fast advertising interval as per
core 4.1 specification, section 9.3.11.2.
A peripheral device entering any of the following GAP modes and
sending either non-connectable advertising events or scannable undirected
advertising events should use adv_fast_interval2(100ms - 150ms)
for adv_fast_period(30s).
- Non-Discoverable Mode
- Non-Connectable Mode
- Limited Discoverable Mode
- General Discoverable Mode
Signed-off-by: Bharat Bhusan Panda <bharat.b.panda@intel.com>
---
include/net/bluetooth/hci_core.h | 2 ++
net/bluetooth/hci_request.c | 27 +++++++++++++++++++++++++++
2 files changed, 29 insertions(+)
diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h
index 0db1b9b..868c2fb 100644
--- a/include/net/bluetooth/hci_core.h
+++ b/include/net/bluetooth/hci_core.h
@@ -1491,6 +1491,8 @@ struct hci_mgmt_chan {
#define DISCOV_INTERLEAVED_INQUIRY_LEN 0x04
#define DISCOV_BREDR_INQUIRY_LEN 0x08
#define DISCOV_LE_RESTART_DELAY msecs_to_jiffies(200) /* msec */
+#define DISCOV_LE_FAST_ADV_INT_MIN 100 /* msec */
+#define DISCOV_LE_FAST_ADV_INT_MAX 150 /* msec */
void mgmt_fill_version_info(void *ver);
int mgmt_new_settings(struct hci_dev *hdev);
diff --git a/net/bluetooth/hci_request.c b/net/bluetooth/hci_request.c
index e8c9ef1..9b73061 100644
--- a/net/bluetooth/hci_request.c
+++ b/net/bluetooth/hci_request.c
@@ -1092,6 +1092,33 @@ void __hci_req_enable_advertising(struct hci_request *req)
else
cp.type = LE_ADV_NONCONN_IND;
+ /* As per core 4.1 spec, section 9.3.11.2: A peripheral device
+ * entering any of the following GAP modes and sending either
+ * non-connectable advertising events or scannable undirected
+ * advertising events should use adv_fast_interval2(100ms - 150ms)
+ * for adv_fast_period(30s).
+ *
+ * - Non-Discoverable Mode
+ * - Non-Connectable Mode
+ * - Limited Discoverable Mode
+ * - General Discoverable Mode
+ */
+ if (cp.type == LE_ADV_NONCONN_IND || cp.type == LE_ADV_SCAN_IND) {
+ /* Set the suggested min and max fast advertising interval,
+ * only if the peripheral device has entered any of the modes
+ * such as non-discoverable, non-connectable or limited-
+ * discoverable.
+ */
+ if (!hci_dev_test_flag(hdev, HCI_DISCOVERABLE) ||
+ !hci_dev_test_flag(hdev, HCI_CONNECTABLE) ||
+ hci_dev_test_flag(hdev, HCI_LIMITED_DISCOVERABLE)) {
+ cp.min_interval =
+ cpu_to_le16(DISCOV_LE_FAST_ADV_INT_MIN);
+ cp.max_interval =
+ cpu_to_le16(DISCOV_LE_FAST_ADV_INT_MAX);
+ }
+ }
+
cp.own_address_type = own_addr_type;
cp.channel_map = hdev->le_adv_channel_map;
--
1.9.1
next reply other threads:[~2019-02-04 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 9:07 Bharat Bhusan Panda [this message]
2019-02-04 14:38 ` [PATCH v3] Bluetooth: Support fast advertising interval Marcel Holtmann
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=1549271267-12393-1-git-send-email-bharat.b.panda@intel.com \
--to=bharat.b.panda@intel.com \
--cc=linux-bluetooth@vger.kernel.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).