From: Marcel Holtmann <marcel@holtmann.org>
To: Andrew Earl <andrewx.earl@intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] bluetooth: Fix aborting eSCO connection in case of error 0x20
Date: Fri, 7 Mar 2014 09:53:50 -0800 [thread overview]
Message-ID: <AF985C9B-3C8D-40BD-96F2-42EF32F28EF6@holtmann.org> (raw)
In-Reply-To: <1394199005-28369-1-git-send-email-andrewx.earl@intel.com>
Hi Andre,
> Add additional error case to attempt alternative configuration for SCO. Error
> occurs with Intel BT controller where fallback is not attempted as the error
> 0x020 Unsupported LMP Parameter value is not included in the list of errors
status is only 1 octet and not 1.5 octets ;)
> where a retry should be attempted.
> The problem also affects PTS test case TC_HF_ACS_BV_05_I.
>
> See the HCI log below for details:
> < HCI Command: Setup Synchronous Connection (0x01|0x0028) plen 17
> handle 256 voice setting 0x0060 ptype 0x0380
>> HCI Event: Command Status (0x0f) plen 4
> Setup Synchronous Connection (0x01|0x0028) status 0x00 ncmd 1
>> HCI Event: Max Slots Change (0x1b) plen 3
> handle 256 slots 1
>> HCI Event: Synchronous Connect Complete (0x2c) plen 17
> status 0x20 handle 0 bdaddr 00:80:98:09:0B:19 type eSCO
> Error: Unsupported LMP Parameter Value
> < HCI Command: Setup Synchronous Connection (0x01|0x0028) plen 17
> handle 256 voice setting 0x0060 ptype 0x0380
>> HCI Event: Command Status (0x0f) plen 4
> Setup Synchronous Connection (0x01|0x0028) status 0x00 ncmd 1
>> HCI Event: Max Slots Change (0x1b) plen 3
> handle 256 slots 5
>> HCI Event: Synchronous Connect Complete (0x2c) plen 17
> status 0x20 handle 0 bdaddr 00:80:98:09:0B:19 type eSCO
> Error: Unsupported LMP Parameter Value
> < HCI Command: Setup Synchronous Connection (0x01|0x0028) plen 17
> handle 256 voice setting 0x0060 ptype 0x03c8
>> HCI Event: Command Status (0x0f) plen 4
> Setup Synchronous Connection (0x01|0x0028) status 0x00 ncmd 1
>> HCI Event: Max Slots Change (0x1b) plen 3
> handle 256 slots 1
>> HCI Event: Synchronous Connect Complete (0x2c) plen 17
> status 0x00 handle 257 bdaddr 00:80:98:09:0B:19 type eSCO
> Air mode: CVSD
You need to sign off your patches. Do you mind actually including the btmon trace since that is a bit more verbose.
> ---
> net/bluetooth/hci_event.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> index 5f81245..59e1b45 100644
> --- a/net/bluetooth/hci_event.c
> +++ b/net/bluetooth/hci_event.c
> @@ -2905,6 +2905,7 @@ static void hci_sync_conn_complete_evt(struct hci_dev *hdev,
> case 0x1c: /* SCO interval rejected */
> case 0x1a: /* Unsupported Remote Feature */
> case 0x1f: /* Unspecified error */
> + case 0x20: /* Unsupported LMP Parameter value */
> if (conn->out) {
> conn->pkt_type = (hdev->esco_type & SCO_ESCO_MASK) |
> (hdev->esco_type & EDR_ESCO_MASK);
Regards
Marcel
next prev parent reply other threads:[~2014-03-07 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 13:30 [PATCH] bluetooth: Fix aborting eSCO connection in case of error 0x20 Andrew Earl
2014-03-07 17:53 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-10 10:31 Andrew Earl
2014-03-10 10:31 ` Andrew Earl
2014-03-11 15:17 ` 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=AF985C9B-3C8D-40BD-96F2-42EF32F28EF6@holtmann.org \
--to=marcel@holtmann.org \
--cc=andrewx.earl@intel.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