From: "Frédéric Danis" <frederic.danis@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: [RFC v4 0/6] Add org.bluez.Telephony interface
Date: Mon, 12 Dec 2011 11:49:08 +0100 [thread overview]
Message-ID: <1323686954-11899-1-git-send-email-frederic.danis@linux.intel.com> (raw)
Hello,
This set of patches replaces telephony drivers for HeadSet/HandsFree
Profiles by a new DBus interface (org.bluez.Telephony).
External applications, which should implement AT parsing and telephony
part of HeadSet or HandsFree Profiles, will have to register a telephony
agent using this new interface.
First patch add the new org.bluez.Telephony interface and remove
functions related to AT parsing from audio/headset.c.
Second, third and fourth patches remove the telephony drivers (dummy,
maemo5, maemo6 and ofono), functions used by telephony drivers and no
more needed methods of org.bluez.Headset interface.
Fifth patch move the HS/HF AG rfcomm servers from audio/manager.c to
audio/telephony.c.
Rfcomm server for a specific profile is only started (and the related
sdp records advertised) when an agent register for it.
Sixth patch passes MediaTransport path to the agent during
NewConnection mehod call. So, telephony agent will be able to set NREC
and ringtone, which can in turn notify Pulse Audio of property changed.
Any comments appreciated
Regards
Fred
Frédéric Danis (6):
audio: Move tel drivers to DBus interface
audio: Remove tel drivers
audio: Remove maemo5 tel driver
audio: Remove maemo6 tel driver
audio: Move HFP/HSP AG servers to telephony.c
audio: Send transport path to telephony agent
Makefile.am | 17 +-
audio/headset.c | 1583 ++--------------------------------
audio/headset.h | 14 +-
audio/manager.c | 390 +--------
audio/media.c | 9 +-
audio/telephony-dummy.c | 433 ---------
audio/telephony-maemo5.c | 2104 --------------------------------------------
audio/telephony-maemo6.c | 2201 ----------------------------------------------
audio/telephony-ofono.c | 1638 ----------------------------------
audio/telephony.c | 968 ++++++++++++++++++++
audio/telephony.h | 198 +----
audio/transport.c | 10 +
audio/unix.c | 2 +
doc/assigned-numbers.txt | 1 +
doc/audio-api.txt | 166 ++--
15 files changed, 1155 insertions(+), 8579 deletions(-)
delete mode 100644 audio/telephony-dummy.c
delete mode 100644 audio/telephony-maemo5.c
delete mode 100644 audio/telephony-maemo6.c
delete mode 100644 audio/telephony-ofono.c
create mode 100644 audio/telephony.c
next reply other threads:[~2011-12-12 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 10:49 Frédéric Danis [this message]
2011-12-12 10:49 ` [RFC v4 1/6] audio: Move tel drivers to DBus interface Frédéric Danis
2011-12-12 10:49 ` [RFC v4 2/6] audio: Remove tel drivers Frédéric Danis
2011-12-12 10:49 ` [RFC v4 3/6] audio: Remove maemo5 tel driver Frédéric Danis
2011-12-12 10:49 ` [RFC v4 4/6] audio: Remove maemo6 " Frédéric Danis
2011-12-12 10:49 ` [RFC v4 5/6] audio: Move HFP/HSP AG servers to telephony.c Frédéric Danis
2011-12-12 10:49 ` [RFC v4 6/6] audio: Send transport path to telephony agent Frédéric Danis
2011-12-12 11:03 ` [RFC v4 0/6] Add org.bluez.Telephony interface Johan Hedberg
2011-12-12 21:24 ` Dmitriy Paliy
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=1323686954-11899-1-git-send-email-frederic.danis@linux.intel.com \
--to=frederic.danis@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;
as well as URLs for NNTP newsgroup(s).