linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santiago Carot-Nemesio <sancane@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Santiago Carot-Nemesio <sancane@gmail.com>
Subject: [PATCH 16/25] Implement function to send md_reconnect_mdl_req
Date: Fri, 14 May 2010 12:19:43 +0200	[thread overview]
Message-ID: <1273832392-18654-16-git-send-email-sancane@gmail.com> (raw)
In-Reply-To: <1273832392-18654-15-git-send-email-sancane@gmail.com>

---
 mcap/mcap.c |   51 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 51 insertions(+), 0 deletions(-)

diff --git a/mcap/mcap.c b/mcap/mcap.c
index c7bbb94..b4b8b09 100644
--- a/mcap/mcap.c
+++ b/mcap/mcap.c
@@ -262,6 +262,20 @@ static uint16_t generate_mdlid(struct mcap_mcl *mcl)
 	return mdlid;
 }
 
+static uint8_t *create_req(uint8_t op, uint16_t mdl_id)
+{
+	uint8_t *req;
+	mcap_md_req *req_cmd;
+
+	req = g_malloc0(sizeof(mcap_md_req));
+
+	req_cmd = (mcap_md_req *)req;
+	req_cmd->op = op;
+	req_cmd->mdl = htons(mdl_id);
+
+	return req;
+}
+
 static uint8_t *create_mdl_req(uint16_t mdl_id, uint8_t mdep, uint8_t conf)
 {
 	uint8_t *req;
@@ -357,6 +371,43 @@ void mcap_req_mdl_creation(struct mcap_mcl *mcl,
 									mcl);
 }
 
+void mcap_req_mdl_reconnect(struct mcap_mdl *mdl,
+				GError **err,
+				mcap_mdl_operation_cb reconnect_cb,
+				gpointer user_data)
+{
+	struct mcap_mdl_op_cb *con;
+	struct mcap_mcl *mcl = mdl->mcl;
+	uint8_t *cmd;
+
+	if (mdl->state != MDL_CLOSED) {
+		g_set_error(err, MCAP_ERROR, MCAP_ERROR_FAILED,
+					"MDL is not closed");
+		return;
+	}
+	con = g_new0(struct mcap_mdl_op_cb, 1);
+
+	cmd = create_req(MCAP_MD_RECONNECT_MDL_REQ, mdl->mdlid);
+	mcap_send_std_opcode(mcl, cmd, sizeof(mcap_md_req), err);
+	if (*err) {
+		g_free(con);
+		g_free(cmd);
+		return;
+	}
+
+	mdl->state = MDL_WAITING;
+
+	con->mdl = mdl;
+	con->cb.op = reconnect_cb;
+	con->user_data = user_data;
+
+	mcl->state = MCL_ACTIVE;
+	mcl->priv_data = con;
+
+	mcl->tid = g_timeout_add_seconds(RESPONSE_TIMER, wait_response_timer,
+									mcl);
+}
+
 static void update_mcl_state(struct mcap_mcl *mcl)
 {
 	GSList *l;
-- 
1.6.3.3


  reply	other threads:[~2010-05-14 10:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 10:19 [PATCH 01/25] Initial support for MCAP Santiago Carot-Nemesio
2010-05-14 10:19 ` [PATCH 02/25] Initial work to create MCAP instances Santiago Carot-Nemesio
2010-05-14 10:19   ` [PATCH 03/25] Initial work to process incomming connection of MCLs Santiago Carot-Nemesio
2010-05-14 10:19     ` [PATCH 04/25] Process events over Control Channels Santiago Carot-Nemesio
2010-05-14 10:19       ` [PATCH 05/25] Save and restore state of MCLs Santiago Carot-Nemesio
2010-05-14 10:19         ` [PATCH 06/25] Release MCAP instances Santiago Carot-Nemesio
2010-05-14 10:19           ` [PATCH 07/25] Process md_create_mdl_req in CONNECTED state Santiago Carot-Nemesio
2010-05-14 10:19             ` [PATCH 08/25] Process md_reconnect_mdl_req " Santiago Carot-Nemesio
2010-05-14 10:19               ` [PATCH 09/25] Process md_delete_mdl_req " Santiago Carot-Nemesio
2010-05-14 10:19                 ` [PATCH 10/25] Process md_abort_mdl_req in PENDING state Santiago Carot-Nemesio
2010-05-14 10:19                   ` [PATCH 11/25] Process commands in ACTIVE state Santiago Carot-Nemesio
2010-05-14 10:19                     ` [PATCH 12/25] Managing connection of Data Channels Santiago Carot-Nemesio
2010-05-14 10:19                       ` [PATCH 13/25] Enable connect operation to a remote MCAP instances Santiago Carot-Nemesio
2010-05-14 10:19                         ` [PATCH 14/25] Implement set callbacks operation over MCLs Santiago Carot-Nemesio
2010-05-14 10:19                           ` [PATCH 15/25] Implement function to send md_create_mdl_req Santiago Carot-Nemesio
2010-05-14 10:19                             ` Santiago Carot-Nemesio [this message]
2010-05-14 10:19                               ` [PATCH 17/25] Implement function to send md_delete_mdl_req Santiago Carot-Nemesio
2010-05-14 10:19                                 ` [PATCH 18/25] Implement function to send md_abort_mdl_req Santiago Carot-Nemesio
2010-05-14 10:19                                   ` [PATCH 19/25] Process response to std. op. codes Santiago Carot-Nemesio
2010-05-14 10:19                                     ` [PATCH 20/25] Process md_create_mdl_rsp Santiago Carot-Nemesio
2010-05-14 10:19                                       ` [PATCH 21/25] Process md_reconnect_mdl_rsp Santiago Carot-Nemesio
2010-05-14 10:19                                         ` [PATCH 22/25] Process md_abort_mdl_rsp Santiago Carot-Nemesio
2010-05-14 10:19                                           ` [PATCH 23/25] Process md_delete_mdl_rsp Santiago Carot-Nemesio
2010-05-14 10:19                                             ` [PATCH 24/25] Enable connection of Data Channel with remote MCAP instances Santiago Carot-Nemesio
2010-05-14 10:19                                               ` [PATCH 25/25] Initial support for clock synchronization protocol Santiago Carot-Nemesio

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=1273832392-18654-16-git-send-email-sancane@gmail.com \
    --to=sancane@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).