linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Marcel Holtmann <marcel@holtmann.org>,
	Denis Kenzior <denkenz@gmail.com>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
	frederic.dalleau@linux.intel.com,
	Mikel Astiz <Mikel.Astiz@bmw-carit.de>
Cc: linux-bluetooth@vger.kernel.org, ofono@ofono.org,
	pulseaudio-discuss@lists.freedesktop.org
Subject: Bluetooth Audio Handling IRC Meeting
Date: Tue, 18 Oct 2011 16:33:01 +0200	[thread overview]
Message-ID: <4E9D8E1D.8050007@monom.org> (raw)

Hi Everyone,

[Sorry for cross posting but it might be interesting for someone on
these mailing lists]

I would like to invite to a IRC discussion on the HFP audio handling.

Topic is to find a solution for the handling/routing of the audio
streams (SCO link) in BlueZ, PulseAudio and oFono.

- Currently, it is not possible for PulseAudio or BlueZ to know what the
audio stream is carrying (*). This information is need for multi phone
uses cases. Think about two connected phones at the same time and both
are doing HFP.

- If there is need for policy decisions, is desirable to have this done
in one place only. With policy decision is meant deciding when to
suspend and resume a SCO link. Of course we would have to agree first,
if this should be done in placed into one component only.

- For the two phone use cases I also like to discuss how to report the
'content' (*) of the audio links, so the above policies can be
implemented. oFono doesn't export this information and I assume we
really don't want to have a dependency on PulseAudio from oFono.

(*) in band ringing, active call, held call, etc.

irc server: freenode.net
irc channel: #bop_audio
date: 20.10.2011 (10/20/11 for the americans)
time: 16:00 CEST (07:00 PDT, 09:00 CDT, 17:00 EEST)
duration: < 1 hour (hopefully)

If the date/time is really bad for you (sorry Marcel), please let me
know. Johan told me he could also attend it if we start one hour later.

cheers,
daniel

                 reply	other threads:[~2011-10-18 14:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4E9D8E1D.8050007@monom.org \
    --to=wagi@monom.org \
    --cc=Mikel.Astiz@bmw-carit.de \
    --cc=denkenz@gmail.com \
    --cc=frederic.dalleau@linux.intel.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=ofono@ofono.org \
    --cc=pulseaudio-discuss@lists.freedesktop.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).