From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220815] btusb: Add Realtek RTL8852CE device ID (13d3:3612)
Date: Sun, 30 Nov 2025 12:41:42 +0000 [thread overview]
Message-ID: <bug-220815-62941-BVQ8yJ0VRk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220815-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220815
Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmenzel+bugzilla.kernel.org
| |@molgen.mpg.de
--- Comment #1 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
Created attachment 308985
--> https://bugzilla.kernel.org/attachment.cgi?id=308985&action=edit
[PATCH] Bluetooth: btusb: Add 13d3:3612 for Realtek RTL8852CE
Thank you for the report, and providing the solution. I cooked up a patch and
attached it. It also adds the flags `BTUSB_WIDEBAND_SPEECH` as all the other
devices have.
It’s common practice to add the device info from
`/sys/kernel/debug/usb/devices` to the commit message. It’d be great, if you
could provide that, so I can send in the patch.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2025-11-30 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-30 6:58 [Bug 220815] New: btusb: Add Realtek RTL8852CE device ID (13d3:3612) bugzilla-daemon
2025-11-30 12:41 ` bugzilla-daemon [this message]
2025-11-30 23:44 ` [Bug 220815] " bugzilla-daemon
2025-12-06 14:17 ` bugzilla-daemon
2025-12-07 20:06 ` bugzilla-daemon
2026-02-14 23:42 ` bugzilla-daemon
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-220815-62941-BVQ8yJ0VRk@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