From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [RFCv1 03/15] Bluetooth: AMP: Process Logical Link Complete event
Date: Tue, 4 Sep 2012 16:44:22 +0300 [thread overview]
Message-ID: <1346766274-21612-4-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1346766274-21612-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
---
net/bluetooth/hci_event.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
index 2a517e0..f2d8335 100644
--- a/net/bluetooth/hci_event.c
+++ b/net/bluetooth/hci_event.c
@@ -3490,6 +3490,17 @@ static void hci_phy_link_complete_evt(struct hci_dev *hdev,
phylink_put(plink);
}
+static void hci_loglink_complete_evt(struct hci_dev *hdev, struct sk_buff *skb)
+{
+ struct hci_ev_logical_link_complete *ev = (void *) skb->data;
+
+ BT_DBG("%s log_handle 0x%4.4x phy_handle 0x%2.2x status 0x%2.2x",
+ hdev->name, le16_to_cpu(ev->handle), ev->phy_handle,
+ ev->status);
+
+ /* Return Config Rsp with success */
+}
+
static void hci_le_conn_complete_evt(struct hci_dev *hdev, struct sk_buff *skb)
{
struct hci_ev_le_conn_complete *ev = (void *) skb->data;
@@ -3816,6 +3827,10 @@ void hci_event_packet(struct hci_dev *hdev, struct sk_buff *skb)
hci_phy_link_complete_evt(hdev, skb);
break;
+ case HCI_EV_LOGICAL_LINK_COMPLETE:
+ hci_loglink_complete_evt(hdev, skb);
+ break;
+
case HCI_EV_NUM_COMP_BLOCKS:
hci_num_comp_blocks_evt(hdev, skb);
break;
--
1.7.9.5
next prev parent reply other threads:[~2012-09-04 13:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 13:44 [RFCv1 00/15] AMP Logical Link setup Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 01/15] Bluetooth: Set Exended Flowspec flag for HS chan Andrei Emeltchenko
2012-09-10 23:49 ` Mat Martineau
2012-09-11 8:15 ` Andrei Emeltchenko
2012-09-11 20:23 ` Mat Martineau
2012-09-04 13:44 ` [RFCv1 02/15] Bluetooth: Add logical link create function Andrei Emeltchenko
2012-09-04 13:44 ` Andrei Emeltchenko [this message]
2012-09-04 13:44 ` [RFCv1 04/15] Bluetooth: AMP: Add handle to hci_chan structure Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 05/15] Bluetooth: AMP: Process Disc Logical Link Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 06/15] Bluetooth: AMP: Process Disc Physical Link Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 07/15] Bluetooth: L2CAP: Create Conf Response function Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 08/15] Bluetooth: AMP: Send EFS Conf Rsp when loglink cmpl Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 09/15] Bluetooth: AMP: Add hs_hchan and hs_hcon to l2cap_chan Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 10/15] Bluetooth: AMP: Handle AMP_LINK connection Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 11/15] Bluetooth: AMP: Send data over AMP channel Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 12/15] Bluetooth: Factor out hci_queue_acl Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 13/15] Bluetooth: AMP: Use Loglink handle in ACL Handle field Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 14/15] Bluetooth: Process create response and connect response identically Andrei Emeltchenko
2012-09-04 13:44 ` [RFCv1 15/15] Bluetooth: Factor out common L2CAP connection code Andrei Emeltchenko
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=1346766274-21612-4-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=andrei.emeltchenko.news@gmail.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