From: Frederic Danis <frederic.danis@linux.intel.com>
To: Mikel Astiz <mikel.astiz.oss@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v15 01/14] doc: Add telephony interface documents
Date: Fri, 27 Jul 2012 10:30:45 +0200 [thread overview]
Message-ID: <501251B5.1060101@linux.intel.com> (raw)
In-Reply-To: <CANT-zCVCXCSha3CTC2BL9TA9564RQyB8x86QGoOrUuo6OBKU3g@mail.gmail.com>
Hello Mikel,
On 27/07/2012 09:52, Mikel Astiz wrote:
>> +TelephonyAgent hierarchy
>> +========================
>> +
>> +Service unique name
>> +Interface org.bluez.TelephonyAgent
>> +Object path freely definable
>> +
>> +Methods void NewConnection(filedescriptor fd, dict properties)
>> +
>> + This method gets called whenever a new connection
>> + has been established. This method assumes that D-Bus
>> + daemon with file descriptor passing capability is
>> + being used.
>> +
>> + The agent should only return successfully once the
>> + establishment of the service level connection (SLC)
>> + has been completed. In the case of Handsfree this
>> + means that BRSF exchange has been performed and
>> + necessary initialization has been done.
>> +
>> + possible properties:
>> +
>> + object Device:
>> +
>> + BlueZ remote device object.
>> +
>> + string UUID:
>> +
>> + Profile UUID of the connection.
>
> What would be the purpose of this property?
>
> I believe the agent was already registered for a specific UUID, so
> this seems redundant.
>
You're right, even if agent registers for multiple profiles, the object
path should be unique for a specific UUID.
I will remove it.
Regards
Fred
--
Frederic Danis Open Source Technology Center
frederic.danis@intel.com Intel Corporation
next prev parent reply other threads:[~2012-07-27 8:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 8:45 [PATCH v15 00/14] Add org.bluez.Telephony interface Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 01/14] doc: Add telephony interface documents Frédéric Danis
2012-07-27 7:52 ` Mikel Astiz
2012-07-27 8:30 ` Frederic Danis [this message]
2012-07-26 8:45 ` [PATCH v15 02/14] audio: Move telephony drivers to D-Bus interface Frédéric Danis
2012-07-27 8:25 ` Mikel Astiz
2012-07-27 9:33 ` Frederic Danis
2012-07-30 7:58 ` Johan Hedberg
2012-07-26 8:45 ` [PATCH v15 03/14] audio: Simplify org.bluez.Headset Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 04/14] audio: Remove dummy telephony driver Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 05/14] audio: Remove maemo5 " Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 06/14] audio: Remove maemo6 " Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 07/14] audio: Remove oFono " Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 08/14] audio: Move HFP/HSP AG servers to telephony.c Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 09/14] audio: Send transport path to telephony agent Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 10/14] audio: Move HFP HF server to telephony.c Frédéric Danis
2012-07-27 8:50 ` Mikel Astiz
2012-07-27 12:44 ` Frederic Danis
2012-07-26 8:45 ` [PATCH v15 11/14] audio: Add DUN GW to org.bluez.Telephony Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 12/14] audio: Add SAP " Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 13/14] adapter: Add API to get fast connectable mode Frédéric Danis
2012-07-26 8:45 ` [PATCH v15 14/14] audio: Add fast connectable to telephony interface 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=501251B5.1060101@linux.intel.com \
--to=frederic.danis@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikel.astiz.oss@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).