public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: lan zhu <zhu.lan.cn@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question on A2DP sink suspend/resume
Date: Thu, 25 Jun 2009 05:45:11 +0200	[thread overview]
Message-ID: <1245901511.15367.150.camel@violet> (raw)
In-Reply-To: <113d36d80906242033p134edf27t12bda1d0359c4134@mail.gmail.com>

Hi Zhu,

> If we want to create SCO link when A2DP is in streaming state, we
> shall suspend A2DP first and then establish SCO link. Conversely, we
> shall resume A2DP link when we drop SCO link. The entire description
> can be found in the Simultaneous use of HFP, A2DP, and AVRCP Profiles
> Whitepaper on bluetooth org web site.
> (https://www.bluetooth.org/Technical/Specifications/whitepapers.htm).
> 
> My question is,  I found there is no such sink_suspend or sink_resume
> method in D-BUS API while these functions are all implemented in Bluez
> audio module. I would like to know why don't put them to D-BUS API?
> If we need to call these functions we have to expand the D-BUS API.
> 
> One more question is, is there a formal way to test SCO/A2DP
> simultaneous case? we can't find a proper headset to test it because
> those headsets are all well implemented with the simultaneous logic,
> so there is no way to enter ourselves' code that handle this logic.
> Can we test it by configurating some test tool such as PTS?

seriously, wrong mailing list. Especially since A2DP is implemented
fully in userspace ;)

Post such questions to linux-bluetooth@vger.kernel.org please.

Regards

Marcel



      reply	other threads:[~2009-06-25  3:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25  3:33 question on A2DP sink suspend/resume lan zhu
2009-06-25  3:45 ` Marcel Holtmann [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=1245901511.15367.150.camel@violet \
    --to=marcel@holtmann.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhu.lan.cn@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox