From: Dohyun Pyun <re20sfree@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: steve.jun@samsung.com, DoHyun Pyun <dh79.pyun@samsung.com>,
C S Bhargava <cs.bhargava@samsung.com>
Subject: [PATCH v3 1/8] Bluetooth: Add Set Reserved LT_ADDR Command
Date: Wed, 2 Oct 2013 21:09:11 +0900 [thread overview]
Message-ID: <1380715758-10334-2-git-send-email-dh79.pyun@samsung.com> (raw)
In-Reply-To: <1380715758-10334-1-git-send-email-dh79.pyun@samsung.com>
From: DoHyun Pyun <dh79.pyun@samsung.com>
The Set_Reserved_LT_ADDR command allows the host to request that the
BR/EDR Controller reserve a specific LT_ADDR for Connectionless Slave
Broadcast.
The Core Spec Addendum 4 adds this command in part B Connectionless
Slave Broadcast.
Bluetooth Core Specification Addendum 4 - Page 90
"7.3.86 Set Reserved LT_ADDR Command [New Section]
...
If the LT_ADDR indicated in the LT_ADDR parameter is already in use by the
BR/EDR Controller, it shall return the ACL Connection Already Exists (0x0B)
error code. If the LT_ADDR indicated in the LT_ADDR parameter is out of
range, the controller shall return the Invalid HCI Command Parameters (0x12)
error code. If the command succeeds, then the reserved LT_ADDR shall be
used when issuing subsequent Set Connectionless Slave Broadcast Data and
Set Connectionless Slave Broadcast commands.
To ensure that the reserved LT_ADDR is not already allocated, it is
recommended that this command be issued at some point after HCI_Reset is
issued but before page scanning is enabled or paging is initiated."
Signed-off-by: Dohyun Pyun <dh79.pyun@samsung.com>
Signed-off-by: C S Bhargava <cs.bhargava@samsung.com>
---
include/net/bluetooth/hci.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/include/net/bluetooth/hci.h b/include/net/bluetooth/hci.h
index d7fd825..4d88809 100644
--- a/include/net/bluetooth/hci.h
+++ b/include/net/bluetooth/hci.h
@@ -839,6 +839,15 @@ struct hci_cp_write_le_host_supported {
__u8 simul;
} __packed;
+#define HCI_OP_SET_RESERVED_LT_ADDR 0x0c74
+struct hci_cp_set_reserved_lt_addr {
+ __u8 lt_addr;
+} __packed;
+struct hci_rp_set_reserved_lt_addr {
+ __u8 status;
+ __u8 lt_addr;
+} __packed;
+
#define HCI_OP_READ_SYNC_TRAIN_PARAMS 0x0c77
#define HCI_OP_READ_LOCAL_VERSION 0x1001
--
1.8.1.2
next prev parent reply other threads:[~2013-10-02 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 12:09 [PATCH v3 0/8] Add CSA 4 commands and events in hci.h Dohyun Pyun
2013-10-02 12:09 ` Dohyun Pyun [this message]
2013-10-02 12:09 ` [PATCH v3 2/8] Bluetooth: Add Delete Reserved LT_ADDR Command Dohyun Pyun
2013-10-02 12:09 ` [PATCH v3 3/8] Bluetooth: Add Set Connectionless Slave Broadcast Data Command Dohyun Pyun
2013-10-02 12:09 ` [PATCH v3 4/8] Bluetooth: Add Write Synchronization Train Parameters Command Dohyun Pyun
2013-10-02 12:09 ` [PATCH v3 5/8] Bluetooth: Add Set Connectionless Slave Broadcast Command Dohyun Pyun
2013-10-02 12:09 ` [PATCH v3 6/8] Bluetooth: Add Start Synchronization Train Command Dohyun Pyun
2013-10-02 12:09 ` [PATCH v3 7/8] Bluetooth: Add Synchronization Train Complete Event Dohyun Pyun
2013-10-02 12:09 ` [PATCH v3 8/8] Bluetooth: Add Slave Page Response Timeout Event Dohyun Pyun
2013-10-02 12:20 ` Anderson Lizardo
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=1380715758-10334-2-git-send-email-dh79.pyun@samsung.com \
--to=re20sfree@gmail.com \
--cc=cs.bhargava@samsung.com \
--cc=dh79.pyun@samsung.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=steve.jun@samsung.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