From: Maxime Chevallier <chevalliersebmax@gmail.com>
To: johan.hedberg@intel.com, linux-bluetooth@vger.kernel.org
Subject: [RFC][PATCH 1/1] lib : Added set_advertising_parameters function to lib.
Date: Fri, 12 Feb 2016 11:06:07 +0100 [thread overview]
Message-ID: <20160212100606.GA32264@vps217108.ovh.net> (raw)
Added hci_le_set_advertising_parameters function to hci_lib.
---
lib/hci.c | 39 +++++++++++++++++++++++++++++++++++++++
lib/hci_lib.h | 5 +++++
2 files changed, 44 insertions(+)
diff --git a/lib/hci.c b/lib/hci.c
index c25be9e..4472dd1 100644
--- a/lib/hci.c
+++ b/lib/hci.c
@@ -2996,6 +2996,45 @@ int hci_le_set_advertise_enable(int dd, uint8_t enable, int to)
return 0;
}
+int hci_le_set_advertising_parameters(int dd, uint16_t min_interval,
+ uint16_t max_interval, uint8_t advtype,
+ uint8_t own_bdaddr_type, uint8_t direct_bdaddr_type,
+ const bdaddr_t *direct_bdaddr, uint8_t chan_map,
+ uint8_t filter, int to)
+{
+ struct hci_request rq;
+ le_set_advertising_parameters_cp param_cp;
+ uint8_t status;
+
+ memset(¶m_cp, 0, sizeof(param_cp));
+ param_cp.min_interval = min_interval;
+ param_cp.max_interval = max_interval;
+ param_cp.advtype = advtype;
+ param_cp.own_bdaddr_type = own_bdaddr_type;
+ param_cp.direct_bdaddr_type = direct_bdaddr_type;
+ bacpy(¶m_cp.direct_bdaddr, direct_bdaddr);
+ param_cp.chan_map = chan_map;
+ param_cp.filter = filter;
+
+ memset(&rq, 0, sizeof(rq));
+ rq.ogf = OGF_LE_CTL;
+ rq.ocf = OCF_LE_SET_ADVERTISING_PARAMETERS;
+ rq.cparam = ¶m_cp;
+ rq.clen = LE_SET_ADVERTISING_PARAMETERS_CP_SIZE;
+ rq.rparam = &status;
+ rq.rlen = 1;
+
+ if (hci_send_req(dd, &rq, to) < 0)
+ return -1;
+
+ if (status) {
+ errno = EIO;
+ return -1;
+ }
+
+ return 0;
+}
+
int hci_le_create_conn(int dd, uint16_t interval, uint16_t window,
uint8_t initiator_filter, uint8_t peer_bdaddr_type,
bdaddr_t peer_bdaddr, uint8_t own_bdaddr_type,
diff --git a/lib/hci_lib.h b/lib/hci_lib.h
index 55aeb17..9fd7505 100644
--- a/lib/hci_lib.h
+++ b/lib/hci_lib.h
@@ -120,6 +120,11 @@ int hci_le_set_scan_parameters(int dev_id, uint8_t type, uint16_t interval,
uint16_t window, uint8_t own_type,
uint8_t filter, int to);
int hci_le_set_advertise_enable(int dev_id, uint8_t enable, int to);
+int hci_le_set_advertising_parameters(int dd, uint16_t min_interval,
+ uint16_t max_interval, uint8_t advtype,
+ uint8_t own_bdaddr_type, uint8_t direct_bdaddr_type,
+ const bdaddr_t *direct_bdaddr, uint8_t chan_map,
+ uint8_t filter, int to);
int hci_le_create_conn(int dd, uint16_t interval, uint16_t window,
uint8_t initiator_filter, uint8_t peer_bdaddr_type,
bdaddr_t peer_bdaddr, uint8_t own_bdaddr_type,
--
2.1.4
reply other threads:[~2016-02-12 10:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160212100606.GA32264@vps217108.ovh.net \
--to=chevalliersebmax@gmail.com \
--cc=johan.hedberg@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).