From: Christos Longros <chris.longros@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Christos Longros <chris.longros@gmail.com>
Subject: [PATCH] Bluetooth: btusb: add Realtek RTL8852CE device ID 0x0852
Date: Sun, 29 Mar 2026 10:13:24 +0200 [thread overview]
Message-ID: <20260329081324.123156-1-chris.longros@gmail.com> (raw)
Add the native Realtek vendor device ID (0bda:0852) for the RTL8852CE
Bluetooth radio to the btusb device table.
Without this entry the device is matched only by the generic Bluetooth
class rule (USB_INTERFACE_INFO 0xe0/0x01/0x01), which means btusb
binds but without the BTUSB_REALTEK flag. This skips Realtek-specific
firmware loading, event handling, and wideband speech support.
Tested on a Gigabyte B650 Gaming X AX V2 with the onboard RTL8852CE
combo WiFi/BT card (USB ID 0bda:0852).
Signed-off-by: Christos Longros <chris.longros@gmail.com>
---
drivers/bluetooth/btusb.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 5c535f3ab..0bc77b29b 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -549,6 +549,8 @@ static const struct usb_device_id quirks_table[] = {
BTUSB_WIDEBAND_SPEECH },
/* Realtek 8852CE Bluetooth devices */
+ { USB_DEVICE(0x0bda, 0x0852), .driver_info = BTUSB_REALTEK |
+ BTUSB_WIDEBAND_SPEECH },
{ USB_DEVICE(0x04ca, 0x4007), .driver_info = BTUSB_REALTEK |
BTUSB_WIDEBAND_SPEECH },
{ USB_DEVICE(0x04c5, 0x1675), .driver_info = BTUSB_REALTEK |
--
2.53.0
next reply other threads:[~2026-03-29 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 8:13 Christos Longros [this message]
2026-03-29 8:55 ` Bluetooth: btusb: add Realtek RTL8852CE device ID 0x0852 bluez.test.bot
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=20260329081324.123156-1-chris.longros@gmail.com \
--to=chris.longros@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--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