Return-Path: Message-ID: <5339214E.700@linux.intel.com> Date: Mon, 31 Mar 2014 11:03:26 +0300 From: Ravi kumar Veeramally MIME-Version: 1.0 To: "linux-bluetooth@vger.kernel.org" Subject: Re: [RFC 0/3] Add HDP .register_application method References: <1395758081-22005-1-git-send-email-ravikumar.veeramally@linux.intel.com> <53357D91.3050601@linux.intel.com> In-Reply-To: <53357D91.3050601@linux.intel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-bluetooth-owner@vger.kernel.org List-ID: 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 >