linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "João Paulo Rechi Vita" <jprvita@gmail.com>
Cc: pulseaudio-discuss@mail.0pointer.de,
	Gustavo Padovan <padovan@profusion.mobi>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Zheng Huan <huan.zheng@intel.com>,
	Lennart Poettering <lennart@poettering.net>,
	ofono@ofono.org, linux-bluetooth@vger.kernel.org
Subject: Re: [RFC] [PATCH 0/2] HFP AG integration with PulseAudio
Date: Tue, 2 Feb 2010 09:03:57 -0800	[thread overview]
Message-ID: <2d5a2c101002020903p19f78ddbxef5aaf6bb6096433@mail.gmail.com> (raw)
In-Reply-To: <1264776266-7646-1-git-send-email-jprvita@gmail.com>

Hi,

2010/1/29 João Paulo Rechi Vita <jprvita@gmail.com>:
> Hi all,
>
> I'm trying to add support for the Handsfree Gateway role Gustavo just added
> to BlueZ and oFono. The BlueZ patches can be found on [1] and [2] and the
> oFono part was just merged upstream.
>
> But when it comes to integrate them with Pulse, I'm getting a POLLHUP when
> trying to write on the fd. Also, it seems different gateways have different
> behaviours regarding when they connect the SCO link. Some phone connect
> them just after the RFCOMM link (some Nokia phones), when there is no call
> going on yet, and others just when a call is started (Android 1.5).
>
> Also, right now the same property (State) is beeing used to refer when the
> RFCOOM link is established (State=Connected) and when the SCO link is
> established (State=Playing). Shouldn't this be handled by separate props?
>
> And last but not least, is the new Media API intended to handle the audio
> part of handsfree gateways too? If so, maybe we should use all this work
> as a prototype for latter integration with the new API.

Yep, Media API is supposed to handle this, that why I asked them to be
though in an integrated manner maybe being registered in the same
interface (although hfp is not really media only), anyway basically we
should have pa acting as a2dp source/sink and/or hfp gateway/headset
endpoint handling the audio. So in essence ofono is acting as a
controller/target in a very similar way as avrcp does for a2dp,
although for avrcp we don't really need an agent as we use uinput.

> Any help on testing and getting this working together or comments on the
> topic would be appreciated.

There is already some code in my git tree:
http://gitorious.org/~vudentz/bluez/vudentzs-clone/commits/for-upstream

-- 
Luiz Augusto von Dentz
Engenheiro de Computação

      parent reply	other threads:[~2010-02-02 17:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29 14:44 [RFC] [PATCH 0/2] HFP AG integration with PulseAudio João Paulo Rechi Vita
2010-01-29 14:44 ` [PATCH 1/2] bluetooth: improve dbus logging a little bit João Paulo Rechi Vita
2010-01-29 14:44   ` [PATCH 2/2] bluetooth: add HFP Gateway support João Paulo Rechi Vita
2010-01-29 14:53 ` [RFC] [PATCH 0/2] HFP AG integration with PulseAudio João Paulo Rechi Vita
     [not found]   ` <20100202111019.GA27346@tango.0pointer.de>
2010-02-03 18:38     ` [pulseaudio-discuss] " João Paulo Rechi Vita
2010-02-01 17:09 ` João Paulo Rechi Vita
2010-02-02  1:38   ` Zhenhua Zhang
2010-02-02  3:50   ` Zhenhua Zhang
2010-02-03 18:30     ` João Paulo Rechi Vita
2010-02-04  3:21       ` Zhenhua Zhang
2010-02-02 17:03 ` Luiz Augusto von Dentz [this message]

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=2d5a2c101002020903p19f78ddbxef5aaf6bb6096433@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=huan.zheng@intel.com \
    --cc=johan.hedberg@gmail.com \
    --cc=jprvita@gmail.com \
    --cc=lennart@poettering.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ofono@ofono.org \
    --cc=padovan@profusion.mobi \
    --cc=pulseaudio-discuss@mail.0pointer.de \
    /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).