linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Ron Shaffer <rshaffer@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/1] Bluetooth: Synchronize SCO/eSCO connection requests to ACL state
Date: Wed, 26 May 2010 10:59:16 +0200	[thread overview]
Message-ID: <1274864356.27220.155.camel@localhost.localdomain> (raw)
In-Reply-To: <4BFAEB65.2060503@codeaurora.org>

Hi Ron,

> Certain headsets such as the Motorola H350 will reject SCO and eSCO
> connection requests while the ACL is transitioning from sniff mode
> to active mode. Add synchronization so that SCO and eSCO connection
> requests will wait until the ACL has fully transitioned to active mode.

I am not completely happy with this patch. First please split it like
Gustavo asked since otherwise it becomes pretty hard to review. I don't
really bother to look into its technical nature before the split and the
coding style is in place.

Second, please don't make a special case for sniff mode. If we do this
then we also do it for park state and hold mode.

And third, I think this needs to be done a little bit more in the way we
handle attempts for connecting ACL links when the baseband is busy. So
can you send hcidump -X -V traces for the failure of SCO/eSCO setup when
sniff is active. I like to see which error codes are returned. Hacking
this directly into sniff exit handling makes the code pretty hard to
understand in the future.

Regards

Marcel



  parent reply	other threads:[~2010-05-26  8:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 21:11 [PATCH 1/1] Bluetooth: Synchronize SCO/eSCO connection requests to ACL state Ron Shaffer
2010-05-24 21:52 ` Gustavo F. Padovan
2010-05-25 17:00   ` Ron Shaffer
2010-05-25 20:09     ` Gustavo F. Padovan
2010-05-26  8:59 ` Marcel Holtmann [this message]
2010-05-26 14:30   ` Ron Shaffer
2010-05-26 15:31     ` Marcel Holtmann
2010-05-26 21:56       ` Ron Shaffer
2010-05-27  3:38         ` Perelet, Oleg
2010-05-27 10:34           ` Marcel Holtmann

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=1274864356.27220.155.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=rshaffer@codeaurora.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).