From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCHv4 12/17] android/socket: Implement HAL connect call
Date: Mon, 18 Nov 2013 15:20:49 +0200 [thread overview]
Message-ID: <1384780854-20970-13-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>
HAL connect uses similar event handlers like listen call.
---
android/socket.c | 43 ++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 42 insertions(+), 1 deletion(-)
diff --git a/android/socket.c b/android/socket.c
index 63c553a..5bedb60 100644
--- a/android/socket.c
+++ b/android/socket.c
@@ -380,8 +380,49 @@ static int handle_listen(void *buf)
return hal_fd;
}
-static void connect_cb(GIOChannel *io, GError *err, gpointer user_data)
+static void connect_cb(GIOChannel *io, GError *conn_err, gpointer user_data)
{
+ struct rfcomm_sock *rfsock = user_data;
+ GIOChannel *io_stack;
+ GError *io_err = NULL;
+ bdaddr_t dst;
+ char address[18];
+ int chan = -1;
+
+ bt_io_get(io, &io_err,
+ BT_IO_OPT_DEST_BDADDR, &dst,
+ BT_IO_OPT_INVALID);
+ if (io_err) {
+ error("%s", io_err->message);
+ g_error_free(io_err);
+ goto fail;
+ }
+
+ if (conn_err) {
+ error("%s", conn_err->message);
+ goto fail;
+ }
+
+ ba2str(&dst, address);
+ DBG("Connected to %s rfsock %p chan %d", address, rfsock, chan);
+
+ DBG("rfsock: fd %d real_sock %d chan %u sock %d",
+ rfsock->fd, rfsock->real_sock, rfsock->channel,
+ g_io_channel_unix_get_fd(io));
+
+ /* Handle events from Android */
+ io_stack = g_io_channel_unix_new(rfsock->fd);
+ g_io_add_watch(io_stack, G_IO_IN | G_IO_HUP | G_IO_ERR | G_IO_NVAL,
+ sock_stack_event_cb, rfsock);
+ g_io_channel_unref(io_stack);
+
+ /* Handle rfcomm events */
+ g_io_add_watch(io, G_IO_IN | G_IO_ERR | G_IO_HUP | G_IO_NVAL,
+ sock_rfcomm_event_cb, rfsock);
+
+ return;
+fail:
+ cleanup_rfsock(rfsock);
}
static void sdp_search_cb(sdp_list_t *recs, int err, gpointer data)
--
1.7.10.4
next prev 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 ` [PATCHv4 04/17] android/socket: Define structs and implement listen Andrei Emeltchenko
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 ` Andrei Emeltchenko [this message]
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-13-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).