* [PATCH] Bluetooth: btmtk: Route firmware debug event to the diag channel
@ 2026-08-26 11:16 Chris Lu
2026-08-26 11:55 ` bluez.test.bot
0 siblings, 1 reply; 2+ messages in thread
From: Chris Lu @ 2026-08-26 11:16 UTC (permalink / raw)
To: Marcel Holtmann, Johan Hedberg, Luiz Von Dentz
Cc: Sean Wang, Will Lee, SS Wu, linux-bluetooth, linux-kernel,
linux-mediatek, Chris Lu
MediaTek controllers may emit a firmware debug event on the ACL channel
using the reserved handle 0x0efd, which shows up in the ACL header as
0x2efd once the start fragment flag is included.
Neither btmtk_usb_recv_acl() nor btmtksdio_recv_acl() recognizes it, so
the packet is passed to the HCI core, which has no connection with that
handle and complains:
Bluetooth: hci0: ACL packet for unknown connection handle 3837
Handle it the same way as the existing firmware debug logging packets and
forward it to the diagnostic channel instead.
Signed-off-by: Chris Lu <chris.lu@mediatek.com>
---
drivers/bluetooth/btmtk.c | 1 +
drivers/bluetooth/btmtksdio.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/bluetooth/btmtk.c b/drivers/bluetooth/btmtk.c
index 73ba4a029e9c..8563ab06a99f 100644
--- a/drivers/bluetooth/btmtk.c
+++ b/drivers/bluetooth/btmtk.c
@@ -1006,6 +1006,7 @@ int btmtk_usb_recv_acl(struct hci_dev *hdev, struct sk_buff *skb)
fallthrough;
case 0x05ff: /* Firmware debug logging 1 */
case 0x05fe: /* Firmware debug logging 2 */
+ case 0x2efd: /* Firmware debug event */
return hci_recv_diag(hdev, skb);
}
diff --git a/drivers/bluetooth/btmtksdio.c b/drivers/bluetooth/btmtksdio.c
index b7f0be7fc42a..cba52724f867 100644
--- a/drivers/bluetooth/btmtksdio.c
+++ b/drivers/bluetooth/btmtksdio.c
@@ -460,6 +460,7 @@ static int btmtksdio_recv_acl(struct hci_dev *hdev, struct sk_buff *skb)
fallthrough;
case 0x05ff:
case 0x05fe:
+ case 0x2efd: /* Firmware debug event */
/* Firmware debug logging */
return hci_recv_diag(hdev, skb);
}
--
2.45.2
^ permalink raw reply related [flat|nested] 2+ messages in thread
* RE: Bluetooth: btmtk: Route firmware debug event to the diag channel
2026-08-26 11:16 [PATCH] Bluetooth: btmtk: Route firmware debug event to the diag channel Chris Lu
@ 2026-08-26 11:55 ` bluez.test.bot
0 siblings, 0 replies; 2+ messages in thread
From: bluez.test.bot @ 2026-08-26 11:55 UTC (permalink / raw)
To: linux-bluetooth, chris.lu
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1152025
---Test result---
Test Summary:
CheckPatch PASS 0.94 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 0.38 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 26.15 seconds
CheckAllWarning PASS 29.55 seconds
CheckSparse PASS 27.91 seconds
BuildKernel32 PASS 25.85 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 469.93 seconds
IncrementalBuild PASS 24.85 seconds
Details
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/655
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-08-26 11:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-26 11:16 [PATCH] Bluetooth: btmtk: Route firmware debug event to the diag channel Chris Lu
2026-08-26 11:55 ` bluez.test.bot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox