* Re: [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support
2026-04-08 8:32 [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support kaihsin
@ 2026-04-08 8:46 ` Paul Menzel
2026-04-08 14:46 ` Luiz Augusto von Dentz
2026-04-08 9:21 ` [PATCH v2] Bluetooth: Add Synaptics " kaihsin Chung
` (4 subsequent siblings)
5 siblings, 1 reply; 14+ messages in thread
From: Paul Menzel @ 2026-04-08 8:46 UTC (permalink / raw)
To: Kaihsin Chung
Cc: marcel, luiz.von.dentz, linux-bluetooth, linux-kernel,
Kaihsin Chung
Dear Kaihsin,
Thank you for your patch.
Am 08.04.26 um 10:32 schrieb kaihsin:
Please add an elaborate commit message.
> Signed-off-by: kaihsin <kaihsin.chung@synaptics.com>
Please configure to use the full name:
git config --global user.name "Kaihsin Chung"
git commit --amend --author="Kaihsin Chung
<kaihsin.chung@synaptics.com>" -s
Then please re-roll as v2 (`git format-patch -v2 …`).
> ---
> drivers/bluetooth/btbcm.c | 2 ++
> drivers/bluetooth/hci_bcm.c | 3 ++-
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/bluetooth/btbcm.c b/drivers/bluetooth/btbcm.c
> index f9a7c790d7e2..21ef875d6aa7 100644
> --- a/drivers/bluetooth/btbcm.c
> +++ b/drivers/bluetooth/btbcm.c
> @@ -515,6 +515,8 @@ static const struct bcm_subver_table bcm_uart_subver_table[] = {
> { 0x4106, "BCM4335A0" }, /* 002.001.006 */
> { 0x410c, "BCM43430B0" }, /* 002.001.012 */
> { 0x2119, "BCM4373A0" }, /* 001.001.025 */
> + { 0x2128, "BCM4384A0_AP6684P" },/* 001.001.040 */
> + { 0x4119, "BCM4384B0_AP6684PL"},/* 002.001.025 */
> { }
> };
>
> diff --git a/drivers/bluetooth/hci_bcm.c b/drivers/bluetooth/hci_bcm.c
> index 874d23089b39..972685e83b8a 100644
> --- a/drivers/bluetooth/hci_bcm.c
> +++ b/drivers/bluetooth/hci_bcm.c
> @@ -1609,7 +1609,8 @@ static const struct of_device_id bcm_bluetooth_of_match[] = {
> { .compatible = "brcm,bcm4335a0" },
> { .compatible = "cypress,cyw4373a0-bt", .data = &cyw4373a0_device_data },
> { .compatible = "infineon,cyw55572-bt", .data = &cyw55572_device_data },
> - { },
> + { .compatible = "brcm,bcm4384-bt" },
> + { },
Any idea, why the empty element is shown as changed?
> };
> MODULE_DEVICE_TABLE(of, bcm_bluetooth_of_match);
> #endif
Kind regards,
Paul
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support
2026-04-08 8:46 ` Paul Menzel
@ 2026-04-08 14:46 ` Luiz Augusto von Dentz
0 siblings, 0 replies; 14+ messages in thread
From: Luiz Augusto von Dentz @ 2026-04-08 14:46 UTC (permalink / raw)
To: Paul Menzel
Cc: Kaihsin Chung, marcel, luiz.von.dentz, linux-bluetooth,
linux-kernel, Kaihsin Chung
Hi,
On Wed, Apr 8, 2026 at 4:47 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>
> Dear Kaihsin,
>
>
> Thank you for your patch.
>
> Am 08.04.26 um 10:32 schrieb kaihsin:
>
> Please add an elaborate commit message.
>
> > Signed-off-by: kaihsin <kaihsin.chung@synaptics.com>
>
> Please configure to use the full name:
>
> git config --global user.name "Kaihsin Chung"
> git commit --amend --author="Kaihsin Chung
> <kaihsin.chung@synaptics.com>" -s
>
> Then please re-roll as v2 (`git format-patch -v2 …`).
>
> > ---
> > drivers/bluetooth/btbcm.c | 2 ++
> > drivers/bluetooth/hci_bcm.c | 3 ++-
> > 2 files changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/bluetooth/btbcm.c b/drivers/bluetooth/btbcm.c
> > index f9a7c790d7e2..21ef875d6aa7 100644
> > --- a/drivers/bluetooth/btbcm.c
> > +++ b/drivers/bluetooth/btbcm.c
> > @@ -515,6 +515,8 @@ static const struct bcm_subver_table bcm_uart_subver_table[] = {
> > { 0x4106, "BCM4335A0" }, /* 002.001.006 */
> > { 0x410c, "BCM43430B0" }, /* 002.001.012 */
> > { 0x2119, "BCM4373A0" }, /* 001.001.025 */
> > + { 0x2128, "BCM4384A0_AP6684P" },/* 001.001.040 */
> > + { 0x4119, "BCM4384B0_AP6684PL"},/* 002.001.025 */
> > { }
> > };
> >
> > diff --git a/drivers/bluetooth/hci_bcm.c b/drivers/bluetooth/hci_bcm.c
> > index 874d23089b39..972685e83b8a 100644
> > --- a/drivers/bluetooth/hci_bcm.c
> > +++ b/drivers/bluetooth/hci_bcm.c
> > @@ -1609,7 +1609,8 @@ static const struct of_device_id bcm_bluetooth_of_match[] = {
> > { .compatible = "brcm,bcm4335a0" },
> > { .compatible = "cypress,cyw4373a0-bt", .data = &cyw4373a0_device_data },
> > { .compatible = "infineon,cyw55572-bt", .data = &cyw55572_device_data },
> > - { },
> > + { .compatible = "brcm,bcm4384-bt" },
> > + { },
>
> Any idea, why the empty element is shown as changed?
Most likely identation changed like capture by sashiko:
https://sashiko.dev/#/patchset/20260408092128.1915973-1-kaihsin.chung%40synaptics.com
> > };
> > MODULE_DEVICE_TABLE(of, bcm_bluetooth_of_match);
> > #endif
>
>
> Kind regards,
>
> Paul
>
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 14+ messages in thread
* [PATCH v2] Bluetooth: Add Synaptics 4384 Chip Support
2026-04-08 8:32 [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support kaihsin
2026-04-08 8:46 ` Paul Menzel
@ 2026-04-08 9:21 ` kaihsin Chung
2026-04-08 10:31 ` [v2] " bluez.test.bot
2026-04-08 9:21 ` Bluetooth: Add Synaptcis " bluez.test.bot
` (3 subsequent siblings)
5 siblings, 1 reply; 14+ messages in thread
From: kaihsin Chung @ 2026-04-08 9:21 UTC (permalink / raw)
To: linux-bluetooth; +Cc: marcel, luiz.von.dentz, linux-kernel, Kaihsin Chung
From: Kaihsin Chung <kaihsin.chung@synaptics.com>
Add BCM4384A0 and BCM4384B0 identifiers to the Broadcom Bluetooth
subversion table and add device tree matching for brcm,bcm4384-bt.
Signed-off-by: kaihsin Chung <kaihsin.chung@synaptics.com>
---
drivers/bluetooth/btbcm.c | 2 ++
drivers/bluetooth/hci_bcm.c | 3 ++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/bluetooth/btbcm.c b/drivers/bluetooth/btbcm.c
index f9a7c790d7e2..21ef875d6aa7 100644
--- a/drivers/bluetooth/btbcm.c
+++ b/drivers/bluetooth/btbcm.c
@@ -515,6 +515,8 @@ static const struct bcm_subver_table bcm_uart_subver_table[] = {
{ 0x4106, "BCM4335A0" }, /* 002.001.006 */
{ 0x410c, "BCM43430B0" }, /* 002.001.012 */
{ 0x2119, "BCM4373A0" }, /* 001.001.025 */
+ { 0x2128, "BCM4384A0_AP6684P" },/* 001.001.040 */
+ { 0x4119, "BCM4384B0_AP6684PL"},/* 002.001.025 */
{ }
};
diff --git a/drivers/bluetooth/hci_bcm.c b/drivers/bluetooth/hci_bcm.c
index 874d23089b39..972685e83b8a 100644
--- a/drivers/bluetooth/hci_bcm.c
+++ b/drivers/bluetooth/hci_bcm.c
@@ -1609,7 +1609,8 @@ static const struct of_device_id bcm_bluetooth_of_match[] = {
{ .compatible = "brcm,bcm4335a0" },
{ .compatible = "cypress,cyw4373a0-bt", .data = &cyw4373a0_device_data },
{ .compatible = "infineon,cyw55572-bt", .data = &cyw55572_device_data },
- { },
+ { .compatible = "brcm,bcm4384-bt" },
+ { },
};
MODULE_DEVICE_TABLE(of, bcm_bluetooth_of_match);
#endif
--
2.43.0
^ permalink raw reply related [flat|nested] 14+ messages in thread* RE: [v2] Bluetooth: Add Synaptics 4384 Chip Support
2026-04-08 9:21 ` [PATCH v2] Bluetooth: Add Synaptics " kaihsin Chung
@ 2026-04-08 10:31 ` bluez.test.bot
0 siblings, 0 replies; 14+ messages in thread
From: bluez.test.bot @ 2026-04-08 10:31 UTC (permalink / raw)
To: linux-bluetooth, kaihsin.chung
[-- Attachment #1: Type: text/plain, Size: 2593 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=1078548
---Test result---
Test Summary:
CheckPatch PENDING 0.36 seconds
GitLint PENDING 0.23 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 26.12 seconds
CheckAllWarning PASS 28.42 seconds
CheckSparse PASS 27.57 seconds
BuildKernel32 PASS 25.43 seconds
TestRunnerSetup PASS 564.78 seconds
TestRunner_l2cap-tester PASS 27.77 seconds
TestRunner_iso-tester PASS 33.34 seconds
TestRunner_bnep-tester PASS 6.36 seconds
TestRunner_mgmt-tester FAIL 113.95 seconds
TestRunner_rfcomm-tester PASS 9.37 seconds
TestRunner_sco-tester FAIL 14.38 seconds
TestRunner_ioctl-tester PASS 10.17 seconds
TestRunner_mesh-tester FAIL 11.55 seconds
TestRunner_smp-tester PASS 8.54 seconds
TestRunner_userchan-tester PASS 6.69 seconds
IncrementalBuild PENDING 0.49 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.113 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.910 seconds
Mesh - Send cancel - 2 Timed out 1.997 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Bluetooth: Add Synaptcis 4384 Chip Support
2026-04-08 8:32 [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support kaihsin
2026-04-08 8:46 ` Paul Menzel
2026-04-08 9:21 ` [PATCH v2] Bluetooth: Add Synaptics " kaihsin Chung
@ 2026-04-08 9:21 ` bluez.test.bot
2026-04-09 1:30 ` [PATCH v3] Bluetooth: Add Synaptics " kaihsin Chung
` (2 subsequent siblings)
5 siblings, 0 replies; 14+ messages in thread
From: bluez.test.bot @ 2026-04-08 9:21 UTC (permalink / raw)
To: linux-bluetooth, kaihsin.chung
[-- Attachment #1: Type: text/plain, Size: 2861 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=1078531
---Test result---
Test Summary:
CheckPatch PENDING 0.53 seconds
GitLint PENDING 0.34 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 25.95 seconds
CheckAllWarning PASS 28.38 seconds
CheckSparse PASS 27.41 seconds
BuildKernel32 PASS 24.95 seconds
TestRunnerSetup PASS 561.74 seconds
TestRunner_l2cap-tester FAIL 27.93 seconds
TestRunner_iso-tester PASS 43.26 seconds
TestRunner_bnep-tester PASS 6.38 seconds
TestRunner_mgmt-tester FAIL 113.01 seconds
TestRunner_rfcomm-tester PASS 9.37 seconds
TestRunner_sco-tester FAIL 14.44 seconds
TestRunner_ioctl-tester PASS 10.09 seconds
TestRunner_mesh-tester FAIL 12.60 seconds
TestRunner_smp-tester PASS 8.49 seconds
TestRunner_userchan-tester PASS 6.61 seconds
IncrementalBuild PENDING 0.99 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
Total: 96, Passed: 95 (99.0%), Failed: 1, Not Run: 0
Failed Test Cases
L2CAP BR/EDR Server - Set PHY 1M Failed 0.112 seconds
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.104 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
BUG: sleeping function called from invalid context at net/core/sock.c:3782
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.749 seconds
Mesh - Send cancel - 2 Timed out 1.996 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 14+ messages in thread* [PATCH v3] Bluetooth: Add Synaptics 4384 Chip Support
2026-04-08 8:32 [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support kaihsin
` (2 preceding siblings ...)
2026-04-08 9:21 ` Bluetooth: Add Synaptcis " bluez.test.bot
@ 2026-04-09 1:30 ` kaihsin Chung
2026-04-09 20:19 ` [v3] " bluez.test.bot
2026-04-09 20:20 ` Bluetooth: Add Synaptcis " bluez.test.bot
2026-05-13 2:20 ` [PATCH v4] Bluetooth: Add Synaptics " kaihsin Chung
5 siblings, 1 reply; 14+ messages in thread
From: kaihsin Chung @ 2026-04-09 1:30 UTC (permalink / raw)
To: linux-bluetooth; +Cc: marcel, luiz.von.dentz, linux-kernel, Kaihsin Chung
From: Kaihsin Chung <kaihsin.chung@synaptics.com>
Add BCM4384A0 and BCM4384B0 identifiers to the Broadcom Bluetooth
subversion table and add device tree matching for brcm,bcm4384-bt.
Signed-off-by: kaihsin Chung <kaihsin.chung@synaptics.com>
---
drivers/bluetooth/btbcm.c | 2 ++
drivers/bluetooth/hci_bcm.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/btbcm.c b/drivers/bluetooth/btbcm.c
index f9a7c790d7e2..21ef875d6aa7 100644
--- a/drivers/bluetooth/btbcm.c
+++ b/drivers/bluetooth/btbcm.c
@@ -515,6 +515,8 @@ static const struct bcm_subver_table bcm_uart_subver_table[] = {
{ 0x4106, "BCM4335A0" }, /* 002.001.006 */
{ 0x410c, "BCM43430B0" }, /* 002.001.012 */
{ 0x2119, "BCM4373A0" }, /* 001.001.025 */
+ { 0x2128, "BCM4384A0_AP6684P" },/* 001.001.040 */
+ { 0x4119, "BCM4384B0_AP6684PL"},/* 002.001.025 */
{ }
};
diff --git a/drivers/bluetooth/hci_bcm.c b/drivers/bluetooth/hci_bcm.c
index 874d23089b39..783346a4a59b 100644
--- a/drivers/bluetooth/hci_bcm.c
+++ b/drivers/bluetooth/hci_bcm.c
@@ -1609,6 +1609,7 @@ static const struct of_device_id bcm_bluetooth_of_match[] = {
{ .compatible = "brcm,bcm4335a0" },
{ .compatible = "cypress,cyw4373a0-bt", .data = &cyw4373a0_device_data },
{ .compatible = "infineon,cyw55572-bt", .data = &cyw55572_device_data },
+ { .compatible = "brcm,bcm4384-bt" },
{ },
};
MODULE_DEVICE_TABLE(of, bcm_bluetooth_of_match);
--
2.43.0
^ permalink raw reply related [flat|nested] 14+ messages in thread* RE: [v3] Bluetooth: Add Synaptics 4384 Chip Support
2026-04-09 1:30 ` [PATCH v3] Bluetooth: Add Synaptics " kaihsin Chung
@ 2026-04-09 20:19 ` bluez.test.bot
2026-04-10 14:16 ` Luiz Augusto von Dentz
0 siblings, 1 reply; 14+ messages in thread
From: bluez.test.bot @ 2026-04-09 20:19 UTC (permalink / raw)
To: linux-bluetooth, kaihsin.chung
[-- Attachment #1: Type: text/plain, Size: 6877 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=1078977
---Test result---
Test Summary:
CheckPatch PENDING 0.51 seconds
GitLint PENDING 0.47 seconds
SubjectPrefix PASS 0.06 seconds
BuildKernel PASS 26.48 seconds
CheckAllWarning PASS 28.63 seconds
CheckSparse PASS 27.53 seconds
BuildKernel32 PASS 25.59 seconds
TestRunnerSetup PASS 567.27 seconds
TestRunner_l2cap-tester PASS 27.85 seconds
TestRunner_iso-tester PASS 38.54 seconds
TestRunner_bnep-tester PASS 6.42 seconds
TestRunner_mgmt-tester FAIL 113.62 seconds
TestRunner_rfcomm-tester PASS 9.34 seconds
TestRunner_sco-tester FAIL 14.29 seconds
TestRunner_ioctl-tester PASS 10.37 seconds
TestRunner_mesh-tester FAIL 11.55 seconds
TestRunner_smp-tester PASS 8.52 seconds
TestRunner_userchan-tester PASS 6.59 seconds
TestRunner_6lowpan-tester FAIL 8.58 seconds
IncrementalBuild PENDING 0.34 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.107 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
7.0.0-rc2-g4eb3d58cb92c #1 Not tainted
------------------------------------------------------
kworker/u5:2/117 is trying to acquire lock:
ffff888001abe240 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_connect_cfm+0x358/0x8d0
but task is already holding lock:
ffff888002090c20 (&conn->lock){+.+.}-{3:3}, at: sco_connect_cfm+0x22d/0x8d0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&conn->lock){+.+.}-{3:3}:
lock_acquire+0xf7/0x2c0
_raw_spin_lock+0x2a/0x40
sco_sock_connect+0x4d7/0x1280
__sys_connect+0x1a3/0x260
__x64_sys_connect+0x6e/0xb0
do_syscall_64+0xa0/0x570
entry_SYSCALL_64_after_hwframe+0x74/0x7c
-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:
check_prev_add+0xe9/0xc70
__lock_acquire+0x1457/0x1df0
lock_acquire+0xf7/0x2c0
lock_sock_nested+0x36/0xd0
sco_connect_cfm+0x358/0x8d0
hci_sync_conn_complete_evt+0x3d3/0x8e0
hci_event_packet+0x74f/0xb10
hci_rx_work+0x398/0xd00
process_scheduled_works+0xb16/0x1ac0
worker_thread+0x4ff/0xba0
kthread+0x368/0x490
ret_from_fork+0x498/0x7e0
ret_from_fork_asm+0x19/0x30
other info that might help us debug this:
...
BUG: sleeping function called from invalid context at net/core/sock.c:3782
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 117, name: kworker/u5:2
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
INFO: lockdep is turned off.
CPU: 0 UID: 0 PID: 117 Comm: kworker/u5:2 Not tainted 7.0.0-rc2-g4eb3d58cb92c #1 PREEMPT(lazy)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
Workqueue: hci0 hci_rx_work
Call Trace:
<TASK>
dump_stack_lvl+0x49/0x60
__might_resched+0x2ea/0x500
lock_sock_nested+0x47/0xd0
? sco_connect_cfm+0x358/0x8d0
sco_connect_cfm+0x358/0x8d0
? hci_debugfs_create_conn+0x190/0x210
? __pfx_sco_connect_cfm+0x10/0x10
hci_sync_conn_complete_evt+0x3d3/0x8e0
hci_event_packet+0x74f/0xb10
? __pfx_hci_sync_conn_complete_evt+0x10/0x10
? __pfx_hci_event_packet+0x10/0x10
? mark_held_locks+0x49/0x80
? lockdep_hardirqs_on_prepare+0xd4/0x180
? _raw_spin_unlock_irqrestore+0x2c/0x50
hci_rx_work+0x398/0xd00
process_scheduled_works+0xb16/0x1ac0
? __pfx_process_scheduled_works+0x10/0x10
? lock_acquire+0xf7/0x2c0
? lock_is_held_type+0x9b/0x110
? __pfx_hci_rx_work+0x10/0x10
worker_thread+0x4ff/0xba0
? _raw_spin_unlock_irqrestore+0x2c/0x50
? __pfx_worker_thread+0x10/0x10
kthread+0x368/0x490
? _raw_spin_unlock_irq+0x23/0x40
? __pfx_kthread+0x10/0x10
ret_from_fork+0x498/0x7e0
? __pfx_ret_from_fork+0x10/0x10
? __switch_to+0x9e4/0xe50
? __switch_to_asm+0x32/0x60
...
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.859 seconds
Mesh - Send cancel - 2 Timed out 1.996 seconds
##############################
Test: TestRunner_6lowpan-tester - FAIL
Desc: Run 6lowpan-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
7.0.0-rc2-g4eb3d58cb92c #1 Not tainted
------------------------------------------------------
kworker/0:1/11 is trying to acquire lock:
ffff8880026e5140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x75/0x180
but task is already holding lock:
ffffffffb6e4d7a0 (rtnl_mutex){+.+.}-{4:4}, at: lowpan_unregister_netdev+0xd/0x30
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #4 (rtnl_mutex){+.+.}-{4:4}:
lock_acquire+0xf7/0x2c0
__mutex_lock+0x16b/0x1fc0
lowpan_register_netdev+0x11/0x30
chan_ready_cb+0x836/0xd00
l2cap_recv_frame+0x6a06/0x8920
l2cap_recv_acldata+0x790/0xdf0
hci_rx_work+0x500/0xd00
process_scheduled_works+0xb16/0x1ac0
worker_thread+0x4ff/0xba0
kthread+0x368/0x490
ret_from_fork+0x498/0x7e0
ret_from_fork_asm+0x19/0x30
-> #3 (&chan->lock#3/1){+.+.}-{4:4}:
lock_acquire+0xf7/0x2c0
__mutex_lock+0x16b/0x1fc0
l2cap_chan_connect+0x74e/0x1980
lowpan_control_write+0x523/0x660
full_proxy_write+0x10b/0x190
vfs_write+0x1c0/0xf60
ksys_write+0xf1/0x1d0
do_syscall_64+0xa0/0x570
entry_SYSCALL_64_after_hwframe+0x74/0x7c
-> #2 (&conn->lock){+.+.}-{4:4}:
...
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
https://github.com/bluez/bluetooth-next/pull/56/checks
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [v3] Bluetooth: Add Synaptics 4384 Chip Support
2026-04-09 20:19 ` [v3] " bluez.test.bot
@ 2026-04-10 14:16 ` Luiz Augusto von Dentz
2026-04-29 9:32 ` Kaihsin Chung
0 siblings, 1 reply; 14+ messages in thread
From: Luiz Augusto von Dentz @ 2026-04-10 14:16 UTC (permalink / raw)
To: linux-bluetooth; +Cc: kaihsin.chung
Hi,
On Thu, Apr 9, 2026 at 4:20 PM <bluez.test.bot@gmail.com> wrote:
>
> 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=1078977
>
> ---Test result---
>
> Test Summary:
> CheckPatch PENDING 0.51 seconds
> GitLint PENDING 0.47 seconds
> SubjectPrefix PASS 0.06 seconds
> BuildKernel PASS 26.48 seconds
> CheckAllWarning PASS 28.63 seconds
> CheckSparse PASS 27.53 seconds
> BuildKernel32 PASS 25.59 seconds
> TestRunnerSetup PASS 567.27 seconds
> TestRunner_l2cap-tester PASS 27.85 seconds
> TestRunner_iso-tester PASS 38.54 seconds
> TestRunner_bnep-tester PASS 6.42 seconds
> TestRunner_mgmt-tester FAIL 113.62 seconds
> TestRunner_rfcomm-tester PASS 9.34 seconds
> TestRunner_sco-tester FAIL 14.29 seconds
> TestRunner_ioctl-tester PASS 10.37 seconds
> TestRunner_mesh-tester FAIL 11.55 seconds
> TestRunner_smp-tester PASS 8.52 seconds
> TestRunner_userchan-tester PASS 6.59 seconds
> TestRunner_6lowpan-tester FAIL 8.58 seconds
> IncrementalBuild PENDING 0.34 seconds
>
> Details
> ##############################
> Test: CheckPatch - PENDING
> Desc: Run checkpatch.pl script
> Output:
>
> ##############################
> Test: GitLint - PENDING
> Desc: Run gitlint
> Output:
>
> ##############################
> Test: TestRunner_mgmt-tester - FAIL
> Desc: Run mgmt-tester with test-runner
> Output:
> Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
>
> Failed Test Cases
> Read Exp Feature - Success Failed 0.107 seconds
> ##############################
> Test: TestRunner_sco-tester - FAIL
> Desc: Run sco-tester with test-runner
> Output:
> WARNING: possible circular locking dependency detected
> 7.0.0-rc2-g4eb3d58cb92c #1 Not tainted
> ------------------------------------------------------
> kworker/u5:2/117 is trying to acquire lock:
> ffff888001abe240 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_connect_cfm+0x358/0x8d0
>
> but task is already holding lock:
> ffff888002090c20 (&conn->lock){+.+.}-{3:3}, at: sco_connect_cfm+0x22d/0x8d0
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
>
> -> #1 (&conn->lock){+.+.}-{3:3}:
> lock_acquire+0xf7/0x2c0
> _raw_spin_lock+0x2a/0x40
> sco_sock_connect+0x4d7/0x1280
> __sys_connect+0x1a3/0x260
> __x64_sys_connect+0x6e/0xb0
> do_syscall_64+0xa0/0x570
> entry_SYSCALL_64_after_hwframe+0x74/0x7c
>
> -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:
> check_prev_add+0xe9/0xc70
> __lock_acquire+0x1457/0x1df0
> lock_acquire+0xf7/0x2c0
> lock_sock_nested+0x36/0xd0
> sco_connect_cfm+0x358/0x8d0
> hci_sync_conn_complete_evt+0x3d3/0x8e0
> hci_event_packet+0x74f/0xb10
> hci_rx_work+0x398/0xd00
> process_scheduled_works+0xb16/0x1ac0
> worker_thread+0x4ff/0xba0
> kthread+0x368/0x490
> ret_from_fork+0x498/0x7e0
> ret_from_fork_asm+0x19/0x30
>
> other info that might help us debug this:
>
> ...
> BUG: sleeping function called from invalid context at net/core/sock.c:3782
> in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 117, name: kworker/u5:2
> preempt_count: 1, expected: 0
> RCU nest depth: 0, expected: 0
> INFO: lockdep is turned off.
> CPU: 0 UID: 0 PID: 117 Comm: kworker/u5:2 Not tainted 7.0.0-rc2-g4eb3d58cb92c #1 PREEMPT(lazy)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
> Workqueue: hci0 hci_rx_work
> Call Trace:
> <TASK>
> dump_stack_lvl+0x49/0x60
> __might_resched+0x2ea/0x500
> lock_sock_nested+0x47/0xd0
> ? sco_connect_cfm+0x358/0x8d0
> sco_connect_cfm+0x358/0x8d0
> ? hci_debugfs_create_conn+0x190/0x210
> ? __pfx_sco_connect_cfm+0x10/0x10
> hci_sync_conn_complete_evt+0x3d3/0x8e0
> hci_event_packet+0x74f/0xb10
> ? __pfx_hci_sync_conn_complete_evt+0x10/0x10
> ? __pfx_hci_event_packet+0x10/0x10
> ? mark_held_locks+0x49/0x80
> ? lockdep_hardirqs_on_prepare+0xd4/0x180
> ? _raw_spin_unlock_irqrestore+0x2c/0x50
> hci_rx_work+0x398/0xd00
> process_scheduled_works+0xb16/0x1ac0
> ? __pfx_process_scheduled_works+0x10/0x10
> ? lock_acquire+0xf7/0x2c0
> ? lock_is_held_type+0x9b/0x110
> ? __pfx_hci_rx_work+0x10/0x10
> worker_thread+0x4ff/0xba0
> ? _raw_spin_unlock_irqrestore+0x2c/0x50
> ? __pfx_worker_thread+0x10/0x10
> kthread+0x368/0x490
> ? _raw_spin_unlock_irq+0x23/0x40
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x498/0x7e0
> ? __pfx_ret_from_fork+0x10/0x10
> ? __switch_to+0x9e4/0xe50
> ? __switch_to_asm+0x32/0x60
> ...
> Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
> ##############################
> Test: TestRunner_mesh-tester - FAIL
> Desc: Run mesh-tester with test-runner
> Output:
> Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
>
> Failed Test Cases
> Mesh - Send cancel - 1 Timed out 1.859 seconds
> Mesh - Send cancel - 2 Timed out 1.996 seconds
> ##############################
> Test: TestRunner_6lowpan-tester - FAIL
> Desc: Run 6lowpan-tester with test-runner
> Output:
> WARNING: possible circular locking dependency detected
> 7.0.0-rc2-g4eb3d58cb92c #1 Not tainted
> ------------------------------------------------------
> kworker/0:1/11 is trying to acquire lock:
> ffff8880026e5140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x75/0x180
>
> but task is already holding lock:
> ffffffffb6e4d7a0 (rtnl_mutex){+.+.}-{4:4}, at: lowpan_unregister_netdev+0xd/0x30
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
>
> -> #4 (rtnl_mutex){+.+.}-{4:4}:
> lock_acquire+0xf7/0x2c0
> __mutex_lock+0x16b/0x1fc0
> lowpan_register_netdev+0x11/0x30
> chan_ready_cb+0x836/0xd00
> l2cap_recv_frame+0x6a06/0x8920
> l2cap_recv_acldata+0x790/0xdf0
> hci_rx_work+0x500/0xd00
> process_scheduled_works+0xb16/0x1ac0
> worker_thread+0x4ff/0xba0
> kthread+0x368/0x490
> ret_from_fork+0x498/0x7e0
> ret_from_fork_asm+0x19/0x30
>
> -> #3 (&chan->lock#3/1){+.+.}-{4:4}:
> lock_acquire+0xf7/0x2c0
> __mutex_lock+0x16b/0x1fc0
> l2cap_chan_connect+0x74e/0x1980
> lowpan_control_write+0x523/0x660
> full_proxy_write+0x10b/0x190
> vfs_write+0x1c0/0xf60
> ksys_write+0xf1/0x1d0
> do_syscall_64+0xa0/0x570
> entry_SYSCALL_64_after_hwframe+0x74/0x7c
>
> -> #2 (&conn->lock){+.+.}-{4:4}:
> ...
> Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
> ##############################
> Test: IncrementalBuild - PENDING
> Desc: Incremental build with the patches in the series
> Output:
>
>
>
> https://github.com/bluez/bluetooth-next/pull/56/checks
Ive got the following error while trying to apply this change:
Applying: Bluetooth: Add Synaptics 4384 Chip Support
WARNING: DT compatible string "brcm,bcm4384-bt" appears un-documented
-- check ./Documentation/devicetree/bindings/
#22: FILE: drivers/bluetooth/hci_bcm.c:1597:
+ { .compatible = "brcm,bcm4384-bt" },
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 14+ messages in thread* RE: [v3] Bluetooth: Add Synaptics 4384 Chip Support
2026-04-10 14:16 ` Luiz Augusto von Dentz
@ 2026-04-29 9:32 ` Kaihsin Chung
0 siblings, 0 replies; 14+ messages in thread
From: Kaihsin Chung @ 2026-04-29 9:32 UTC (permalink / raw)
To: Luiz Augusto von Dentz, linux-bluetooth@vger.kernel.org
Cc: kaihsin.chung@synaptics.corp-partner.google.com
HI Luiz,
I didn't see the apply patch failure on my side.
From your log, do you mean we should also add document in Documentation/devicetree/bindings
B.R
KaiHsin
-----Original Message-----
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Sent: Friday, April 10, 2026 10:17 PM
To: linux-bluetooth@vger.kernel.org
Cc: kaihsin.chung@synaptics.corp-partner.google.com
Subject: Re: [v3] Bluetooth: Add Synaptics 4384 Chip Support
CAUTION: Email originated externally, do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi,
On Thu, Apr 9, 2026 at 4:20 PM <bluez.test.bot@gmail.com> wrote:
>
> 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://urldefense.proofpoint.com/v2/url?u=https-3A__patchwork.kernel.org_project_bluetooth_list_-3Fseries-3D1078977&d=DwIFaQ&c=7dfBJ8cXbWjhc0BhImu8wVIoUFmBzj1s88r8EGyM0UY&r=_rvKD1lVMETnjfJne-APcrTZP0H9q0aBYQGmJWPSXJQ&m=OONH5zv5vMU43bEEZ3QknB0gB_vrzW9LOONd11Vx0z2qGVcvR94hfOX8xdyUbdlL&s=KTuNrxunr5r0yeCKm5BgwRrxJ3qTqJA4IPRifZ6X21U&e=
>
> ---Test result---
>
> Test Summary:
> CheckPatch PENDING 0.51 seconds
> GitLint PENDING 0.47 seconds
> SubjectPrefix PASS 0.06 seconds
> BuildKernel PASS 26.48 seconds
> CheckAllWarning PASS 28.63 seconds
> CheckSparse PASS 27.53 seconds
> BuildKernel32 PASS 25.59 seconds
> TestRunnerSetup PASS 567.27 seconds
> TestRunner_l2cap-tester PASS 27.85 seconds
> TestRunner_iso-tester PASS 38.54 seconds
> TestRunner_bnep-tester PASS 6.42 seconds
> TestRunner_mgmt-tester FAIL 113.62 seconds
> TestRunner_rfcomm-tester PASS 9.34 seconds
> TestRunner_sco-tester FAIL 14.29 seconds
> TestRunner_ioctl-tester PASS 10.37 seconds
> TestRunner_mesh-tester FAIL 11.55 seconds
> TestRunner_smp-tester PASS 8.52 seconds
> TestRunner_userchan-tester PASS 6.59 seconds
> TestRunner_6lowpan-tester FAIL 8.58 seconds
> IncrementalBuild PENDING 0.34 seconds
>
> Details
> ##############################
> Test: CheckPatch - PENDING
> Desc: Run checkpatch.pl script
> Output:
>
> ##############################
> Test: GitLint - PENDING
> Desc: Run gitlint
> Output:
>
> ##############################
> Test: TestRunner_mgmt-tester - FAIL
> Desc: Run mgmt-tester with test-runner
> Output:
> Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
>
> Failed Test Cases
> Read Exp Feature - Success Failed 0.107 seconds
> ##############################
> Test: TestRunner_sco-tester - FAIL
> Desc: Run sco-tester with test-runner
> Output:
> WARNING: possible circular locking dependency detected
> 7.0.0-rc2-g4eb3d58cb92c #1 Not tainted
> ------------------------------------------------------
> kworker/u5:2/117 is trying to acquire lock:
> ffff888001abe240 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_connect_cfm+0x358/0x8d0
>
> but task is already holding lock:
> ffff888002090c20 (&conn->lock){+.+.}-{3:3}, at: sco_connect_cfm+0x22d/0x8d0
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
>
> -> #1 (&conn->lock){+.+.}-{3:3}:
> lock_acquire+0xf7/0x2c0
> _raw_spin_lock+0x2a/0x40
> sco_sock_connect+0x4d7/0x1280
> __sys_connect+0x1a3/0x260
> __x64_sys_connect+0x6e/0xb0
> do_syscall_64+0xa0/0x570
> entry_SYSCALL_64_after_hwframe+0x74/0x7c
>
> -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:
> check_prev_add+0xe9/0xc70
> __lock_acquire+0x1457/0x1df0
> lock_acquire+0xf7/0x2c0
> lock_sock_nested+0x36/0xd0
> sco_connect_cfm+0x358/0x8d0
> hci_sync_conn_complete_evt+0x3d3/0x8e0
> hci_event_packet+0x74f/0xb10
> hci_rx_work+0x398/0xd00
> process_scheduled_works+0xb16/0x1ac0
> worker_thread+0x4ff/0xba0
> kthread+0x368/0x490
> ret_from_fork+0x498/0x7e0
> ret_from_fork_asm+0x19/0x30
>
> other info that might help us debug this:
>
> ...
> BUG: sleeping function called from invalid context at net/core/sock.c:3782
> in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 117, name: kworker/u5:2
> preempt_count: 1, expected: 0
> RCU nest depth: 0, expected: 0
> INFO: lockdep is turned off.
> CPU: 0 UID: 0 PID: 117 Comm: kworker/u5:2 Not tainted 7.0.0-rc2-g4eb3d58cb92c #1 PREEMPT(lazy)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
> Workqueue: hci0 hci_rx_work
> Call Trace:
> <TASK>
> dump_stack_lvl+0x49/0x60
> __might_resched+0x2ea/0x500
> lock_sock_nested+0x47/0xd0
> ? sco_connect_cfm+0x358/0x8d0
> sco_connect_cfm+0x358/0x8d0
> ? hci_debugfs_create_conn+0x190/0x210
> ? __pfx_sco_connect_cfm+0x10/0x10
> hci_sync_conn_complete_evt+0x3d3/0x8e0
> hci_event_packet+0x74f/0xb10
> ? __pfx_hci_sync_conn_complete_evt+0x10/0x10
> ? __pfx_hci_event_packet+0x10/0x10
> ? mark_held_locks+0x49/0x80
> ? lockdep_hardirqs_on_prepare+0xd4/0x180
> ? _raw_spin_unlock_irqrestore+0x2c/0x50
> hci_rx_work+0x398/0xd00
> process_scheduled_works+0xb16/0x1ac0
> ? __pfx_process_scheduled_works+0x10/0x10
> ? lock_acquire+0xf7/0x2c0
> ? lock_is_held_type+0x9b/0x110
> ? __pfx_hci_rx_work+0x10/0x10
> worker_thread+0x4ff/0xba0
> ? _raw_spin_unlock_irqrestore+0x2c/0x50
> ? __pfx_worker_thread+0x10/0x10
> kthread+0x368/0x490
> ? _raw_spin_unlock_irq+0x23/0x40
> ? __pfx_kthread+0x10/0x10
> ret_from_fork+0x498/0x7e0
> ? __pfx_ret_from_fork+0x10/0x10
> ? __switch_to+0x9e4/0xe50
> ? __switch_to_asm+0x32/0x60
> ...
> Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
> ##############################
> Test: TestRunner_mesh-tester - FAIL
> Desc: Run mesh-tester with test-runner
> Output:
> Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
>
> Failed Test Cases
> Mesh - Send cancel - 1 Timed out 1.859 seconds
> Mesh - Send cancel - 2 Timed out 1.996 seconds
> ##############################
> Test: TestRunner_6lowpan-tester - FAIL
> Desc: Run 6lowpan-tester with test-runner
> Output:
> WARNING: possible circular locking dependency detected
> 7.0.0-rc2-g4eb3d58cb92c #1 Not tainted
> ------------------------------------------------------
> kworker/0:1/11 is trying to acquire lock:
> ffff8880026e5140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x75/0x180
>
> but task is already holding lock:
> ffffffffb6e4d7a0 (rtnl_mutex){+.+.}-{4:4}, at: lowpan_unregister_netdev+0xd/0x30
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
>
> -> #4 (rtnl_mutex){+.+.}-{4:4}:
> lock_acquire+0xf7/0x2c0
> __mutex_lock+0x16b/0x1fc0
> lowpan_register_netdev+0x11/0x30
> chan_ready_cb+0x836/0xd00
> l2cap_recv_frame+0x6a06/0x8920
> l2cap_recv_acldata+0x790/0xdf0
> hci_rx_work+0x500/0xd00
> process_scheduled_works+0xb16/0x1ac0
> worker_thread+0x4ff/0xba0
> kthread+0x368/0x490
> ret_from_fork+0x498/0x7e0
> ret_from_fork_asm+0x19/0x30
>
> -> #3 (&chan->lock#3/1){+.+.}-{4:4}:
> lock_acquire+0xf7/0x2c0
> __mutex_lock+0x16b/0x1fc0
> l2cap_chan_connect+0x74e/0x1980
> lowpan_control_write+0x523/0x660
> full_proxy_write+0x10b/0x190
> vfs_write+0x1c0/0xf60
> ksys_write+0xf1/0x1d0
> do_syscall_64+0xa0/0x570
> entry_SYSCALL_64_after_hwframe+0x74/0x7c
>
> -> #2 (&conn->lock){+.+.}-{4:4}:
> ...
> Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
> ##############################
> Test: IncrementalBuild - PENDING
> Desc: Incremental build with the patches in the series
> Output:
>
>
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_bluez_bluetooth-2Dnext_pull_56_checks&d=DwIFaQ&c=7dfBJ8cXbWjhc0BhImu8wVIoUFmBzj1s88r8EGyM0UY&r=_rvKD1lVMETnjfJne-APcrTZP0H9q0aBYQGmJWPSXJQ&m=OONH5zv5vMU43bEEZ3QknB0gB_vrzW9LOONd11Vx0z2qGVcvR94hfOX8xdyUbdlL&s=rpGqZ1uR_azOxaKMAqBf65sBjFIqPg5IPBQ2NIcisdY&e=
Ive got the following error while trying to apply this change:
Applying: Bluetooth: Add Synaptics 4384 Chip Support
WARNING: DT compatible string "brcm,bcm4384-bt" appears un-documented
-- check ./Documentation/devicetree/bindings/
#22: FILE: drivers/bluetooth/hci_bcm.c:1597:
+ { .compatible = "brcm,bcm4384-bt" },
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: Bluetooth: Add Synaptcis 4384 Chip Support
2026-04-08 8:32 [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support kaihsin
` (3 preceding siblings ...)
2026-04-09 1:30 ` [PATCH v3] Bluetooth: Add Synaptics " kaihsin Chung
@ 2026-04-09 20:20 ` bluez.test.bot
2026-05-13 2:20 ` [PATCH v4] Bluetooth: Add Synaptics " kaihsin Chung
5 siblings, 0 replies; 14+ messages in thread
From: bluez.test.bot @ 2026-04-09 20:20 UTC (permalink / raw)
To: linux-bluetooth, kaihsin.chung
[-- Attachment #1: Type: text/plain, Size: 6877 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=1078531
---Test result---
Test Summary:
CheckPatch PENDING 0.38 seconds
GitLint PENDING 0.26 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 25.61 seconds
CheckAllWarning PASS 28.40 seconds
CheckSparse PASS 27.03 seconds
BuildKernel32 PASS 24.83 seconds
TestRunnerSetup PASS 560.33 seconds
TestRunner_l2cap-tester PASS 27.83 seconds
TestRunner_iso-tester PASS 39.17 seconds
TestRunner_bnep-tester PASS 6.24 seconds
TestRunner_mgmt-tester FAIL 111.38 seconds
TestRunner_rfcomm-tester PASS 9.22 seconds
TestRunner_sco-tester FAIL 14.18 seconds
TestRunner_ioctl-tester PASS 10.20 seconds
TestRunner_mesh-tester FAIL 13.70 seconds
TestRunner_smp-tester PASS 8.72 seconds
TestRunner_userchan-tester PASS 6.60 seconds
TestRunner_6lowpan-tester FAIL 8.80 seconds
IncrementalBuild PENDING 0.26 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
Read Exp Feature - Success Failed 0.107 seconds
##############################
Test: TestRunner_sco-tester - FAIL
Desc: Run sco-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
7.0.0-rc2-gf5b83b75cf22 #1 Not tainted
------------------------------------------------------
kworker/u5:2/117 is trying to acquire lock:
ffff88800192e240 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_connect_cfm+0x358/0x8d0
but task is already holding lock:
ffff888002607220 (&conn->lock){+.+.}-{3:3}, at: sco_connect_cfm+0x22d/0x8d0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&conn->lock){+.+.}-{3:3}:
lock_acquire+0xf7/0x2c0
_raw_spin_lock+0x2a/0x40
sco_sock_connect+0x4d7/0x1280
__sys_connect+0x1a3/0x260
__x64_sys_connect+0x6e/0xb0
do_syscall_64+0xa0/0x570
entry_SYSCALL_64_after_hwframe+0x74/0x7c
-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:
check_prev_add+0xe9/0xc70
__lock_acquire+0x1457/0x1df0
lock_acquire+0xf7/0x2c0
lock_sock_nested+0x36/0xd0
sco_connect_cfm+0x358/0x8d0
hci_sync_conn_complete_evt+0x3d3/0x8e0
hci_event_packet+0x74f/0xb10
hci_rx_work+0x398/0xd00
process_scheduled_works+0xb16/0x1ac0
worker_thread+0x4ff/0xba0
kthread+0x368/0x490
ret_from_fork+0x498/0x7e0
ret_from_fork_asm+0x19/0x30
other info that might help us debug this:
...
BUG: sleeping function called from invalid context at net/core/sock.c:3782
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 117, name: kworker/u5:2
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
INFO: lockdep is turned off.
CPU: 0 UID: 0 PID: 117 Comm: kworker/u5:2 Not tainted 7.0.0-rc2-gf5b83b75cf22 #1 PREEMPT(lazy)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014
Workqueue: hci0 hci_rx_work
Call Trace:
<TASK>
dump_stack_lvl+0x49/0x60
__might_resched+0x2ea/0x500
lock_sock_nested+0x47/0xd0
? sco_connect_cfm+0x358/0x8d0
sco_connect_cfm+0x358/0x8d0
? hci_debugfs_create_conn+0x190/0x210
? __pfx_sco_connect_cfm+0x10/0x10
hci_sync_conn_complete_evt+0x3d3/0x8e0
hci_event_packet+0x74f/0xb10
? __pfx_hci_sync_conn_complete_evt+0x10/0x10
? __pfx_hci_event_packet+0x10/0x10
? mark_held_locks+0x49/0x80
? lockdep_hardirqs_on_prepare+0xd4/0x180
? _raw_spin_unlock_irqrestore+0x2c/0x50
hci_rx_work+0x398/0xd00
process_scheduled_works+0xb16/0x1ac0
? __pfx_process_scheduled_works+0x10/0x10
? lock_acquire+0xf7/0x2c0
? lock_is_held_type+0x9b/0x110
? __pfx_hci_rx_work+0x10/0x10
worker_thread+0x4ff/0xba0
? _raw_spin_unlock_irqrestore+0x2c/0x50
? __pfx_worker_thread+0x10/0x10
kthread+0x368/0x490
? _raw_spin_unlock_irq+0x23/0x40
? __pfx_kthread+0x10/0x10
ret_from_fork+0x498/0x7e0
? __pfx_ret_from_fork+0x10/0x10
? __switch_to+0x9e4/0xe50
? __switch_to_asm+0x32/0x60
...
Total: 30, Passed: 30 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.845 seconds
Mesh - Send cancel - 2 Timed out 1.995 seconds
##############################
Test: TestRunner_6lowpan-tester - FAIL
Desc: Run 6lowpan-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
7.0.0-rc2-gf5b83b75cf22 #1 Not tainted
------------------------------------------------------
kworker/0:1/11 is trying to acquire lock:
ffff888002777140 ((wq_completion)hci0#2){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x75/0x180
but task is already holding lock:
ffffffffb344d7a0 (rtnl_mutex){+.+.}-{4:4}, at: lowpan_unregister_netdev+0xd/0x30
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #4 (rtnl_mutex){+.+.}-{4:4}:
lock_acquire+0xf7/0x2c0
__mutex_lock+0x16b/0x1fc0
lowpan_register_netdev+0x11/0x30
chan_ready_cb+0x836/0xd00
l2cap_recv_frame+0x6a06/0x8920
l2cap_recv_acldata+0x790/0xdf0
hci_rx_work+0x500/0xd00
process_scheduled_works+0xb16/0x1ac0
worker_thread+0x4ff/0xba0
kthread+0x368/0x490
ret_from_fork+0x498/0x7e0
ret_from_fork_asm+0x19/0x30
-> #3 (&chan->lock#3/1){+.+.}-{4:4}:
lock_acquire+0xf7/0x2c0
__mutex_lock+0x16b/0x1fc0
l2cap_chan_connect+0x74e/0x1980
lowpan_control_write+0x523/0x660
full_proxy_write+0x10b/0x190
vfs_write+0x1c0/0xf60
ksys_write+0xf1/0x1d0
do_syscall_64+0xa0/0x570
entry_SYSCALL_64_after_hwframe+0x74/0x7c
-> #2 (&conn->lock){+.+.}-{4:4}:
...
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
https://github.com/bluez/bluetooth-next/pull/53/checks
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 14+ messages in thread* [PATCH v4] Bluetooth: Add Synaptics 4384 Chip Support
2026-04-08 8:32 [PATCH] Bluetooth: Add Synaptcis 4384 Chip Support kaihsin
` (4 preceding siblings ...)
2026-04-09 20:20 ` Bluetooth: Add Synaptcis " bluez.test.bot
@ 2026-05-13 2:20 ` kaihsin Chung
2026-05-13 4:40 ` [v4] " bluez.test.bot
5 siblings, 1 reply; 14+ messages in thread
From: kaihsin Chung @ 2026-05-13 2:20 UTC (permalink / raw)
To: linux-bluetooth; +Cc: marcel, luiz.von.dentz, linux-kernel, Kaihsin Chung
From: Kaihsin Chung <kaihsin.chung@synaptics.com>
Add BCM4384A0 and BCM4384B0 identifiers to the Broadcom Bluetooth
subversion table and add device tree matching for brcm,bcm4384-bt.
Signed-off-by: kaihsin Chung <kaihsin.chung@synaptics.com>
---
drivers/bluetooth/btbcm.c | 6 +++++-
drivers/bluetooth/hci_bcm.c | 1 +
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/bluetooth/btbcm.c b/drivers/bluetooth/btbcm.c
index f9a7c790d7e2..1164cca40324 100644
--- a/drivers/bluetooth/btbcm.c
+++ b/drivers/bluetooth/btbcm.c
@@ -31,6 +31,7 @@
#define BDADDR_BCM4334B0 (&(bdaddr_t) {{0x00, 0x00, 0x00, 0xb0, 0x34, 0x43}})
#define BDADDR_BCM4345C5 (&(bdaddr_t) {{0xac, 0x1f, 0x00, 0xc5, 0x45, 0x43}})
#define BDADDR_BCM43341B (&(bdaddr_t) {{0xac, 0x1f, 0x00, 0x1b, 0x34, 0x43}})
+#define BDADDR_BCM4384B0 (&(bdaddr_t) {{0x93, 0x76, 0x00, 0xb0, 0x84, 0x43}})
#define BCM_FW_NAME_LEN 64
#define BCM_FW_NAME_COUNT_MAX 4
@@ -130,7 +131,8 @@ int btbcm_check_bdaddr(struct hci_dev *hdev)
!bacmp(&bda->bdaddr, BDADDR_BCM4345C5) ||
!bacmp(&bda->bdaddr, BDADDR_BCM43430A0) ||
!bacmp(&bda->bdaddr, BDADDR_BCM43430A1) ||
- !bacmp(&bda->bdaddr, BDADDR_BCM43341B)) {
+ !bacmp(&bda->bdaddr, BDADDR_BCM43341B) ||
+ !bacmp(&bda->bdaddr, BDADDR_BCM4384B0)) {
/* Try falling back to BDADDR EFI variable */
if (btbcm_set_bdaddr_from_efi(hdev) != 0) {
bt_dev_info(hdev, "BCM: Using default device address (%pMR)",
@@ -515,6 +517,8 @@ static const struct bcm_subver_table bcm_uart_subver_table[] = {
{ 0x4106, "BCM4335A0" }, /* 002.001.006 */
{ 0x410c, "BCM43430B0" }, /* 002.001.012 */
{ 0x2119, "BCM4373A0" }, /* 001.001.025 */
+ { 0x2128, "BCM4384A0" },/* 001.001.040 */
+ { 0x4119, "BCM4384B0"},/* 002.001.025 */
{ }
};
diff --git a/drivers/bluetooth/hci_bcm.c b/drivers/bluetooth/hci_bcm.c
index 874d23089b39..783346a4a59b 100644
--- a/drivers/bluetooth/hci_bcm.c
+++ b/drivers/bluetooth/hci_bcm.c
@@ -1609,6 +1609,7 @@ static const struct of_device_id bcm_bluetooth_of_match[] = {
{ .compatible = "brcm,bcm4335a0" },
{ .compatible = "cypress,cyw4373a0-bt", .data = &cyw4373a0_device_data },
{ .compatible = "infineon,cyw55572-bt", .data = &cyw55572_device_data },
+ { .compatible = "brcm,bcm4384-bt" },
{ },
};
MODULE_DEVICE_TABLE(of, bcm_bluetooth_of_match);
--
2.43.0
^ permalink raw reply related [flat|nested] 14+ messages in thread* RE: [v4] Bluetooth: Add Synaptics 4384 Chip Support
2026-05-13 2:20 ` [PATCH v4] Bluetooth: Add Synaptics " kaihsin Chung
@ 2026-05-13 4:40 ` bluez.test.bot
2026-05-15 15:42 ` Luiz Augusto von Dentz
0 siblings, 1 reply; 14+ messages in thread
From: bluez.test.bot @ 2026-05-13 4:40 UTC (permalink / raw)
To: linux-bluetooth, kaihsin.chung
[-- Attachment #1: Type: text/plain, Size: 1846 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=1093859
---Test result---
Test Summary:
CheckPatch FAIL 1.05 seconds
GitLint PASS 0.33 seconds
SubjectPrefix PASS 0.35 seconds
BuildKernel PASS 25.97 seconds
CheckAllWarning PASS 29.42 seconds
CheckSparse PASS 27.85 seconds
BuildKernel32 PASS 25.96 seconds
TestRunnerSetup PASS 537.07 seconds
IncrementalBuild PASS 25.45 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v4] Bluetooth: Add Synaptics 4384 Chip Support
WARNING: DT compatible string "brcm,bcm4384-bt" appears un-documented -- check ./Documentation/devicetree/bindings/
#160: FILE: drivers/bluetooth/hci_bcm.c:1612:
+ { .compatible = "brcm,bcm4384-bt" },
WARNING: From:/Signed-off-by: email name mismatch: 'From: Kaihsin Chung <kaihsin.chung@synaptics.com>' != 'Signed-off-by: kaihsin Chung <kaihsin.chung@synaptics.com>'
total: 0 errors, 2 warnings, 31 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14570021.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
https://github.com/bluez/bluetooth-next/pull/180
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [v4] Bluetooth: Add Synaptics 4384 Chip Support
2026-05-13 4:40 ` [v4] " bluez.test.bot
@ 2026-05-15 15:42 ` Luiz Augusto von Dentz
0 siblings, 0 replies; 14+ messages in thread
From: Luiz Augusto von Dentz @ 2026-05-15 15:42 UTC (permalink / raw)
To: linux-bluetooth; +Cc: kaihsin.chung
Hi,
On Wed, May 13, 2026 at 12:40 AM <bluez.test.bot@gmail.com> wrote:
>
> 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=1093859
>
> ---Test result---
>
> Test Summary:
> CheckPatch FAIL 1.05 seconds
> GitLint PASS 0.33 seconds
> SubjectPrefix PASS 0.35 seconds
> BuildKernel PASS 25.97 seconds
> CheckAllWarning PASS 29.42 seconds
> CheckSparse PASS 27.85 seconds
> BuildKernel32 PASS 25.96 seconds
> TestRunnerSetup PASS 537.07 seconds
> IncrementalBuild PASS 25.45 seconds
>
> Details
> ##############################
> Test: CheckPatch - FAIL
> Desc: Run checkpatch.pl script
> Output:
> [v4] Bluetooth: Add Synaptics 4384 Chip Support
> WARNING: DT compatible string "brcm,bcm4384-bt" appears un-documented -- check ./Documentation/devicetree/bindings/
> #160: FILE: drivers/bluetooth/hci_bcm.c:1612:
> + { .compatible = "brcm,bcm4384-bt" },
Hmm, is this warning something we need to take into consideradion, or
perhaps the compatibility is string is really wrong since it doesn't
match any existing chip?
> WARNING: From:/Signed-off-by: email name mismatch: 'From: Kaihsin Chung <kaihsin.chung@synaptics.com>' != 'Signed-off-by: kaihsin Chung <kaihsin.chung@synaptics.com>'
>
> total: 0 errors, 2 warnings, 31 lines checked
>
> NOTE: For some of the reported defects, checkpatch may be able to
> mechanically convert to the typical style using --fix or --fix-inplace.
>
> /github/workspace/src/patch/14570021.patch has style problems, please review.
>
> NOTE: Ignored message types: UNKNOWN_COMMIT_ID
>
> NOTE: If any of the errors are false positives, please report
> them to the maintainer, see CHECKPATCH in MAINTAINERS.
>
>
>
>
> https://github.com/bluez/bluetooth-next/pull/180
>
> ---
> Regards,
> Linux Bluetooth
>
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 14+ messages in thread