linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCHv4 04/17] android/socket: Define structs and implement listen
Date: Mon, 18 Nov 2013 15:20:41 +0200	[thread overview]
Message-ID: <1384780854-20970-5-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1384780854-20970-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>

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

This defines structures for socket HAL. We need to emulate Android
sockets by sending connect/accept signals over file descriptor.
Handle HAL socket listen call. Create RFCOMM socket and wait for events.
---
 android/socket.c |   79 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 79 insertions(+)

diff --git a/android/socket.c b/android/socket.c
index 9c94c03..0731bd9 100644
--- a/android/socket.c
+++ b/android/socket.c
@@ -27,8 +27,12 @@
 
 #include <glib.h>
 #include <stdbool.h>
+#include <unistd.h>
+#include <errno.h>
 
 #include "lib/bluetooth.h"
+#include "btio/btio.h"
+#include "lib/sdp.h"
 #include "log.h"
 #include "hal-msg.h"
 #include "hal-ipc.h"
@@ -40,6 +44,50 @@
 
 static bdaddr_t adapter_addr;
 
+/* Simple list of RFCOMM server sockets */
+GList *servers = NULL;
+
+/* Simple list of RFCOMM connected sockets */
+GList *connections = NULL;
+
+struct rfcomm_sock {
+	int fd;		/* descriptor for communication with Java framework */
+	int real_sock;	/* real RFCOMM socket */
+	int channel;	/* RFCOMM channel */
+};
+
+static struct rfcomm_sock *create_rfsock(int sock, int *hal_fd)
+{
+	int fds[2] = {-1, -1};
+	struct rfcomm_sock *rfsock;
+
+	if (socketpair(AF_LOCAL, SOCK_STREAM, 0, fds) < 0) {
+		error("socketpair(): %s", strerror(errno));
+		*hal_fd = -1;
+		return NULL;
+	}
+
+	rfsock = g_new0(struct rfcomm_sock, 1);
+	rfsock->fd = fds[0];
+	*hal_fd = fds[1];
+	rfsock->real_sock = sock;
+
+	return rfsock;
+}
+
+static void cleanup_rfsock(struct rfcomm_sock *rfsock)
+{
+	DBG("rfsock: %p fd %d real_sock %d chan %u",
+		rfsock, rfsock->fd, rfsock->real_sock, rfsock->channel);
+
+	if (rfsock->fd > 0)
+		close(rfsock->fd);
+	if (rfsock->real_sock > 0)
+		close(rfsock->real_sock);
+
+	g_free(rfsock);
+}
+
 static struct {
 	uint8_t uuid[16];
 	uint8_t channel;
@@ -71,8 +119,16 @@ static int get_rfcomm_default_chan(const uint8_t *uuid)
 	return -ENOENT;
 }
 
+static void accept_cb(GIOChannel *io, GError *err, gpointer user_data)
+{
+}
+
 static int handle_listen(void *buf)
 {
+	struct hal_cmd_sock_listen *cmd = buf;
+	struct rfcomm_sock *rfsock;
+	GIOChannel *io;
+	GError *err = NULL;
 	int hal_fd;
 	int chan;
 
@@ -82,6 +138,29 @@ static int handle_listen(void *buf)
 	if (chan < 0)
 		return chan;
 
+	DBG("rfcomm channel %d", chan);
+
+	rfsock = create_rfsock(-1, &hal_fd);
+	if (!rfsock)
+		return -1;
+
+	io = bt_io_listen(accept_cb, NULL, rfsock, NULL, &err,
+				BT_IO_OPT_SOURCE_BDADDR, &adapter_addr,
+				BT_IO_OPT_CHANNEL, chan,
+				BT_IO_OPT_INVALID);
+	if (!io) {
+		error("Failed listen: %s", err->message);
+		g_error_free(err);
+		cleanup_rfsock(rfsock);
+		return -1;
+	}
+
+	rfsock->real_sock = g_io_channel_unix_get_fd(io);
+	servers = g_list_append(servers, rfsock);
+
+	DBG("real_sock %d fd %d hal_fd %d",
+				rfsock->real_sock, rfsock->fd, hal_fd);
+
 	return hal_fd;
 }
 
-- 
1.7.10.4


  parent reply	other threads:[~2013-11-18 13:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 13:20 [PATCHv4 00/17] Socket HAL Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 01/17] android/socket: Add connect signal to socket Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 02/17] android: trivial: Add comment making code consistent Andrei Emeltchenko
2013-11-19  9:22   ` Johan Hedberg
2013-11-18 13:20 ` [PATCHv4 03/17] android/socket: Add get RFCOMM default channel Andrei Emeltchenko
2013-11-18 13:20 ` Andrei Emeltchenko [this message]
2013-11-18 13:20 ` [PATCHv4 05/17] android/socket: Implement socket accepted event Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 06/17] android/socket: Implement Android RFCOMM stack events Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 07/17] android/socket: Implement RFCOMM events Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 08/17] android/socket: Implement accept signal over Android fd Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 09/17] android/socket: Write channel to " Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 10/17] android/socket: Implement socket connect HAL method Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 11/17] android/socket: Parse SDP response and connect Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 12/17] android/socket: Implement HAL connect call Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 13/17] android/socket: Send RFCOMM channel to framework Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 14/17] android/socket: Send connect signal on connect Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 15/17] android/socket: Close file descriptor after sending Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 16/17] android/socket: Add SDP record for OPP profile Andrei Emeltchenko
2013-11-18 13:20 ` [PATCHv4 17/17] android/socket: Add MAS uuid to channel mapping 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=1384780854-20970-5-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;
as well as URLs for NNTP newsgroup(s).