* [PATCH v1] Bluetooth: btintel_pcie: Trigger device coredump on hardware exception
@ 2025-03-04 16:21 Kiran K
2025-03-04 17:04 ` [v1] " bluez.test.bot
0 siblings, 1 reply; 2+ messages in thread
From: Kiran K @ 2025-03-04 16:21 UTC (permalink / raw)
To: linux-bluetooth
Cc: ravishankar.srivatsa, chethan.tumkur.narayan,
chandrashekar.devegowda, vijay.satija, Kiran K
Driver dumps device core dump on firmware exception.
Signed-off-by: Kiran K <kiran.k@intel.com>
---
drivers/bluetooth/btintel_pcie.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/bluetooth/btintel_pcie.c b/drivers/bluetooth/btintel_pcie.c
index a499bad58b53..3c3699250312 100644
--- a/drivers/bluetooth/btintel_pcie.c
+++ b/drivers/bluetooth/btintel_pcie.c
@@ -60,6 +60,7 @@ MODULE_DEVICE_TABLE(pci, btintel_pcie_table);
#define BTINTEL_PCIE_MAGIC_NUM 0xA5A5A5A5
#define BTINTEL_PCIE_TRIGGER_REASON_USER_TRIGGER 0x17A2
+#define BTINTEL_PCIE_TRIGGER_REASON_FW_ASSERT 0x1E61
/* Alive interrupt context */
enum {
@@ -1202,6 +1203,10 @@ static void btintel_pcie_msix_hw_exp_handler(struct btintel_pcie_data *data)
if (test_and_set_bit(BTINTEL_PCIE_HWEXP_INPROGRESS, &data->flags))
return;
+
+ /* Trigger device core dump when there is HW exception */
+ if (!test_and_set_bit(BTINTEL_PCIE_COREDUMP_INPROGRESS, &data->flags))
+ data->dmp_hdr.trigger_reason = BTINTEL_PCIE_TRIGGER_REASON_FW_ASSERT;
queue_work(data->workqueue, &data->rx_work);
}
--
2.43.0
^ permalink raw reply related [flat|nested] 2+ messages in thread
* RE: [v1] Bluetooth: btintel_pcie: Trigger device coredump on hardware exception
2025-03-04 16:21 [PATCH v1] Bluetooth: btintel_pcie: Trigger device coredump on hardware exception Kiran K
@ 2025-03-04 17:04 ` bluez.test.bot
0 siblings, 0 replies; 2+ messages in thread
From: bluez.test.bot @ 2025-03-04 17:04 UTC (permalink / raw)
To: linux-bluetooth, kiran.k
[-- Attachment #1: Type: text/plain, Size: 1947 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=940159
---Test result---
Test Summary:
CheckPatch PENDING 0.25 seconds
GitLint PENDING 0.23 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 25.05 seconds
CheckAllWarning PASS 27.66 seconds
CheckSparse PASS 30.73 seconds
BuildKernel32 PASS 24.91 seconds
TestRunnerSetup PASS 435.45 seconds
TestRunner_l2cap-tester PASS 21.36 seconds
TestRunner_iso-tester PASS 31.99 seconds
TestRunner_bnep-tester PASS 4.85 seconds
TestRunner_mgmt-tester PASS 122.68 seconds
TestRunner_rfcomm-tester PASS 10.31 seconds
TestRunner_sco-tester PASS 12.72 seconds
TestRunner_ioctl-tester PASS 8.95 seconds
TestRunner_mesh-tester FAIL 6.39 seconds
TestRunner_smp-tester PASS 7.32 seconds
TestRunner_userchan-tester PASS 5.09 seconds
IncrementalBuild PENDING 0.93 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 2 Failed 0.117 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-03-04 17:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-04 16:21 [PATCH v1] Bluetooth: btintel_pcie: Trigger device coredump on hardware exception Kiran K
2025-03-04 17:04 ` [v1] " 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