From: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
Subject: [RFC 0/5] Implement MDL disconnect and reconnect
Date: Fri, 27 Jun 2014 00:30:41 +0300 [thread overview]
Message-ID: <1403818246-20205-1-git-send-email-ravikumar.veeramally@linux.intel.com> (raw)
Patshset introduces extra api in haltest tool (close_channel).
PTS test case for MDL disconnect and reconnect expects only
channel disconnection/close not deletion. It can not be called
with current HAL api. This call just shutdown specified fd, which
triggers channel disconnection. Another attempt for connection
means simply start with reconnect request.
Ravi kumar Veeramally (5):
android/client/health: Introduce close_channel API.
android/health: Implement mdl_closed_cb callback
android/health: Fix deleting channels queue
android/health: Implement mdl reconnect
android/health: Implement destroy_channel call
android/client/if-hl.c | 29 +++++++++++++++
android/health.c | 98 +++++++++++++++++++++++++++++++++++++++++++++++---
2 files changed, 122 insertions(+), 5 deletions(-)
--
1.9.1
next reply other threads:[~2014-06-26 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 21:30 Ravi kumar Veeramally [this message]
2014-06-26 21:30 ` [RFC 1/5] android/client/health: Introduce close_channel API Ravi kumar Veeramally
2014-06-26 21:30 ` [RFC 2/5] android/health: Implement mdl_closed_cb callback Ravi kumar Veeramally
2014-06-26 21:30 ` [RFC 3/5] android/health: Fix deleting channels queue Ravi kumar Veeramally
2014-06-26 21:30 ` [RFC 4/5] android/health: Implement mdl reconnect Ravi kumar Veeramally
2014-06-26 21:30 ` [RFC 5/5] android/health: Implement destroy_channel call Ravi kumar Veeramally
2014-06-27 14:13 ` Andrei Emeltchenko
2014-06-27 13:32 ` [RFC 0/5] Implement MDL disconnect and reconnect Szymon Janc
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=1403818246-20205-1-git-send-email-ravikumar.veeramally@linux.intel.com \
--to=ravikumar.veeramally@linux.intel.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).