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: [RFCv1 7/9] android/hal-sock: Implement RFCOMM events
Date: Mon, 11 Nov 2013 14:37:16 +0200	[thread overview]
Message-ID: <1384173438-21708-8-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1384173438-21708-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>

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

Copy data from RFCOMM socket to Android framework.
---
 android/socket.c |   29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/android/socket.c b/android/socket.c
index dfad9da..a962cdc 100644
--- a/android/socket.c
+++ b/android/socket.c
@@ -129,6 +129,35 @@ static gboolean sock_stack_event_cb(GIOChannel *io, GIOCondition cond,
 static gboolean sock_rfcomm_event_cb(GIOChannel *io, GIOCondition cond,
 								gpointer data)
 {
+	struct rfcomm_slot *rfslot = data;
+	unsigned char buf[1024] = { 0 };
+	int len;
+
+	DBG("rfslot: fd %d hal_fd %d real_sock %d chan %u sock %d",
+		rfslot->fd, rfslot->hal_fd, rfslot->real_sock, rfslot->channel,
+		g_io_channel_unix_get_fd(io));
+
+	if (cond & (G_IO_ERR | G_IO_HUP | G_IO_NVAL)) {
+		error("Socket error: sock %d cond %d",
+					g_io_channel_unix_get_fd(io), cond);
+		g_io_channel_shutdown(io, TRUE, NULL);
+		return FALSE;
+	}
+
+	/* FIXME check real_sock vs sock(io) */
+	len = recv(rfslot->real_sock, buf, sizeof(buf), 0);
+	if (len <= 0) {
+		error("recv(): %s sock %d", strerror(errno), rfslot->real_sock);
+		return FALSE;
+	}
+
+	DBG("read %d bytes, write to fd %d", len, rfslot->fd);
+
+	if (send(rfslot->fd, buf, len, MSG_DONTWAIT) < 0) {
+		error("send(): %s sock %d", strerror(errno), rfslot->fd);
+		return FALSE;
+	}
+
 	return TRUE;
 }
 
-- 
1.7.10.4


  parent reply	other threads:[~2013-11-11 12:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 12:37 [RFCv1 0/9] Socket HAL Andrei Emeltchenko
2013-11-11 12:37 ` [RFCv1 1/9] android/hal-sock: Add debug flag printing Andrei Emeltchenko
2013-11-11 12:37 ` [RFCv1 2/9] android: Avoid unneeded includes Andrei Emeltchenko
2013-11-11 13:20   ` Luiz Augusto von Dentz
2013-11-11 13:31     ` Szymon Janc
2013-11-11 12:37 ` [RFCv1 3/9] android/ahl-sock: Add connect signal to socket Andrei Emeltchenko
2013-11-11 12:37 ` [RFCv1 4/9] android/hal-sock: Initial listen handle Andrei Emeltchenko
2013-11-11 12:37 ` [RFCv1 5/9] android/hal-sock: Implement socket accepted event Andrei Emeltchenko
2013-11-11 12:37 ` [RFCv1 6/9] android/hal-sock: Implement Android RFCOMM stack events Andrei Emeltchenko
2013-11-11 12:37 ` Andrei Emeltchenko [this message]
2013-11-11 23:11   ` [RFCv1 7/9] android/hal-sock: Implement RFCOMM events Marcel Holtmann
2013-11-11 12:37 ` [RFCv1 8/9] android/hal-sock: Implement accept signal over Android fd Andrei Emeltchenko
2013-11-11 12:37 ` [RFCv1 9/9] android/hal-sock: Write channel to " Andrei Emeltchenko
  -- strict thread matches above, loose matches on Subject: below --
2013-11-11 14:03 [RFCv1 0/9] Socket HAL Andrei Emeltchenko
2013-11-11 14:03 ` [RFCv1 7/9] android/hal-sock: Implement RFCOMM events 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=1384173438-21708-8-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).