From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216764] New: WCN6855 bluetooth USB completely unable to detect on some devices
Date: Fri, 02 Dec 2022 06:15:59 +0000 [thread overview]
Message-ID: <bug-216764-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216764
Bug ID: 216764
Summary: WCN6855 bluetooth USB completely unable to detect on
some devices
Product: Drivers
Version: 2.5
Kernel Version: 5.10.115;6.0.1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: wiagn233@outlook.com
Regression: No
I'm using a QCNFA765(WCN6855) wlan+bt combo card on my arm SBCs. However some
devices completely unable to detect its Bluetooth USB device. I've tested it on
radxa's Rock 3A and Rock 5B and beaglebone ai-64. USB only detected on Rock 3a
at any kernel version(both downstream and upstream kernel detects). Other two
devices cannot detect it at all. lsusb doesn't report anything about this card,
dmesg reports no warning/error about usb.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2022-12-02 6:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-216764-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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