From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCHv6 03/19] android/socket: Implement listen on RFCOMM socket
Date: Wed, 20 Nov 2013 12:24:21 +0200 [thread overview]
Message-ID: <1384943077-5366-4-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1384943077-5366-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Handle HAL socket listen call. Create RFCOMM socket and wait for events.
---
android/socket.c | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/android/socket.c b/android/socket.c
index e19b2aa..b8d96f9 100644
--- a/android/socket.c
+++ b/android/socket.c
@@ -133,11 +133,17 @@ static struct profile_info *get_profile_by_uuid(const uint8_t *uuid)
return NULL;
}
+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 profile_info *profile;
struct rfcomm_sock *rfsock;
+ GIOChannel *io;
+ GError *err = NULL;
int hal_fd;
int chan;
@@ -155,6 +161,27 @@ static int handle_listen(void *buf)
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);
+
+ /* TODO: Add server watch */
+ g_io_channel_set_close_on_unref(io, TRUE);
+ g_io_channel_unref(io);
+
+ DBG("real_sock %d fd %d hal_fd %d", rfsock->real_sock, rfsock->fd,
+ hal_fd);
+
return hal_fd;
}
--
1.7.10.4
next prev parent reply other threads:[~2013-11-20 10:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 10:24 [PATCHv6 00/19] Socket HAL Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 01/19] android/socket: Add get RFCOMM default channel Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 02/19] android/socket: Handling rfcomm sockets Andrei Emeltchenko
2013-11-20 13:06 ` Johan Hedberg
2013-11-20 10:24 ` Andrei Emeltchenko [this message]
2013-11-20 10:24 ` [PATCHv6 04/19] android/socket: Implement socket accepted event Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 05/19] android/socket: Implement Android RFCOMM stack events Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 06/19] android/socket: Implement RFCOMM events Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 07/19] android/socket: Send accept signal to Android framework Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 08/19] android/socket: Notify channel " Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 09/19] android/socket: Implement socket connect HAL method Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 10/19] android/socket: Parse SDP response and connect Andrei Emeltchenko
2013-11-20 13:21 ` Johan Hedberg
2013-11-20 10:24 ` [PATCHv6 11/19] android/socket: Implement HAL connect call Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 12/19] android/socket: Send RFCOMM channel to framework Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 13/19] android/socket: Send connect signal to Android framework Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 14/19] android/socket: Close file descriptor after sending Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 15/19] android/socket: Add SDP record for OPP profile Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 16/19] android/socket: Add MAS uuid to profile table Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 17/19] android/socket: Add SPP " Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 18/19] android/socket: Add PBAP SDP record Andrei Emeltchenko
2013-11-20 10:24 ` [PATCHv6 19/19] android/socket: Add SPP " 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=1384943077-5366-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;
as well as URLs for NNTP newsgroup(s).