All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Danis <frederic.danis@linux.intel.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC v6 1/8] audio: Move tel drivers to DBus interface
Date: Thu, 29 Dec 2011 10:38:18 +0100	[thread overview]
Message-ID: <4EFC350A.5000404@linux.intel.com> (raw)
In-Reply-To: <CABBYNZJGakUpv=vbq47h7qxaCNV5p808Jq5YYj7TxwmbBH6oEA@mail.gmail.com>

Hello Luiz,

Le 29/12/2011 09:49, Luiz Augusto von Dentz a écrit :
>> +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 DBus
>> +                       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:
>> +
>> +                               strict Device:
>> +
>> +                                       BlueZ remote device object.
>> +
>> +                               string UUID:
>> +
>> +                                       Profile UUID of the connection.
>> +
>> +                               uint16 Version:
>> +
>> +                                       Remote profile version.
>> +
>> +                               uint16 Features:
>> +
>> +                                       Remote profile features.
>> +
>> +                               string MediaTransportPath:
>> +
>> +                                       Optional. MediaTransport object path.
>
> This should be an object not a string and IMO it should be called
> Transport just to keep it sort.

OK

Fred

-- 
Frederic Danis                            Open Source Technology Center
frederic.danis@intel.com                              Intel Corporation


  reply	other threads:[~2011-12-29  9:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 13:48 [RFC v6 0/8] Add org.bluez.Telephony interface Frédéric Danis
2011-12-28 13:48 ` [RFC v6 1/8] audio: Move tel drivers to DBus interface Frédéric Danis
2011-12-29  8:49   ` Luiz Augusto von Dentz
2011-12-29  9:38     ` Frederic Danis [this message]
2011-12-28 13:48 ` [RFC v6 2/8] audio: Simplify org.bluez.Headset Frédéric Danis
2011-12-28 13:48 ` [RFC v6 3/8] audio: Remove dummy tel driver Frédéric Danis
2011-12-28 13:48 ` [RFC v6 4/8] audio: Remove maemo5 " Frédéric Danis
2011-12-28 13:48 ` [RFC v6 5/8] audio: Remove maemo6 " Frédéric Danis
2011-12-28 13:48 ` [RFC v6 6/8] audio: Remove oFono " Frédéric Danis
2011-12-28 13:48 ` [RFC v6 7/8] audio: Move HFP/HSP AG servers to telephony.c Frédéric Danis
2011-12-28 13:48 ` [RFC v6 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=4EFC350A.5000404@linux.intel.com \
    --to=frederic.danis@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.