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 v2 0/2] Code handling for VOCS service
Date: Wed, 7 Jun 2023 15:13:40 +0300 [thread overview]
Message-ID: <20230607121342.6136-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
All the code implementation has been tested using PTS testing the verdict is PASS for all mandatory test cases.
Thank you in advance for your review.
Warm Regards
Nitin Jadhav
Nitin Jadhav (2):
Added initial code for handling VOCS
Fixed the following issue observed during PTS testing for mandatory
test cases - Specified Upper and Lower Limit for Volume offset -
Corrected the number of handles for VOCS - VOCS is made as included
service of VCS because VOCS is secondary service and VSC is primary
service
lib/uuid.h | 5 +
src/shared/vcp.c | 552 ++++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 555 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2023-06-07 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 12:13 Nitin Jadhav [this message]
2023-06-07 12:13 ` [PATCH BlueZ v2 1/2] Added initial code for handling VOCS Nitin Jadhav
2023-06-07 12:24 ` Paul Menzel
2023-06-07 13:37 ` Code handling for VOCS service bluez.test.bot
2023-06-07 12:13 ` [PATCH BlueZ v2 2/2] 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=20230607121342.6136-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).