Skip to contentSkip to conversation

Bluetooth: btmtk: Route firmware debug event to the diag channel

PATCH In review Chris Lu 2 participants 3 messages Aug 26 – Sep 10

Subsystems (2)
lore
Share & tools
lore

Chris Lu

author
#0 lore raw

PATCH 1/1 Bluetooth: btmtk: Route firmware debug event to the diag channel

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.

---
 drivers/bluetooth/btmtk.c     | 1 +
 drivers/bluetooth/btmtksdio.c | 1 +
 2 files changed, 2 insertions(+)
drivers/bluetooth/btmtk.c +1 -0
index 73ba4a029e9c..8563ab06a99f 100644
@@ -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);
 	}
 
drivers/bluetooth/btmtksdio.c +1 -0
index b7f0be7fc42a..cba52724f867 100644
@@ -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);
 	}
Signature · 1 line
2.45.2
#1 lore raw

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

#2 lore raw
In reply to Chris Lu

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/series/1152025/

---Test result---

Test Summary:

CheckPatch                    PASS      0.83 seconds
VerifyFixes                   PASS      0.08 seconds
VerifySignedoff               PASS      0.07 seconds
GitLint                       PASS      0.21 seconds
SubjectPrefix                 PASS      0.07 seconds
BuildKernel                   PASS      22.53 seconds
CheckAllWarning               PASS      30.69 seconds
CheckSparse                   PASS      27.35 seconds
BuildKernel32                 PASS      22.49 seconds
CheckKernelLLVM               PASS      23.42 seconds
TestRunnerSetup               PASS      562.17 seconds
IncrementalBuild              PASS      23.60 seconds

https://github.com/bluez/bluetooth-next/pull/747

---
Regards,
Linux Bluetooth