linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC 0/3] Add HDP .register_application method
Date: Mon, 31 Mar 2014 11:03:26 +0300	[thread overview]
Message-ID: <5339214E.700@linux.intel.com> (raw)
In-Reply-To: <53357D91.3050601@linux.intel.com>

ping.

On 03/28/2014 03:48 PM, Ravi kumar Veeramally wrote:
> ping.
>
> On 03/25/2014 04:34 PM, Ravi kumar Veeramally wrote:
>> 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    | 88 
>> ++++++++++++++++++++++++++++++++++++++++++++++++-
>>   android/hal-ipc-api.txt | 34 +++++++++++--------
>>   android/hal-msg.h       | 37 ++++++++++-----------
>>   3 files changed, 126 insertions(+), 33 deletions(-)
>>
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe 
> linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


      reply	other threads:[~2014-03-31  8:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 14:34 [RFC 0/3] Add HDP .register_application method Ravi kumar Veeramally
2014-03-25 14:34 ` [RFC 1/3] android/hal-ipc-api: Add extra command to Health HAL api document Ravi kumar Veeramally
2014-03-25 14:34 ` [RFC 2/3] android/hal-msg: Add extra struct for mdep data Ravi kumar Veeramally
2014-03-25 14:34 ` [RFC 3/3] android/hal-health: Add HDP .register_application method Ravi kumar Veeramally
2014-03-28 13:48 ` [RFC 0/3] " Ravi kumar Veeramally
2014-03-31  8:03   ` Ravi kumar Veeramally [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=5339214E.700@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).