public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "Zhang, Zhenhua" <zhenhua.zhang@intel.com>
Cc: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"Gustavo F. Padovan" <gustavo@las.ic.unicamp.br>
Subject: Re: [PATCH] oFonoHFP profile to enable audio routing in BlueZ
Date: Fri, 13 Nov 2009 10:36:15 -0300	[thread overview]
Message-ID: <2d5a2c100911130536p27acb9b1ob4b566e43afef321@mail.gmail.com> (raw)
In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E089CD174BB@pdsmsx502.ccr.corp.intel.com>

Hi,

2009/11/12 Zhang, Zhenhua <zhenhua.zhang@intel.com>:
> Hi,
>
> Ops, forgot to add ofono-hfp.c into BlueZ patch. So I add them and
> resend 0001 patch.
>
> linux-bluetooth-owner@vger.kernel.org wrote:
>> Hi,
>>
>> These three patches are created to enable audio routing for Handsfree
>> Profile. It was created during the voicecall driver implementation in
>> oFono so it does not use the new hfp-api yet. You can take it
>> as reference only since it will not be commited into trunk.
>>
>> Basically, a new profile oFonoHFP was added to create RFCOMM
>> connection and turn IO into TTY device for oFono. It sends TTY
>> device string to oFono through D-Bus. Meanwhile, it listens
>> oFono property changes to emit CallStarted and CallEnded
>> signals. PulseAudio could listen these signals and redirect
>> audio source/sink to use bluetooth one.
>>
>> If you are interested at it, you may apply 0001..0003 into
>> BlueZ, oFono and PA respectively. Last commit SHA-1 is in patch note.
>>
>> And you need to enable oFonoHFP by modify audio.conf:         Disable=Gateway
>>       Enable=oFonoHFP, Headset
>>
>> In ofono modem.conf, specify device address like:
>>       [hfp]
>>       Driver=hfp
>>       Address=00:22:A9:8C:AF:34
>>
>> And power on modem by:
>>       dbus-send --system --print-reply --dest=org.ofono /hfp0
>> org.ofono.Modem.SetProperty string:Powered variant:boolean:true
>>
>> The PulseAudio will load module-bluetooth-discover
>> automatically. If not, please load it manually. This module
>> listens BlueZ signal and load module-bluetooth-device
>> automatically. Unfortunately, you need to load module-loopback
>> manually to redirect bluez source/sink to alsa, e.g.:
>>       load-module module-loopback source="bluez_source.XX..XX"
>> sink="alsa_output.0.analog-stereo"
>>       load-module module-loopback source="alsa_input.0.analog-stereo"
>> sink="bluez_sink.XX..XX"
>>
>> Feel free to let me know if any problems. Thanks.

What happened with the original idea from Denis, I don't think
oFonoHFP is a good name to start with and it should be a generic
interface where any telephony agent could register.


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

  reply	other threads:[~2009-11-13 13:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  7:50 [PATCH] oFonoHFP profile to enable audio routing in BlueZ Zhang, Zhenhua
2009-11-12 16:48 ` Gustavo F. Padovan
2009-11-13  1:01 ` Zhang, Zhenhua
2009-11-13 13:36   ` Luiz Augusto von Dentz [this message]
2009-11-13 13:54     ` Gustavo F. Padovan

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=2d5a2c100911130536p27acb9b1ob4b566e43afef321@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=gustavo@las.ic.unicamp.br \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zhenhua.zhang@intel.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