From: Ron Shaffer <rshaffer@codeaurora.org>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 0/1] Bluetooth: Synchronize SCO/eSCO connection requests to ACL state
Date: Mon, 24 May 2010 16:10:52 -0500 [thread overview]
Message-ID: <4BFAEB5C.4040300@codeaurora.org> (raw)
Marcel:
This patch resolves some issues with what looks to be certain CSR
based headsets. When requesting SCO or eSCO while the connection
is transitioning from sniff to active, i.e. unsniff has been requested
but the headset has not responded with accepted, these headsets seem
to enter a state where they don't positively respond the SCO/eSCO
request. This was first noticed in and Motorola H350 Headset.
In addition, I've cleaned up some extraneous spaces and the original
Copyright has been changed from Qualcomm to Code Aurora Forum as
Qualcomm has reassigned these rights to Code Aurora Forum.
--
Ron Shaffer
Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next reply other threads:[~2010-05-24 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 21:10 Ron Shaffer [this message]
2010-05-24 21:19 ` [PATCH 0/1] Bluetooth: Synchronize SCO/eSCO connection requests to ACL state 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=4BFAEB5C.4040300@codeaurora.org \
--to=rshaffer@codeaurora.org \
--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).