From: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
To: Andrzej Kaczmarek <andrzej.kaczmarek@tieto.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 06/15] android/hal-msg: Add HDP app channel state event struct
Date: Wed, 12 Mar 2014 19:36:24 +0200 [thread overview]
Message-ID: <53209B18.5000003@linux.intel.com> (raw)
In-Reply-To: <CAF3PWx11bdQfjfGmVRBvVagfA0tn81arDKzWw_K8T9+MuK+v2A@mail.gmail.com>
Hi,
On 03/12/2014 05:57 PM, Andrzej Kaczmarek wrote:
> Hi Ravi,
>
> On 12 March 2014 16:10, Ravi kumar Veeramally
> <ravikumar.veeramally@linux.intel.com> wrote:
>> ---
>> android/hal-msg.h | 16 ++++++++++++++++
>> 1 file changed, 16 insertions(+)
>>
>> diff --git a/android/hal-msg.h b/android/hal-msg.h
>> index 694529f..0139543 100644
>> --- a/android/hal-msg.h
>> +++ b/android/hal-msg.h
>> @@ -1001,12 +1001,28 @@ struct hal_ev_pan_conn_state {
>> #define HAL_HEALTH_APP_DEREG_SUCCESS 0x02
>> #define HAL_HEALTH_APP_DEREG_FAILED 0x03
>>
>> +#define HAL_HEALTH_CHANL_STATE_CONNECTING 0x00
>> +#define HAL_HEALTH_CHANL_STATE_CONNECTED 0x01
>> +#define HAL_HEALTH_CHANL_STATE_DISCONNECTING 0x02
>> +#define HAL_HEALTH_CHANL_STATE_DISCONNECTED 0x03
>> +#define HAL_HEALTH_CHANL_STATE_DESTROYED 0x04
>> +
>> #define HAL_EV_HEALTH_APP_REG_STATE 0x81
>> struct hal_ev_health_app_reg_state {
>> uint16_t id;
>> uint8_t state;
>> } __attribute__((packed));
>>
>> +#define HAL_EV_HEALTH_CHNL_STATE 0x82
> You have CHNL here and CHANL in states definitions - better have them
> consistent. I guess either CHAN or CHANNEL would be actually better.
Ok, I will fix.
>> +struct hal_ev_health_chnl_state {
>> + uint16_t app_id;
>> + uint8_t bdaddr[6];
>> + uint8_t mdep_index;
>> + uint16_t chnl_id;
>> + uint8_t chnl_state;
> Same here - chan or channel.
>
>> + uint32_t file_descr;
> fd shall be passed as auxiliary data - there's parameter for this in
> IPC calls. Now you just pass plain int value which is useless as fd.
OK.
Thanks,
Ravi.
next prev parent reply other threads:[~2014-03-12 17:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 15:10 [PATCH 00/15] Add HDP profile support at HAL side Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 01/15] android/hal-msg: Add HDP app registration struct Ravi kumar Veeramally
2014-03-12 15:39 ` Luiz Augusto von Dentz
2014-03-12 17:39 ` Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 02/15] android/hal-msg: Add HDP app unregistration struct Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 03/15] android/hal-msg: Add HDP connect channel struct Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 04/15] android/hal-msg: Add HDP destroy " Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 05/15] android/hal-msg: Add HDP app registration state event struct Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 06/15] android/hal-msg: Add HDP app channel " Ravi kumar Veeramally
2014-03-12 15:57 ` Andrzej Kaczmarek
2014-03-12 17:36 ` Ravi kumar Veeramally [this message]
2014-03-12 15:10 ` [PATCH 07/15] android/hal-health: Add hal-health file Ravi kumar Veeramally
2014-03-12 19:53 ` Szymon Janc
2014-03-12 15:10 ` [PATCH 08/15] android/hal-health: Add HDP .init method Ravi kumar Veeramally
2014-03-12 19:56 ` Szymon Janc
2014-03-12 15:10 ` [PATCH 09/15] android/hal-health: Add HDP .cleanup method Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 10/15] android/hal-health: Add HDP .register_application method Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 11/15] android/hal-health: Add HDP .unregister_application method Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 12/15] android/hal-health: Add HDP .connect_channel method Ravi kumar Veeramally
2014-03-12 20:05 ` Szymon Janc
2014-03-13 9:22 ` Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 13/15] android/hal-health: Add HDP .destroy_channel method Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 14/15] android/hal-health: Add app state and channel state event handlers Ravi kumar Veeramally
2014-03-12 15:10 ` [PATCH 15/15] android/health: Add health.c|h file with basic calls Ravi kumar Veeramally
2014-03-12 15:18 ` Grzegorz Kolodziejczyk
2014-03-12 17:37 ` Ravi kumar Veeramally
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=53209B18.5000003@linux.intel.com \
--to=ravikumar.veeramally@linux.intel.com \
--cc=andrzej.kaczmarek@tieto.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.