From: Szymon Janc <szymon.janc@tieto.com>
To: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH_v3 0/6] Initial implementation for MCAP data channel
Date: Mon, 23 Jun 2014 11:15:31 +0200 [thread overview]
Message-ID: <15258901.WdTfi0p35E@uw000953> (raw)
In-Reply-To: <1403438341-14321-1-git-send-email-ravikumar.veeramally@linux.intel.com>
Hi Ravi,
On Sunday 22 of June 2014 14:58:55 Ravi kumar Veeramally wrote:
> v3: Fixed Szymon's comments.
>
> v2: Few cleanups and support for streaming data channel.
>
> v1: Patchset implements initial MCAP MDL creation and connection. On
> successful MDL (reliable) connection fd will be passed to HAL.
>
> PTS tests:
>
> TC_SRC_CC_BV_03_C:
>
> hl register_application bluez-android Bluez bluez-hdp health-device-profile 1 BTHL_MDEP_ROLE_SOURCE 4100 BTHL_CHANNEL_TYPE_RELIABLE pulse-oximeter
>
> hl connect_channel 1 00:1b:dc:05:b5:54 0
>
> TC_SRC_CC_BV_07_C:
>
> hl register_application bluez-android Bluez bluez-hdp health-device-profile 2 BTHL_MDEP_ROLE_SOURCE 4100 BTHL_CHANNEL_TYPE_RELIABLE pulse-oximeter BTHL_MDEP_ROLE_SOURCE 4100 BTHL_CHANNEL_TYPE_STREAMING pulse-oximeter
>
> hl connect_channel 1 00:1b:dc:05:b5:54 0
> hl connect_channel 1 00:1b:dc:05:b5:54 1
>
>
> TC_SNK_CC_BV_04_C:
> TC_SNK_HCT_BV_01_I:
>
> hl register_application bluez-android Bluez bluez-hdp health-device-profile 1 BTHL_MDEP_ROLE_SINK 4100 BTHL_CHANNEL_TYPE_RELIABLE pulse-oximeter
>
> hl connect_channel 1 00:1b:dc:05:b5:54 0
>
>
> TC_SNK_CC_BV_08_C:
>
> hl register_application bluez-android Bluez bluez-hdp health-device-profile 2 BTHL_MDEP_ROLE_SINK 4100 BTHL_CHANNEL_TYPE_RELIABLE pulse-oximeter BTHL_MDEP_ROLE_SINK 4100 BTHL_CHANNEL_TYPE_STREAMING pulse-oximeter
>
> hl connect_channel 1 00:1b:dc:05:b5:54 0
> hl connect_channel 1 00:1b:dc:05:b5:54 1
>
>
> Ravi kumar Veeramally (6):
> android/health: Check if device and channel already exists or not
> android/health: Cache remote mdep id on channel connect request
> android/health: Notify channel status on channel destroy call
> android/health: Create and connect MDL
> android/health: Implement mcap_mdl_deleted_cb
> anrdroid/client/health: Cache fd and close on channel disconnection
>
> android/client/if-hl.c | 9 ++
> android/health.c | 415 +++++++++++++++++++++++++++++++++++++++++++------
> 2 files changed, 376 insertions(+), 48 deletions(-)
>
>
All patches are now applied, thanks.
--
Best regards,
Szymon Janc
prev parent reply other threads:[~2014-06-23 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 11:58 [PATCH_v3 0/6] Initial implementation for MCAP data channel Ravi kumar Veeramally
2014-06-22 11:58 ` [PATCH_v3 1/6] android/health: Check if device and channel already exists or not Ravi kumar Veeramally
2014-06-22 11:58 ` [PATCH_v3 2/6] android/health: Cache remote mdep id on channel connect request Ravi kumar Veeramally
2014-06-22 11:58 ` [PATCH_v3 3/6] android/health: Notify channel status on channel destroy call Ravi kumar Veeramally
2014-06-22 11:58 ` [PATCH_v3 4/6] android/health: Create and connect MDL Ravi kumar Veeramally
2014-06-22 11:59 ` [PATCH_v3 5/6] android/health: Implement mcap_mdl_deleted_cb Ravi kumar Veeramally
2014-06-22 11:59 ` [PATCH_v3 6/6] anrdroid/client/health: Cache fd and close on channel disconnection Ravi kumar Veeramally
2014-06-23 9:15 ` Szymon Janc [this message]
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=15258901.WdTfi0p35E@uw000953 \
--to=szymon.janc@tieto.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravikumar.veeramally@linux.intel.com \
/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