From: Takashi Iwai <tiwai@suse.de>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Atheros 1525/QCA6174 BT issue
Date: Thu, 08 Mar 2018 09:27:50 +0100 [thread overview]
Message-ID: <s5hd10fkm49.wl-tiwai@suse.de> (raw)
Hi,
we've got a but report about the broken Atheros BT on the recent
kernels:
http://bugzilla.opensuse.org/show_bug.cgi?id=1082504
In short, btusb can't load the patch ar3k/AthrBT_0x00000200.dfu, and
this could be worked around by the patch to move 0cf3:3004 blacklist
entry to use BTUSB_QCA_ROM instead of BTUSB_ATH3012.
And this looks like a long-standing problem, at least for over two
years. Many web pages suggest the same patch, but it's never merged
to upstream.
So this made me wonder what's going on. I see that the BTUSB_ATH3012
quirk was originally introduced just for this chip id (0cf3:3004).
Is it a different variant from the original chip that causes a
problem?
I'm happy to get any fix patch and can provide a test kernel to the
reporter.
FWIW, the device looks like:
T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=03 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0cf3 ProdID=3004 Rev= 0.01
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
And the lsusb output:
Bus 001 Device 004: ID 0cf3:3004 Qualcomm Atheros Communications AR3012
Bluetooth 4.0
thanks,
Takashi
next reply other threads:[~2018-03-08 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 8:27 Takashi Iwai [this message]
2018-03-08 9:06 ` Atheros 1525/QCA6174 BT issue Marcel Holtmann
2018-03-08 9:16 ` Takashi Iwai
2018-03-13 8:05 ` Takashi Iwai
2018-03-13 8:10 ` Marcel Holtmann
2018-03-13 8:32 ` Takashi Iwai
2018-03-13 8:38 ` Marcel Holtmann
2018-03-13 8:50 ` Takashi Iwai
2018-03-13 9:15 ` Marcel Holtmann
2018-03-15 15:56 ` Takashi Iwai
2018-03-15 18:32 ` 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=s5hd10fkm49.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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