Linux bluetooth development
 help / color / mirror / Atom feed
From: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [RFCv0 02/20] Bluetooth: A2MP: sk_data_ready for a2mp socket
Date: Wed,  2 Nov 2011 16:02:30 +0200	[thread overview]
Message-ID: <1320242568-372-3-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>


Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
---
 include/net/bluetooth/a2mp.h |   24 ++++++++++++++++++++++++
 net/bluetooth/a2mp.c         |   39 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 63 insertions(+), 0 deletions(-)
 create mode 100644 include/net/bluetooth/a2mp.h

diff --git a/include/net/bluetooth/a2mp.h b/include/net/bluetooth/a2mp.h
new file mode 100644
index 0000000..95dfaeb
--- /dev/null
+++ b/include/net/bluetooth/a2mp.h
@@ -0,0 +1,24 @@
+/*
+   Copyright (c) 2010-2011 Code Aurora Forum.  All rights reserved.
+   Copyright (c) 2011 Intel Corp.
+
+   This program is free software; you can redistribute it and/or modify
+   it under the terms of the GNU General Public License version 2 and
+   only version 2 as published by the Free Software Foundation.
+
+   This program is distributed in the hope that it will be useful,
+   but WITHOUT ANY WARRANTY; without even the implied warranty of
+   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+   GNU General Public License for more details.
+*/
+
+#ifndef __A2MP_H
+#define __A2MP_H
+
+struct a2mp_work_data_ready {
+	struct work_struct work;
+	struct sock *sk;
+	int bytes;
+};
+
+#endif /* __A2MP_H */
diff --git a/net/bluetooth/a2mp.c b/net/bluetooth/a2mp.c
index b69dd07..2b41882 100644
--- a/net/bluetooth/a2mp.c
+++ b/net/bluetooth/a2mp.c
@@ -17,6 +17,44 @@
 #include <net/bluetooth/bluetooth.h>
 #include <net/bluetooth/hci_core.h>
 #include <net/bluetooth/l2cap.h>
+#include <net/bluetooth/a2mp.h>
+
+static struct workqueue_struct *a2mp_workqueue;
+
+static void data_ready_worker(struct work_struct *w)
+{
+	struct a2mp_work_data_ready *work = (struct a2mp_work_data_ready *) w;
+	struct sock *sk = work->sk;
+	struct sk_buff *skb;
+
+	BT_DBG("sk %p", sk);
+
+	/* skb_dequeue() is thread-safe */
+	while ((skb = skb_dequeue(&sk->sk_receive_queue))) {
+		/* process a2mp here */
+		kfree_skb(skb);
+	}
+
+	sock_put(work->sk);
+	kfree(work);
+}
+
+static void a2mp_data_ready(struct sock *sk, int bytes)
+{
+	struct a2mp_work_data_ready *work;
+
+	work = kmalloc(sizeof(*work), GFP_KERNEL);
+	if (work) {
+		INIT_WORK(&work->work, data_ready_worker);
+		sock_hold(sk);
+		work->sk = sk;
+		work->bytes = bytes;
+		if (!queue_work(a2mp_workqueue, &work->work)) {
+			kfree(work);
+			sock_put(sk);
+		}
+	}
+}
 
 static void l2cap_fixed_channel_config(struct sock *sk)
 {
@@ -64,6 +102,7 @@ static struct socket *open_a2mp_sock(struct l2cap_conn *conn)
 	}
 
 	sk = sock->sk;
+	sk->sk_data_ready = a2mp_data_ready;
 	memset(&addr, 0, sizeof(addr));
 	bacpy(&addr.l2_bdaddr, conn->src);
 	addr.l2_family = AF_BLUETOOTH;
-- 
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 ` Emeltchenko Andrei [this message]
2011-11-02 14:02 ` [RFCv0 03/20] Bluetooth: A2MP: sk_state_change for a2mp socket Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 04/20] Bluetooth: A2MP: build and send msg helpers Emeltchenko Andrei
2011-11-02 14:02 ` [RFCv0 05/20] Bluetooth: A2MP: AMP Manager basic functions Emeltchenko Andrei
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-3-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