From: Hui Wang <hui.wang@canonical.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Tedd An <tedd.an@intel.com>,
Johan Hedberg <johan.hedberg@intel.com>,
xiong.y.zhang@intel.com,
"Gustavo F. Padovan" <gustavo.padovan@collabora.co.uk>,
"linux-bluetooth@vger.kernel.org development"
<linux-bluetooth@vger.kernel.org>,
Kun Yang <kun.yang@canonical.com>,
Anthony Wong <anthony.wong@canonical.com>
Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus
Date: Mon, 04 Nov 2013 13:59:35 +0800 [thread overview]
Message-ID: <527737C7.40208@canonical.com> (raw)
In-Reply-To: <9DFD9618-158E-41C4-8183-134A3FC4E61F@holtmann.org>
On 11/03/2013 03:05 AM, Marcel Holtmann wrote:
> Hi Hui,
>
<snip>
>>
>> The attachment lenovo-k4450-btmon-v1.log is the log of intel 7260 init procedure + scan headset + connect headset + play sound.
> I looked through the logs and the controller init is just fine. So in theory this should route the SCO audio frames over HCI. For some reason it does not and I have no idea why not.
>
> That it makes a different between EHCI and XHCI is strange. I can not explain this. Maybe Tedd can help you since I have no further insights in our chips at this moment.
Thanks Marcel for your kind help and analysis.
Tedd, did you reproduce this issue on the machines with intel 7260 BT
module connected to the EHCI bus? Did you have any idea on this issue?
Thanks,
Hui.
>
> Regards
>
> Marcel
>
>
next prev parent reply other threads:[~2013-11-04 5:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 10:03 Intel 7260 bluetooth malfunction when it is connected to EHCI bus Hui Wang
2013-10-29 11:16 ` Marcel Holtmann
2013-10-30 2:51 ` Hui Wang
2013-10-30 19:36 ` Tedd Ho-Jeong An
2013-10-31 5:15 ` Hui Wang
2013-10-30 19:44 ` Marcel Holtmann
2013-10-31 5:29 ` Hui Wang
2013-10-31 9:49 ` Marcel Holtmann
2013-11-01 2:39 ` Hui Wang
2013-11-01 7:49 ` Marcel Holtmann
2013-11-01 9:18 ` Hui Wang
2013-11-02 19:05 ` Marcel Holtmann
2013-11-04 5:59 ` Hui Wang [this message]
2013-11-04 13:15 ` Stevie Trujillo
2013-11-05 2:32 ` Hui Wang
2013-11-05 18:44 ` Stevie Trujillo
2013-11-07 3:45 ` Hui Wang
2013-11-07 10:07 ` Stevie Trujillo
2013-11-08 1:43 ` Hui Wang
2013-11-08 11:17 ` Michal Labedzki
2013-11-26 9:11 ` Michal Labedzki
2013-12-20 12:30 ` Stevie Trujillo
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=527737C7.40208@canonical.com \
--to=hui.wang@canonical.com \
--cc=anthony.wong@canonical.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=johan.hedberg@intel.com \
--cc=kun.yang@canonical.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=tedd.an@intel.com \
--cc=xiong.y.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.