linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Jakub Tyszkowski <jakub.tyszkowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 01/18] android/hal-gatt-api: Add Client Register event
Date: Sun, 02 Mar 2014 23:02:25 +0100	[thread overview]
Message-ID: <1720368.2O4kFFxrmM@leonov> (raw)
In-Reply-To: <1393583043-23455-1-git-send-email-jakub.tyszkowski@tieto.com>

Hi Jakub,

On Friday 28 of February 2014 11:23:46 Jakub Tyszkowski wrote:
> ---
>  android/hal-ipc-api.txt | 5 +++++
>  android/hal-msg.h       | 7 +++++++
>  2 files changed, 12 insertions(+)
> 
> diff --git a/android/hal-ipc-api.txt b/android/hal-ipc-api.txt
> index 1a19c80..58c05a9 100644
> --- a/android/hal-ipc-api.txt
> +++ b/android/hal-ipc-api.txt
> @@ -1797,6 +1797,11 @@ Android HAL name: "gatt" (BT_PROFILE_GATT_ID)
>  		In case of an error, the error response will be returned.
> 
>  	Opcode 0x81 - Register Client notification
> +
> +		Notification parameters: Status (4 octets)
> +		                         Client Interface (4 octets)
> +		                         UUID (16 octets)
> +
>  	Opcode 0x82 - Scan Result notification
>  	Opcode 0x83 - Connect Device notification
>  	Opcode 0x84 - Disconnect Device notification
> diff --git a/android/hal-msg.h b/android/hal-msg.h
> index bde9717..9f7f9e9 100644
> --- a/android/hal-msg.h
> +++ b/android/hal-msg.h
> @@ -1236,3 +1236,10 @@ struct hal_ev_avrcp_passthrough_cmd {
>  	uint8_t id;
>  	uint8_t state;
>  } __attribute__((packed));
> +
> +#define HAL_EV_GATT_CLIENT_REGISTER_CLIENT	0x81
> +struct hal_ev_gatt_client_register_client {
> +	int32_t status;
> +	int32_t client_if;
> +	uint8_t app_uuid[16];
> +} __attribute__((packed));

All patches in this set are now applied, thanks.

-- 
BR
Szymon Janc

      parent reply	other threads:[~2014-03-02 22:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 10:23 [PATCH 01/18] android/hal-gatt-api: Add Client Register event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 02/18] android/hal-gatt-api: Add Client Scan Result event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 03/18] android/hal-gatt-api: Add Client Connect event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 04/18] android/hal-gatt-api: Add Client Disconnect event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 05/18] android/hal-gatt-api: Add Client Search Complete event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 06/18] android/hal-gatt-api: Add Client Search Result event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 07/18] android/hal-gatt-api: Add Client Get Characteristic event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 08/18] android/hal-gatt-api: Add Client Get Descriptor event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 09/18] android/hal-gatt-api: Add Client Get Included Service event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 10/18] android/hal-gatt-api: Add Client Register for Notification event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 11/18] android/hal-gatt-api: Add Client Notify event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 12/18] android/hal-gatt-api: Add Client Read Characteristic event Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 13/18] android/hal-gatt-api: Add Client Write " Jakub Tyszkowski
2014-02-28 10:23 ` [PATCH 14/18] android/hal-gatt-api: Add Client Read Descriptor event Jakub Tyszkowski
2014-02-28 10:24 ` [PATCH 15/18] android/hal-gatt-api: Add Client Write " Jakub Tyszkowski
2014-02-28 10:24 ` [PATCH 16/18] android/hal-gatt-api: Add Client Exec Write event Jakub Tyszkowski
2014-02-28 10:24 ` [PATCH 17/18] android/hal-gatt-api: Add Client Read Remote RSSI event Jakub Tyszkowski
2014-02-28 10:24 ` [PATCH 18/18] android/hal-gatt-api: Add Client Listen event Jakub Tyszkowski
2014-03-02 22:02 ` 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=1720368.2O4kFFxrmM@leonov \
    --to=szymon.janc@tieto.com \
    --cc=jakub.tyszkowski@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 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).