From: Nitin Jadhav <nitin.jadhav@nxp.com>
To: linux-bluetooth@vger.kernel.org
Cc: devyani.godbole@nxp.com, mihai-octavian.urzica@nxp.com,
silviu.barbulescu@nxp.com, nitin.jadhav@nxp.com
Subject: [PATCH BlueZ v4 0/3] Code handling for VOCS service
Date: Fri, 9 Jun 2023 15:12:19 +0530 [thread overview]
Message-ID: <20230609094222.1877-1-nitin.jadhav@nxp.com> (raw)
Hello Maintainers
This patch series handles code implementation for mandatory features of Volume Offset Control Service.
Implementation of following features have been handled in this patch series
- Volume Offset Control Service
- Volume Offset State Characteristic (Read, Notify)
- Audio Location Characteristic (Read)
- Volume Offset Control Point Characteristic (Write)
- Audio Output Description Characteristic (Read)
- Set Volume Offset
Reference Document:
- Code implementation is based on VOCS_v1.0.pdf
- Testing is done using PTS in reference to VOCS.TS.p1.pdf
- The verdict is PASS for all mandatory test cases.
Thank you in advance for your review.
Warm Regards
Nitin Jadhav
Nitin Jadhav (3):
lib/uuid.h: Add VOCS characteristic uuid(s)
shared/vcp: Add initial code for handling VOCS
shared/vcp.c: Make VOCS (Secondary) as an included service of VCS
(Primary)
lib/uuid.h | 5 +
src/shared/vcp.c | 564 ++++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 567 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2023-06-09 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 9:42 Nitin Jadhav [this message]
2023-06-09 9:42 ` [PATCH BlueZ v4 1/3] lib/uuid.h: Add VOCS characteristic uuid(s) Nitin Jadhav
2023-06-09 11:33 ` Code handling for VOCS service bluez.test.bot
2023-06-09 9:42 ` [PATCH BlueZ v4 2/3] shared/vcp: Add initial code for handling VOCS Nitin Jadhav
2023-06-09 9:42 ` [PATCH BlueZ v4 3/3] shared/vcp.c: Make VOCS (Secondary) as an included service of VCS (Primary) Nitin Jadhav
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=20230609094222.1877-1-nitin.jadhav@nxp.com \
--to=nitin.jadhav@nxp.com \
--cc=devyani.godbole@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mihai-octavian.urzica@nxp.com \
--cc=silviu.barbulescu@nxp.com \
/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).