From: Santiago Carot-Nemesio <sancane@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Santiago Carot-Nemesio <sancane@gmail.com>
Subject: [PATCH 02/26] Initial work to create MCAP instances
Date: Fri, 4 Jun 2010 10:26:55 +0200 [thread overview]
Message-ID: <1275640039-7245-3-git-send-email-sancane@gmail.com> (raw)
In-Reply-To: <1275640039-7245-2-git-send-email-sancane@gmail.com>
---
mcap/mcap.c | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 files changed, 71 insertions(+), 2 deletions(-)
diff --git a/mcap/mcap.c b/mcap/mcap.c
index 535b8e3..f2c95fb 100644
--- a/mcap/mcap.c
+++ b/mcap/mcap.c
@@ -34,6 +34,18 @@
#include "mcap_lib.h"
#include "mcap_internal.h"
+#define MCAP_ERROR g_quark_from_static_string("mcap-error-quark")
+
+static void confirm_dc_event_cb(GIOChannel *chan, gpointer user_data)
+{
+ /* TODO */
+}
+
+static void confirm_mcl_event_cb(GIOChannel *chan, gpointer user_data)
+{
+ /* TODO */
+}
+
struct mcap_instance *mcap_create_instance(struct btd_adapter *btd_adapter,
BtIOSecLevel sec,
uint16_t ccpsm,
@@ -45,8 +57,65 @@ struct mcap_instance *mcap_create_instance(struct btd_adapter *btd_adapter,
mcap_mcl_event_cb mcl_uncached,
gpointer user_data)
{
- /* TODO */
- return NULL;
+ struct mcap_instance *ms;
+
+ if (sec < BT_IO_SEC_MEDIUM) {
+ g_set_error(gerr, MCAP_ERROR, MCAP_ERROR_INVALID_ARGS,
+ "Security level can't be minor of %d",
+ BT_IO_SEC_MEDIUM);
+ return NULL;
+ }
+
+ if (!(mcl_connected && mcl_reconnected &&
+ mcl_disconnected && mcl_uncached)) {
+ g_set_error(gerr, MCAP_ERROR, MCAP_ERROR_INVALID_ARGS,
+ "The callbacks can't be null");
+ return NULL;
+ }
+
+ ms = g_new0(struct mcap_instance, 1);
+
+ adapter_get_address(btd_adapter, &ms->src);
+
+ ms->sec = sec;
+ ms->mcl_connected_cb = mcl_connected;
+ ms->mcl_reconnected_cb = mcl_reconnected;
+ ms->mcl_disconnected_cb = mcl_disconnected;
+ ms->mcl_uncached_cb = mcl_uncached;
+ ms->user_data = user_data;
+
+ /* Listen incoming connections in control channel */
+ ms->ccio = bt_io_listen(BT_IO_L2CAP, NULL, confirm_mcl_event_cb, ms,
+ NULL, gerr,
+ BT_IO_OPT_SOURCE_BDADDR, &ms->src,
+ BT_IO_OPT_PSM, ccpsm,
+ BT_IO_OPT_MTU, MCAP_CC_MTU,
+ BT_IO_OPT_SEC_LEVEL, sec,
+ BT_IO_OPT_INVALID);
+ if (!ms->ccio) {
+ error("%s", (*gerr)->message);
+ g_free(ms);
+ return NULL;
+ }
+
+ /* Listen incoming connections in data channels */
+ ms->dcio = bt_io_listen(BT_IO_L2CAP, NULL, confirm_dc_event_cb, ms,
+ NULL, gerr,
+ BT_IO_OPT_SOURCE_BDADDR, &ms->src,
+ BT_IO_OPT_PSM, dcpsm,
+ BT_IO_OPT_MTU, MCAP_DC_MTU,
+ BT_IO_OPT_SEC_LEVEL, sec,
+ BT_IO_OPT_INVALID);
+ if (!ms->dcio) {
+ g_io_channel_shutdown(ms->ccio, TRUE, NULL);
+ g_io_channel_unref(ms->ccio);
+ ms->ccio = NULL;
+ error("%s", (*gerr)->message);
+ g_free(ms);
+ return NULL;
+ }
+
+ return ms;
}
void mcap_release_instance(struct mcap_instance *ms)
--
1.6.3.3
next prev parent reply other threads:[~2010-06-04 8:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 8:26 Patches for MCAP Santiago Carot-Nemesio
2010-06-04 8:26 ` [PATCH 01/26] Initial support " Santiago Carot-Nemesio
2010-06-04 8:26 ` Santiago Carot-Nemesio [this message]
2010-06-04 8:26 ` [PATCH 03/26] Initial work to process incomming connection of MCLs Santiago Carot-Nemesio
2010-06-04 8:26 ` [PATCH 04/26] Process events over Control Channels Santiago Carot-Nemesio
2010-06-04 8:26 ` [PATCH 05/26] Save and restore state of MCLs Santiago Carot-Nemesio
2010-06-04 8:26 ` [PATCH 06/26] Release MCAP instances Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 07/26] Process md_create_mdl_req in CONNECTED state Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 08/26] Process md_reconnect_mdl_req " Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 09/26] Process md_delete_mdl_req " Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 10/26] Process md_abort_mdl_req in PENDING state Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 11/26] Process commands in ACTIVE state Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 12/26] Managing connection of Data Channels Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 13/26] Enable connect operation to a remote MCAP instances Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 14/26] Implement set callbacks operation over MCLs Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 15/26] Implement function to send md_create_mdl_req Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 16/26] Implement function to send md_reconnect_mdl_req Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 17/26] Implement function to send md_delete_mdl_req Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 18/26] Implement function to send md_abort_mdl_req Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 19/26] Process response to std. op. codes Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 20/26] Process md_create_mdl_rsp Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 21/26] Process md_reconnect_mdl_rsp Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 22/26] Process md_abort_mdl_rsp Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 23/26] Process md_delete_mdl_rsp Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 24/26] Enable connection of Data Channel with remote MCAP instances Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 25/26] Initial support for clock synchronization protocol Santiago Carot-Nemesio
2010-06-04 8:27 ` [PATCH 26/26] Free memory when a unref operation happens over a cached MCL 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=1275640039-7245-3-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).