From: "Frédéric Danis" <frederic.danis@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 0/4] Add new dbus telephony driver
Date: Thu, 20 Oct 2011 15:52:14 +0200 [thread overview]
Message-ID: <1319118738-20131-1-git-send-email-frederic.danis@linux.intel.com> (raw)
This patch add a new telephony driver allowing HSP/HFP to be managed
through an external DBus agent.
BlueZ takes care of SDP and RFComm parts while the upper layer is
processed by the agent.
Current AT parser and dbus code which are only needed by current
drivers (built-in drivers) are move to telephony-builtin.[ch].
Frédéric Danis (4):
Audio: move at parsing code to telephony-builtin.[ch] files
Audio: move dbus callbacks to telephony-builtin.c
Audio: add adapter to telephony_init/_exit
Audio: add dbus telephony driver
Makefile.am | 9 +-
acinclude.m4 | 1 +
audio/headset.c | 1485 +++----------------------------------------
audio/headset.h | 4 +
audio/manager.c | 4 +-
audio/telephony-builtin.c | 1570 +++++++++++++++++++++++++++++++++++++++++++++
audio/telephony-builtin.h | 218 +++++++
audio/telephony-dbus.c | 554 ++++++++++++++++
audio/telephony-dummy.c | 5 +-
audio/telephony-maemo5.c | 5 +-
audio/telephony-maemo6.c | 5 +-
audio/telephony-ofono.c | 5 +-
audio/telephony.h | 225 +------
doc/audio-api.txt | 99 +++
14 files changed, 2590 insertions(+), 1599 deletions(-)
create mode 100644 audio/telephony-builtin.c
create mode 100644 audio/telephony-builtin.h
create mode 100644 audio/telephony-dbus.c
next reply other threads:[~2011-10-20 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 13:52 Frédéric Danis [this message]
2011-10-20 13:52 ` [PATCH 1/4] Audio: move at parsing code to telephony-builtin.[ch] files Frédéric Danis
2011-10-20 13:52 ` [PATCH 2/4] Audio: move dbus callbacks to telephony-builtin.c Frédéric Danis
2011-10-20 13:52 ` [PATCH 3/4] Audio: add adapter to telephony_init/_exit Frédéric Danis
2011-10-20 13:52 ` [PATCH 4/4] Audio: add dbus telephony driver 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=1319118738-20131-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).