From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCHv5 11/19] android/socket: Implement HAL connect call
Date: Tue, 19 Nov 2013 15:30:01 +0200 [thread overview]
Message-ID: <1384867809-18135-12-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1384867809-18135-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 | 41 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/android/socket.c b/android/socket.c
index 6d9c69e..ad09a2c 100644
--- a/android/socket.c
+++ b/android/socket.c
@@ -395,6 +395,47 @@ static int handle_listen(void *buf)
static void connect_cb(GIOChannel *io, GError *err, gpointer user_data)
{
+ struct rfcomm_sock *rfsock = user_data;
+ GIOChannel *io_stack;
+ GError *gerr = NULL;
+ bdaddr_t dst;
+ char address[18];
+ int chan = -1;
+
+ if (err) {
+ error("%s", err->message);
+ goto fail;
+ }
+
+ bt_io_get(io, &gerr,
+ BT_IO_OPT_DEST_BDADDR, &dst,
+ BT_IO_OPT_INVALID);
+ if (gerr) {
+ error("%s", gerr->message);
+ g_error_free(gerr);
+ 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-19 13:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 13:29 [PATCHv5 00/19] Socket HAL Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 01/19] android/hal-sock: Print bdaddr string instead of pointer Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 02/19] android/socket: Add get RFCOMM default channel Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 03/19] android/socket: Define structs and implement listen Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 04/19] android/socket: Implement socket accepted event Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 05/19] android/socket: Implement Android RFCOMM stack events Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 06/19] android/socket: Implement RFCOMM events Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 07/19] android/socket: Send accept signal to Android through hal_fd Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 08/19] android/socket: Write channel to Android fd Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 09/19] android/socket: Implement socket connect HAL method Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 10/19] android/socket: Parse SDP response and connect Andrei Emeltchenko
2013-11-19 13:30 ` Andrei Emeltchenko [this message]
2013-11-19 13:30 ` [PATCHv5 12/19] android/socket: Send RFCOMM channel to framework Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 13/19] android/socket: Send connect signal on connect Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 14/19] android/socket: Close file descriptor after sending Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 15/19] android/socket: Add SDP record for OPP profile Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 16/19] android/socket: Add MAS uuid to profile table Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 17/19] android/socket: Add SPP " Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 18/19] android/socket: Add PBAP SDP record Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 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=1384867809-18135-12-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).