From: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
Subject: [PATCH_v4 00/12] Implemented hid interfaces in daemon and HAL
Date: Tue, 5 Nov 2013 23:09:06 +0200 [thread overview]
Message-ID: <1383685758-3900-1-git-send-email-ravikumar.veeramally@linux.intel.com> (raw)
v4: Fixed Johan's comments (length issue and single byte array)
v3: Wrong order of patches
v2: Fixed Johan's comments (splitting of patches, proper function and
struct names, update hal-msg.h and ipc document, alignment issues
removed pointer from ipc struct)
v1: This patch set implements get/set protocol and get/set report
interfaces and supported functionality in daemon. Sending notifications
and notification handling in hal. Few naming fixes and error handling.
And last handling of few uHID events.
Ravi kumar Veeramally (12):
android/hid: Implement hid get protocol in daemon
android/hid: Implement hid set protocol in daemon
android/hid: Handle protocol mode notification in HAL
android/hid: Add hid event get report structure to HAL msg headers
android/hid: Implement hid get report in daemon
android/hid: Add missing set report parameters to ipc document
android/hid: Implement hid set report in daemon
android/hid: Handle get report notification in HAL
android/hid: Replace header checking magic number with defines
android/hid: Handle invalid parameters in HAL
android/hid: Handle uhid events
android/hid: Align hal hid struct variables properly
android/hal-hidhost.c | 41 +++++-
android/hal-ipc-api.txt | 4 +-
android/hal-msg.h | 32 +++--
android/hid.c | 325 ++++++++++++++++++++++++++++++++++++++++++++++--
4 files changed, 372 insertions(+), 30 deletions(-)
--
1.8.1.2
next reply other threads:[~2013-11-05 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 21:09 Ravi kumar Veeramally [this message]
2013-11-05 21:09 ` [PATCH_v4 01/12] android/hid: Implement hid get protocol in daemon Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 02/12] android/hid: Implement hid set " Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 03/12] android/hid: Handle protocol mode notification in HAL Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 04/12] android/hid: Add hid event get report structure to HAL msg headers Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 05/12] android/hid: Implement hid get report in daemon Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 06/12] android/hid: Add missing set report parameters to ipc document Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 07/12] android/hid: Implement hid set report in daemon Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 08/12] android/hid: Handle get report notification in HAL Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 09/12] android/hid: Replace header checking magic number with defines Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 10/12] android/hid: Handle invalid parameters in HAL Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 11/12] android/hid: Handle uhid events Ravi kumar Veeramally
2013-11-05 21:09 ` [PATCH_v4 12/12] android/hid: Align hal hid struct variables properly Ravi kumar Veeramally
2013-11-06 8:37 ` [PATCH_v4 00/12] Implemented hid interfaces in daemon and HAL Johan Hedberg
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=1383685758-3900-1-git-send-email-ravikumar.veeramally@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