linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikel Astiz <mikel.astiz.oss@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Mikel Astiz <mikel.astiz.oss@gmail.com>
Subject: [PATCH BlueZ v1 0/5] Multiple Bluetooth SCO connections (userspace)
Date: Fri, 27 Apr 2012 12:59:42 +0200	[thread overview]
Message-ID: <1335524387-22831-1-git-send-email-mikel.astiz.oss@gmail.com> (raw)

This second version integrates the review from Luiz and drops patches v0 1 and 7. The first one is not needed due to recent Kernel changes (it's now possible to bind several SCO sockets to same address), and patch 7 needs further research (but is in practice needed for testing).

After these changes, it's possible to have two simultaneous SCO links. The question whether this should be enabled by default or not has not been addressed here.

>From previous cover letter:

This patch series includes patches that have been useful to connect two HCI-based SCO links simultaneously. This can be used for example to connect to HSP headsets at the same time.

The patch series is divided in three groups: kernel patches, BlueZ userspace patches and PulseAudio patches for module-bluetooth-device.

The kernel patches include some code cleanup and more importantly a dynamically changing alternate setting in btusb driver. These ideas have been taken from the patches I found in [1]. The last patch, “Bluetooth: Remove outgoing MTU check” should be considered with care, since there probably are better approaches to solve this (WIP).

The BlueZ userspace patches add some necessary infrastructure to support such use-cases.

The PulseAudio patches provide some changes to be able to test the rest of the code. The first three patches have been reused from a previously submitted patch series, and only the last two patches are relevant for this purpose. They provide some simple workarounds and should not be considered a proper solution.

As I said, the easiest may to test these patches is by using two Bluetooth headsets. You should use the Media API (Enable=Media in audio.conf), connect both headsets, and use pacmd to set their profile to hsp.

[1] http://bluetooth-alsa.sourceforge.net/future.html

Mikel Astiz (5):
  audio: Fix gateway state check
  audio: Add multiple device search to manager
  media: Support multiple transports per endpoint
  media: Create multiple transports if needed
  media: Enable parallel requests to endpoint

 audio/device.c  |    2 +-
 audio/manager.c |   25 +++++++-
 audio/manager.h |    6 ++
 audio/media.c   |  164 +++++++++++++++++++++++++++++++++++-------------------
 4 files changed, 135 insertions(+), 62 deletions(-)

-- 
1.7.7.6


             reply	other threads:[~2012-04-27 10:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 10:59 Mikel Astiz [this message]
2012-04-27 10:59 ` [PATCH BlueZ v1 1/5] audio: Fix gateway state check Mikel Astiz
2012-04-27 10:59 ` [PATCH BlueZ v1 2/5] audio: Add multiple device search to manager Mikel Astiz
2012-04-27 10:59 ` [PATCH BlueZ v1 3/5] media: Support multiple transports per endpoint Mikel Astiz
2012-04-27 10:59 ` [PATCH BlueZ v1 4/5] media: Create multiple transports if needed Mikel Astiz
2012-04-27 11:45   ` Luiz Augusto von Dentz
2012-04-27 10:59 ` [PATCH BlueZ v1 5/5] media: Enable parallel requests to endpoint Mikel Astiz

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=1335524387-22831-1-git-send-email-mikel.astiz.oss@gmail.com \
    --to=mikel.astiz.oss@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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).