Linux bluetooth development
 help / color / mirror / Atom feed
From: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [RFCv0 05/20] Bluetooth: A2MP: AMP Manager basic functions
Date: Wed,  2 Nov 2011 16:02:33 +0200	[thread overview]
Message-ID: <1320242568-372-6-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1320242568-372-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>

From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>

Define AMP Manager and some basic functions.

Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
---
 include/net/bluetooth/a2mp.h |   11 +++++++
 net/bluetooth/a2mp.c         |   60 ++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 71 insertions(+), 0 deletions(-)

diff --git a/include/net/bluetooth/a2mp.h b/include/net/bluetooth/a2mp.h
index 7ead6a3..9827cec 100644
--- a/include/net/bluetooth/a2mp.h
+++ b/include/net/bluetooth/a2mp.h
@@ -15,6 +15,17 @@
 #ifndef __A2MP_H
 #define __A2MP_H
 
+struct amp_mgr *get_amp_mgr_sk(struct sock *sk);
+struct amp_mgr *create_amp_mgr(struct l2cap_conn *conn);
+void remove_amp_mgr(struct amp_mgr *mgr);
+
+struct amp_mgr {
+	struct	list_head list;
+	struct	l2cap_conn *l2cap_conn;
+	struct	socket *a2mp_sock;
+	unsigned long	flags;
+};
+
 struct a2mp_cmd {
 	__u8	code;
 	__u8	ident;
diff --git a/net/bluetooth/a2mp.c b/net/bluetooth/a2mp.c
index 2fe0004..d505c77 100644
--- a/net/bluetooth/a2mp.c
+++ b/net/bluetooth/a2mp.c
@@ -13,6 +13,7 @@
 */
 
 #include <linux/workqueue.h>
+#include <linux/list.h>
 
 #include <net/bluetooth/bluetooth.h>
 #include <net/bluetooth/hci_core.h>
@@ -21,6 +22,9 @@
 
 static struct workqueue_struct *a2mp_workqueue;
 
+LIST_HEAD(amp_mgr_list);
+DEFINE_RWLOCK(amp_mgr_list_lock);
+
 /* A2MP build & send command helper functions */
 static struct a2mp_cmd *__a2mp_build(u8 code, u8 ident, u16 len, void *data)
 {
@@ -205,3 +209,59 @@ static struct socket *open_a2mp_sock(struct l2cap_conn *conn)
 	}
 }
 
+/* AMP Manager functions */
+struct amp_mgr *get_amp_mgr_sk(struct sock *sk)
+{
+	struct amp_mgr *mgr;
+	struct amp_mgr *found = NULL;
+
+	read_lock(&amp_mgr_list_lock);
+	list_for_each_entry(mgr, &amp_mgr_list, list) {
+		if ((mgr->a2mp_sock) && (mgr->a2mp_sock->sk == sk)) {
+			found = mgr;
+			break;
+		}
+	}
+	read_unlock(&amp_mgr_list_lock);
+
+	return found;
+}
+
+void remove_amp_mgr(struct amp_mgr *mgr)
+{
+	BT_DBG("mgr %p", mgr);
+
+	write_lock(&amp_mgr_list_lock);
+	sock_release(mgr->a2mp_sock);
+	list_del(&mgr->list);
+	write_unlock(&amp_mgr_list_lock);
+
+	kfree(mgr);
+}
+
+struct amp_mgr *create_amp_mgr(struct l2cap_conn *conn)
+{
+	struct amp_mgr *mgr;
+
+	mgr = kzalloc(sizeof(*mgr), GFP_KERNEL);
+	if (!mgr)
+		goto finished;
+
+	BT_DBG("conn %p mgr %p", conn, mgr);
+
+	mgr->l2cap_conn = conn;
+
+	mgr->a2mp_sock = open_a2mp_sock(conn);
+	if (!mgr->a2mp_sock) {
+		kfree(mgr);
+		mgr = NULL;
+		goto finished;
+	}
+
+	write_lock(&amp_mgr_list_lock);
+	list_add(&(mgr->list), &amp_mgr_list);
+	write_unlock(&amp_mgr_list_lock);
+
+finished:
+	return mgr;
+}
-- 
1.7.4.1


  parent reply	other threads:[~2011-11-02 14:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 14:02 [RFCv0 00/20] RFC A2MP implementation Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 01/20] Bluetooth: A2MP: create A2MP socket Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 02/20] Bluetooth: A2MP: sk_data_ready for a2mp socket Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 03/20] Bluetooth: A2MP: sk_state_change " Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 04/20] Bluetooth: A2MP: build and send msg helpers Emeltchenko Andrei
2011-11-02 14:02 ` Emeltchenko Andrei [this message]
2011-11-02 14:02 ` [RFCv0 06/20] Bluetooth: A2MP: Remove AMP manager in state_change Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 07/20] Bluetooth: A2MP: AMP manager initialization Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 08/20] Bluetooth: A2MP: Definitions for A2MP commands Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 09/20] Bluetooth: A2MP: process A2MP messages Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 10/20] Bluetooth: A2MP: processing A2MP command reject Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 11/20] Bluetooth: A2MP: helper functions to count HCI devs Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 12/20] Bluetooth: A2MP: process A2MP Discover Request Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 13/20] Bluetooth: A2MP: process A2MP Change Notify Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 14/20] Bluetooth: A2MP: process A2MP Get Info Request Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 15/20] Bluetooth: A2MP: process A2MP Get AMP Assoc Request Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 16/20] Bluetooth: A2MP: process A2MP Create Physlink Request Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 17/20] Bluetooth: A2MP: process A2MP Disc " Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 18/20] Bluetooth: A2MP: process A2MP Command Responses Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 19/20] Bluetooth: A2MP: handling fixed channel Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 20/20] Bluetooth: A2MP: manage incoming connection Emeltchenko Andrei
2011-11-04  0:20 ` [RFCv0 00/20] RFC A2MP implementation Peter Krystad
2011-11-04  7:47   ` 'Emeltchenko Andrei'

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=1320242568-372-6-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