* [PATCH] Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks
@ 2026-09-30 18:11 Konstantin Nazarov
2026-09-30 18:44 ` bluez.test.bot
2026-09-30 19:18 ` [PATCH] " Konstantin Nazarov
0 siblings, 2 replies; 3+ messages in thread
From: Konstantin Nazarov @ 2026-09-30 18:11 UTC (permalink / raw)
To: marcel, luiz.dentz; +Cc: linux-bluetooth, linux-kernel, Konstantin Nazarov
The Bluetooth controller with USB ID 0b05:1825 found on ASUS
systems uses a Qualcomm QCA Rome chipset, but is currently matched
only by the generic Bluetooth USB entry.
Without BTUSB_QCA_ROME, the driver does not load the QCA rampatch and
NVM firmware. BLE scanning also repeatedly reports:
Bluetooth: hci0: unexpected event for opcode 0x2005
Mark the device as BTUSB_QCA_ROME with wideband speech support, in
line with the other QCA Rome USB IDs.
Same issue as https://github.com/bluez/bluetooth-next/pull/833 but
with different device id. After patching bluetooth is working fine,
no unexpected events in log.
Tested on: Qualcomm Atheros QCA6174 SoC integrated in motherboard
ASUS Z170I PRO GAMING, USB device id: 0b05:1825
Signed-off-by: Konstantin Nazarov <qwertyuiopyyy@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 dc7191bf4..66e12b15e 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -270,6 +270,8 @@ static const struct usb_device_id quirks_table[] = {
{ USB_DEVICE(0x0489, 0xe03c), .driver_info = BTUSB_ATH3012 },
/* QCA ROME chipset */
+ { USB_DEVICE(0x0b05, 0x1825), .driver_info = BTUSB_QCA_ROME |
+ BTUSB_WIDEBAND_SPEECH },
{ USB_DEVICE(0x0cf3, 0x535b), .driver_info = BTUSB_QCA_ROME |
BTUSB_WIDEBAND_SPEECH },
{ USB_DEVICE(0x0cf3, 0xe007), .driver_info = BTUSB_QCA_ROME |
--
2.43.0
^ permalink raw reply related [flat|nested] 3+ messages in thread* RE: Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks
2026-09-30 18:11 [PATCH] Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks Konstantin Nazarov
@ 2026-09-30 18:44 ` bluez.test.bot
2026-09-30 19:18 ` [PATCH] " Konstantin Nazarov
1 sibling, 0 replies; 3+ messages in thread
From: bluez.test.bot @ 2026-09-30 18:44 UTC (permalink / raw)
To: linux-bluetooth, qwertyuiopyyy
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
This is an automated email and please do not reply to this email.
Dear Submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
While preparing the CI tests, the patches you submitted couldn't be applied to the current HEAD of the repository.
----- Output -----
error: drivers/bluetooth/btusb.c: does not exist in index
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Please resolve the issue and submit the patches again.
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks
2026-09-30 18:11 [PATCH] Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks Konstantin Nazarov
2026-09-30 18:44 ` bluez.test.bot
@ 2026-09-30 19:18 ` Konstantin Nazarov
1 sibling, 0 replies; 3+ messages in thread
From: Konstantin Nazarov @ 2026-09-30 19:18 UTC (permalink / raw)
To: marcel, luiz.dentz; +Cc: linux-bluetooth, linux-kernel
Please ignore this patch, it was based on the wrong tree.
I will send v2 shortly.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-09-30 19:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-09-30 18:11 [PATCH] Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks Konstantin Nazarov
2026-09-30 18:44 ` bluez.test.bot
2026-09-30 19:18 ` [PATCH] " Konstantin Nazarov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox