From: "Pali Rohár" <pali.rohar@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>,
linux-bluetooth@vger.kernel.org,
General PulseAudio Discussion
<pulseaudio-discuss@lists.freedesktop.org>,
ofono@ofono.org, devkit-devel@lists.freedesktop.org,
Bastien Nocera <hadess@hadess.net>, Georg Chini <georg@chini.tk>,
Russell Treleaven <rtreleaven@bunnykick.ca>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Tanu Kaskinen <tanuk@iki.fi>,
Arun Raghavan <arun@arunraghavan.net>,
Marcel Holtmann <marcel@holtmann.org>,
Sebastian Reichel <sre@ring0.de>, Pavel Machek <pavel@ucw.cz>,
Wim Taymans <wim.taymans@gmail.com>,
George Kiagiadakis <george.kiagiadakis@collabora.com>
Subject: Re: Proposal for a new API and usage of Bluetooth HSP and HFP profiles on Linux
Date: Sat, 7 Dec 2019 21:09:42 +0100 [thread overview]
Message-ID: <20191207200942.nbao4mxsqw4sp67v@pali> (raw)
In-Reply-To: <20191201185740.uot7zb2s53p5gu7z@pali>
[-- Attachment #1: Type: text/plain, Size: 4148 bytes --]
+Denis from ofono
ofono and pulseaudio are two main users of HFP profile on Linux...
On Sunday 01 December 2019 19:57:40 Pali Rohár wrote:
> Hello!
>
> I'm sending this email to relevant mailing lists and other people who
> could be interested in it. (I'm not subscribed to all of ML, so please
> CC me when replying).
>
>
> I would like to open a discussion about a completely new way of handling
> Bluetooth HSP and HFP profiles on Linux. These two profiles are the only
> standard way how to access microphone data from Bluetooth Headsets.
>
>
> Previously in bluez4, HFP profile was implemented by bluez daemon and
> telephony HFP functionality was provided by either dummy modem, ofono
> modem or by Nokia's CSD Maemo modem.
>
> In bluez5 version was modem code together with implementation of HFP
> profile removed. And let implementation of HSP and HFP profiles to
> external application.
>
> Currently HSP profile is implemented in pulseaudio daemon to handle
> microphone and Bluetooth speakers. HFP profile is not implemented yet.
>
>
> HSP and HFP profiles use AT modem commands, so its implementation needs
> to parse and generates AT commands, plus implement needed state machine
> for it.
>
> And now problem is that last version of HFP profile specification is too
> complicated, plus Bluetooth headsets vendors started to inventing and
> using of own custom extensions to HFP profile and AT commands.
>
> Main problem of this "external" implementation outside of bluez is that
> only one application can communicate with remote Bluetooth device. It
> is application which received needed socket from bluez.
>
> So in this design if audio daemon (pulseaudio) implements HFP profile
> for processing audio, and e.g. power supply application wants to
> retrieve battery level from Bluetooth device, it means that audio daemon
> needs to implement also battery related functionality.
>
> It does not make sense to force power supply daemon (upower) to
> implement audio routing/encoding/decoding or audio daemon (power supply)
> to force implementing battery related operations.
>
>
> For handle this problem I would like to propose a new way how to use and
> implement HSP and HFP profiles on Linux.
>
> Implement a new HSP/HFP daemon (I called it hsphfpd) which register HSP
> and HFP profiles in bluez and then exports functionality for all other
> specific applications via DBus API (API for audio, power supply, input
> layer, telephony functions, vendor extensions, etc...). So it would acts
> as proxy daemon between bluez and target applications (pulseaudio,
> upower, ofono, ...)
>
> This would simplify whole HFP usage as applications would not need to
> re-implement parsing and processing of AT commands and it would allow
> more applications to use HFP profile at one time. And also it means that
> audio software does not have to implement telephony stack or power
> supply operations.
>
>
> I wrote a document how such DBus API could look like, see here:
>
> https://github.com/pali/hsphfpd-prototype/raw/prototype/hsphfpd.txt
>
>
> And also I implemented "prototype" implementation to verify that
> designed API make sense and can be really implemented. Prototype fully
> supports HSP profile in both HS and AG role, plus HFP profile in HF
> role. This prototype implementation is available here:
>
> https://github.com/pali/hsphfpd-prototype
>
> Some other details are written in README:
>
> https://github.com/pali/hsphfpd-prototype/raw/prototype/README
>
>
> What do you think about it? Does it make sense to have such design?
> Would you accept usage of such hsphfpd daemon, implemented according to
> specification, on Linux desktop?
>
> I would like to hear your opinion if I should continue with this hsphfpd
> design, or not.
>
>
> With this design and implementation of hsphfpd is possible to easily fix
> pulseaudio issue about power supply properties:
>
> https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/722
>
>
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-12-07 20:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 18:57 Proposal for a new API and usage of Bluetooth HSP and HFP profiles on Linux Pali Rohár
2019-12-02 17:01 ` [pulseaudio-discuss] " Tanu Kaskinen
2019-12-02 18:45 ` Pali Rohár
2019-12-04 15:15 ` Arun Raghavan
2019-12-04 17:05 ` Pali Rohár
2019-12-05 9:32 ` Pali Rohár
2019-12-15 22:11 ` Luiz Augusto von Dentz
2019-12-16 9:15 ` Pali Rohár
2019-12-17 23:47 ` Luiz Augusto von Dentz
2019-12-18 8:30 ` Pali Rohár
2019-12-18 17:00 ` Denis Kenzior
2019-12-18 17:28 ` Pali Rohár
2019-12-18 17:36 ` Pali Rohár
2019-12-18 20:53 ` Denis Kenzior
2019-12-18 21:33 ` Pali Rohár
2019-12-19 1:03 ` Denis Kenzior
2019-12-19 9:51 ` Pali Rohár
2019-12-19 14:53 ` Denis Kenzior
2019-12-19 15:33 ` Pali Rohár
2019-12-20 21:19 ` Denis Kenzior
2019-12-20 22:46 ` Pali Rohár
2020-01-04 10:51 ` Pali Rohár
2020-01-07 17:35 ` Denis Kenzior
2020-01-07 19:01 ` Pali Rohár
2019-12-02 19:49 ` Sebastian Reichel
2019-12-07 20:09 ` Pali Rohár [this message]
2019-12-09 9:43 ` George Kiagiadakis
2019-12-09 11:07 ` Pali Rohár
2020-03-15 14:17 ` Pali Rohár
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=20191207200942.nbao4mxsqw4sp67v@pali \
--to=pali.rohar@gmail.com \
--cc=arun@arunraghavan.net \
--cc=denkenz@gmail.com \
--cc=devkit-devel@lists.freedesktop.org \
--cc=georg@chini.tk \
--cc=george.kiagiadakis@collabora.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=ofono@ofono.org \
--cc=pavel@ucw.cz \
--cc=pulseaudio-discuss@lists.freedesktop.org \
--cc=rtreleaven@bunnykick.ca \
--cc=sre@ring0.de \
--cc=tanuk@iki.fi \
--cc=wim.taymans@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