From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 211013] Cannot find ath3k bluetooth controller attached on USB
Date: Sun, 03 Jan 2021 08:21:50 +0000 [thread overview]
Message-ID: <bug-211013-62941-IFEafVVRDP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211013-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211013
--- Comment #1 from Tianhao Chai (cth451@gmail.com) ---
Apparently this ver_rom 0x11020000 has never been recorded in
qca_devices_table[] defined in btusb.c.
Before 5.10 (i.e. 5.9.x and possibly earlier), the function btusb_setup_qca()
will short circuit and return 0 before querying the device table (the following
from 5.9.16, btusb.c:3627):
ver_rom = le32_to_cpu(ver.rom_version);
/* Don't care about high ROM versions */
if (ver_rom & ~0xffffU)
return 0;
Since this check is removed in 5.10.x due to added support of WCN6855 (which
has a high ROM version), the driver would return -ENODEV as this 0x11020000
doesn't exist in qca_devices_table in the first place.
I am not sure how this should be resolved. We could check whether ver_rom ==
0x11020000 and directly return 0 (and the card would work after that), but I
think this is a very dirty approach.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-01-03 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 5:34 [Bug 211013] New: Cannot find ath3k bluetooth controller attached on USB bugzilla-daemon
2021-01-03 8:21 ` bugzilla-daemon [this message]
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=bug-211013-62941-IFEafVVRDP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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