From: "Frédéric Danis" <frederic.danis@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: [RFC v5 0/8] Add org.bluez.Telephony interface
Date: Wed, 14 Dec 2011 10:05:02 +0100 [thread overview]
Message-ID: <1323853510-5195-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).
This will simplify BlueZ code by focusing on Bluetooth communication
part and by letting external application (i.e. oFono) take in charge
the Telephony tasks (AT parsing and modem specific code, which can be
removed from BlueZ code). So, it becomes simpler, easier to maintain
and debug.
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.
Any comments appreciated.
Regards
Fred
Frédéric Danis (8):
audio: Move tel drivers to DBus interface
audio: Simplify org.bluez.Headset
audio: Remove dummy tel driver
audio: Remove maemo5 tel driver
audio: Remove maemo6 tel driver
audio: Remove oFono 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-14 9:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 9:05 Frédéric Danis [this message]
2011-12-14 9:05 ` [RFC v5 1/8] audio: Move tel drivers to DBus interface Frédéric Danis
2011-12-15 10:00 ` Luiz Augusto von Dentz
2011-12-15 11:04 ` Frederic Danis
2011-12-15 11:25 ` Luiz Augusto von Dentz
2011-12-16 8:41 ` Frederic Danis
2011-12-16 10:35 ` Luiz Augusto von Dentz
2011-12-16 15:00 ` Frederic Danis
2011-12-17 10:15 ` Luiz Augusto von Dentz
2011-12-27 10:09 ` Frederic Danis
2011-12-14 9:05 ` [RFC v5 2/8] audio: Simplify org.bluez.Headset Frédéric Danis
2011-12-14 9:05 ` [RFC v5 3/8] audio: Remove dummy tel driver Frédéric Danis
2011-12-14 9:05 ` [RFC v5 4/8] audio: Remove maemo5 " Frédéric Danis
2011-12-14 9:05 ` [RFC v5 5/8] audio: Remove maemo6 " Frédéric Danis
2011-12-14 9:05 ` [RFC v5 6/8] audio: Remove oFono " Frédéric Danis
2011-12-14 9:05 ` [RFC v5 7/8] audio: Move HFP/HSP AG servers to telephony.c Frédéric Danis
2011-12-14 9:05 ` [RFC v5 8/8] audio: Send transport path to telephony agent Frédéric Danis
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=1323853510-5195-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).