Linux bluetooth development
 help / color / mirror / Atom feed
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_v2 0/3] Add HDP .register_application method
Date: Mon, 31 Mar 2014 15:49:41 +0200	[thread overview]
Message-ID: <1884435.E5HBSYUjjS@uw000953> (raw)
In-Reply-To: <1396271615-10221-1-git-send-email-ravikumar.veeramally@linux.intel.com>

Hi Ravi,

On Monday 31 of March 2014 16:13:32 Ravi kumar Veeramally wrote:
> v2: Fixed Szymon's comments (response: app_id will be returned
>     in response to HAL_OP_HEALTH_REG_APP ipc command).
> v1: Fixed Szymon's comments(copy terminating character null
>     also from HAL data(names, descriptions).
> 
> RFC: Due to limited IPC_MTU and variable length of
> fields from 'bthl_reg_param_t *', it is difficult to put them
> in single command and send though IPC. So we split this command
> to multiple calls. First command will be called with opcode of
> HAL_OP_HEALTH_REG_APP with 'struct hal_cmd_health_reg_app' data.
> Later command will be called with opcode of
> HAL_OP_HEALTH_MDEP with 'struct hal_cmd_health_mdep' data for
> number_of_mdeps times. Daemon (android/health) side it will
> process after it received all data and response will be sent
> along with last call of HAL_OP_HEALTH_MDEP.
> 
> This avoids increasing value of IPC_MTU and mainly because of
> optional parameters in 'bthl_reg_param_t'. Incase of unfilled
> optional parameters, fixed size arrays in hal commands will be
> empty.
> 
> Ravi kumar Veeramally (3):
>   android/hal-ipc-api: Add extra command to Health HAL api document
>   android/hal-msg: Add extra struct for mdep data
>   android/hal-health: Add HDP .register_application method
> 
>  android/hal-health.c    | 83 ++++++++++++++++++++++++++++++++++++++++++++++++-
>  android/hal-ipc-api.txt | 35 +++++++++++++--------
>  android/hal-msg.h       | 37 +++++++++++-----------
>  3 files changed, 122 insertions(+), 33 deletions(-)
>

All three patches are now upstream, thanks. 

-- 
Best regards, 
Szymon Janc

      parent reply	other threads:[~2014-03-31 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 13:13 [PATCH_v2 0/3] Add HDP .register_application method Ravi kumar Veeramally
2014-03-31 13:13 ` [PATCH_v2 1/3] android/hal-ipc-api: Add extra command to Health HAL api document Ravi kumar Veeramally
2014-03-31 13:13 ` [PATCH_v2 2/3] android/hal-msg: Add extra struct for mdep data Ravi kumar Veeramally
2014-03-31 13:13 ` [PATCH_v2 3/3] android/hal-health: Add HDP .register_application method Ravi kumar Veeramally
2014-03-31 13:49 ` 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=1884435.E5HBSYUjjS@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