All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Tyszkowski <jakub.tyszkowski@tieto.com>
To: linux-bluetooth@vger.kernel.org
Cc: Jakub Tyszkowski <jakub.tyszkowski@tieto.com>
Subject: [PATCH 14/18] android/hal-gatt-api: Add Client Read Descriptor event
Date: Fri, 28 Feb 2014 11:23:59 +0100	[thread overview]
Message-ID: <1393583043-23455-14-git-send-email-jakub.tyszkowski@tieto.com> (raw)
In-Reply-To: <1393583043-23455-1-git-send-email-jakub.tyszkowski@tieto.com>

---
 android/hal-ipc-api.txt | 6 ++++++
 android/hal-msg.h       | 7 +++++++
 2 files changed, 13 insertions(+)

diff --git a/android/hal-ipc-api.txt b/android/hal-ipc-api.txt
index 1ce350d..a1852a6 100644
--- a/android/hal-ipc-api.txt
+++ b/android/hal-ipc-api.txt
@@ -1919,6 +1919,12 @@ Android HAL name: "gatt" (BT_PROFILE_GATT_ID)
 		Valid GATT Char. & Decr. ID: As described in Get Descriptor
 
 	Opcode 0x8e - Read Descriptor notification
+
+		Notification parameters: Connection ID (4 octets)
+		                         Status (4 octets)
+		                         GATT Read Parameters (variable)
+		Valid GATT Read Parameters: As described in Read Characteristic
+
 	Opcode 0x8f - Write Descriptor notification
 	Opcode 0x90 - Execute Write notification
 	Opcode 0x91 - Read Remote RSSI notification
diff --git a/android/hal-msg.h b/android/hal-msg.h
index c6d9ab4..3bf9c68 100644
--- a/android/hal-msg.h
+++ b/android/hal-msg.h
@@ -1364,3 +1364,10 @@ struct hal_ev_gatt_client_write_characteristic {
 	int32_t status;
 	struct hal_gatt_write_params data;
 } __attribute__((packed));
+
+#define HAL_EV_GATT_CLIENT_READ_DESCRIPTOR	0x8e
+struct hal_ev_gatt_client_read_descriptor {
+	int32_t conn_id;
+	int32_t status;
+	struct hal_gatt_read_params data;
+} __attribute__((packed));
-- 
1.9.0


  parent reply	other threads:[~2014-02-28 10:23 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 ` Jakub Tyszkowski [this message]
2014-02-28 10:24 ` [PATCH 15/18] android/hal-gatt-api: Add Client Write Descriptor event 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 ` [PATCH 01/18] android/hal-gatt-api: Add Client Register event Szymon Janc

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=1393583043-23455-14-git-send-email-jakub.tyszkowski@tieto.com \
    --to=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 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.