From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez: Export SDP "Remote audio volume control" item for HSP profile
Date: Thu, 12 Dec 2019 21:42:27 +0200 [thread overview]
Message-ID: <CABBYNZKCovNDcAaMMeYZgKAAq-8oz+pcs6xmS3A_Qt-28aoEbQ@mail.gmail.com> (raw)
In-Reply-To: <20191212172944.hgt6se2qz2hpsbo2@pali>
Hi Pali,
On Thu, Dec 12, 2019 at 7:31 PM Pali Rohár <pali.rohar@gmail.com> wrote:
>
> Hello!
>
> According to HSP 1.2 specification, section 4.7 Remote Audio Volume
> Control, Support for remote audio volume control is optional, so an
> implementation may support none, either, or both of the controls for
> microphone volume and speaker volume.
>
> According to HSP 1.2 specification, section 5.3 SDP Interoperability
> Requirements, bluetooth device with HSP profile announce via SDP "Remote
> audio volume control" field information if device itself supports volume
> control.
>
> But currently I did not found any way how to access "Remote audio volume
> control" SDP field in (pulseaudio) application as bluez does not export
> it.
>
> Can you please export this field? E.g. for HFP profile all optional
> features from SDP are passed to NewConnection() DBus method via
> fd_properties dictionary under Features key. Could you export that
> "Remote audio volume control" bit for HSP profile in Features key?
>
> And in same way, this needs to be handled also in RegisterProfile() DBus
> method.
Do you have a use case in mind?
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2019-12-12 19:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 17:29 bluez: Export SDP "Remote audio volume control" item for HSP profile Pali Rohár
2019-12-12 19:42 ` Luiz Augusto von Dentz [this message]
2019-12-12 23:03 ` Pali Rohár
2020-02-09 13:02 ` Pali Rohár
2020-03-20 13:01 ` Pali Rohár
2020-03-20 17:48 ` Luiz Augusto von Dentz
2020-03-21 18:40 ` Pali Rohár
2020-03-21 19:54 ` Pali Rohár
2020-04-13 16:25 ` [PATCH 0/3] " Pali Rohár
2020-04-13 16:25 ` [PATCH 1/3] src/profile: Distinguish between zero-set HFP AG features and unset HFP AG features Pali Rohár
2020-04-13 16:44 ` Luiz Augusto von Dentz
2020-04-13 16:52 ` Pali Rohár
2020-04-13 16:58 ` Luiz Augusto von Dentz
2020-04-13 17:17 ` Pali Rohár
2020-04-13 17:47 ` Luiz Augusto von Dentz
2020-04-13 17:58 ` Pali Rohár
2020-04-13 19:41 ` Luiz Augusto von Dentz
2020-04-13 19:51 ` Pali Rohár
2020-04-13 20:24 ` Luiz Augusto von Dentz
2020-04-13 20:42 ` Pali Rohár
2020-04-13 21:07 ` Luiz Augusto von Dentz
2020-04-13 22:26 ` Pali Rohár
2020-04-13 16:25 ` [PATCH 2/3] src/profile: Export Remote Audio Volume Control SDP value for HSP HS role via first bit in features value Pali Rohár
2020-04-13 16:25 ` [PATCH 3/3] src/profile: Add default SDP record for Headset role of HSP 1.2 profile with Erratum 3507 Pali Rohár
2020-04-13 16:51 ` Luiz Augusto von Dentz
2020-04-14 0:09 ` [PATCH 0/3] bluez: Export SDP "Remote audio volume control" item for HSP profile Luiz Augusto von Dentz
2020-04-14 8:09 ` Pali Rohár
2020-04-14 19:53 ` Pali Rohár
2020-04-14 20:28 ` Luiz Augusto von Dentz
2020-04-14 20:46 ` [PATCH] doc: Update documentation for HSP and HFP profiles Pali Rohár
2020-04-14 21:03 ` Luiz Augusto von Dentz
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=CABBYNZKCovNDcAaMMeYZgKAAq-8oz+pcs6xmS3A_Qt-28aoEbQ@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pali.rohar@gmail.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).