* RE: Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial Mezz reworked for BT over UART
[not found] ` <20260723-rb3-industrial-bt-uart-v1-1-3c8e580c09d1@oss.qualcomm.com>
@ 2026-07-23 15:46 ` bluez.test.bot
2026-07-23 19:06 ` [PATCH 1/3] Bluetooth: qca: add QCC2072 support Dmitry Baryshkov
2026-07-23 19:19 ` Krzysztof Kozlowski
2 siblings, 0 replies; 7+ messages in thread
From: bluez.test.bot @ 2026-07-23 15:46 UTC (permalink / raw)
To: linux-bluetooth, rahul.samana
[-- Attachment #1: Type: text/plain, Size: 4766 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=1133207
---Test result---
Test Summary:
CheckPatch FAIL 3.78 seconds
VerifyFixes PASS 0.14 seconds
VerifySignedoff PASS 0.14 seconds
GitLint PASS 1.01 seconds
SubjectPrefix FAIL 0.46 seconds
BuildKernel PASS 27.03 seconds
CheckAllWarning PASS 30.93 seconds
CheckSparse PASS 28.48 seconds
BuildKernel32 PASS 26.47 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 505.18 seconds
TestRunner_l2cap-tester PASS 63.01 seconds
TestRunner_iso-tester PASS 86.12 seconds
TestRunner_bnep-tester PASS 19.37 seconds
TestRunner_mgmt-tester FAIL 222.76 seconds
TestRunner_rfcomm-tester PASS 25.78 seconds
TestRunner_sco-tester PASS 35.00 seconds
TestRunner_ioctl-tester PASS 26.77 seconds
TestRunner_mesh-tester FAIL 26.97 seconds
TestRunner_smp-tester PASS 23.95 seconds
TestRunner_userchan-tester PASS 20.89 seconds
TestRunner_6lowpan-tester PASS 24.22 seconds
IncrementalBuild PASS 28.40 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/3] Bluetooth: qca: add QCC2072 support
WARNING: DT compatible string "qcom,qcc2072-bt" appears un-documented -- check ./Documentation/devicetree/bindings/
#457: FILE: drivers/bluetooth/hci_qca.c:2811:
+ { .compatible = "qcom,qcc2072-bt", .data = &qca_soc_data_qcc2072},
total: 0 errors, 1 warnings, 240 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/14706139.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.
[2/3] arm64: dts: qcom: kodiak: mark PCIe root port as bridge
WARNING: DT compatible string vendor "pciclass" appears un-documented -- check ./Documentation/devicetree/bindings/vendor-prefixes.yaml
#188: FILE: arch/arm64/boot/dts/qcom/kodiak.dtsi:2299:
+ compatible = "pciclass,0604";
total: 0 errors, 1 warnings, 7 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/14706140.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.
[3/3] arm64: dts: qcom: rb3gen2: add Industrial BT UART overlay
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#203:
new file mode 100644
total: 0 errors, 1 warnings, 143 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/14706141.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.
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
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.256 seconds
##############################
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.435 seconds
Mesh - Send cancel - 2 Timed out 1.985 seconds
https://github.com/bluez/bluetooth-next/pull/482
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH 1/3] Bluetooth: qca: add QCC2072 support
[not found] ` <20260723-rb3-industrial-bt-uart-v1-1-3c8e580c09d1@oss.qualcomm.com>
2026-07-23 15:46 ` Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial Mezz reworked for BT over UART bluez.test.bot
@ 2026-07-23 19:06 ` Dmitry Baryshkov
2026-07-23 19:26 ` Krzysztof Kozlowski
2026-07-23 19:19 ` Krzysztof Kozlowski
2 siblings, 1 reply; 7+ messages in thread
From: Dmitry Baryshkov @ 2026-07-23 19:06 UTC (permalink / raw)
To: Rahul Samana
Cc: Luiz Augusto von Dentz, Krzysztof Kozlowski, Marcel Holtmann,
Bartosz Golaszewski, Conor Dooley, Rob Herring, Bjorn Andersson,
Konrad Dybcio, linux-bluetooth, linux-kernel, quic_hbandi,
devicetree, linux-arm-msm, quic_anubhavg, quic_mohamull
On Thu, Jul 23, 2026 at 06:01:07PM +0530, Rahul Samana wrote:
> Add QCC2072 as a supported Qualcomm Bluetooth controller.
>
> QCC2072 uses the ORN firmware and NVM naming scheme. Select the NVM file
> and BCS calibration file using the controller board ID when available,
> with fallback to the default files.
>
> Register the QCC2072 compatible with hci_qca and route it through the
> same UART setup, speed switching and power-control paths as recent
> Qualcomm Bluetooth controllers.
>
> Signed-off-by: Rahul Samana <rahul.samana@oss.qualcomm.com>
> ---
> drivers/bluetooth/btqca.c | 70 ++++++++++++++++++++++++++++++++++++++++++++-
> drivers/bluetooth/btqca.h | 2 ++
> drivers/bluetooth/hci_qca.c | 24 ++++++++++++++++
> 3 files changed, 95 insertions(+), 1 deletion(-)
I think you are a third engineer who submits a patch with this name and
with no mentions of the previous work. Are you working in parallel with
no idea what other team is doing, are you ignoring the previous work and
implementing it from scratch or are you picking up a patch made by
somebody else and killing the authorship / SoB tags?
--
With best wishes
Dmitry
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH 1/3] Bluetooth: qca: add QCC2072 support
2026-07-23 19:06 ` [PATCH 1/3] Bluetooth: qca: add QCC2072 support Dmitry Baryshkov
@ 2026-07-23 19:26 ` Krzysztof Kozlowski
0 siblings, 0 replies; 7+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-23 19:26 UTC (permalink / raw)
To: Dmitry Baryshkov, Rahul Samana
Cc: Luiz Augusto von Dentz, Krzysztof Kozlowski, Marcel Holtmann,
Bartosz Golaszewski, Conor Dooley, Rob Herring, Bjorn Andersson,
Konrad Dybcio, linux-bluetooth, linux-kernel, quic_hbandi,
devicetree, linux-arm-msm, quic_anubhavg, quic_mohamull
On 23/07/2026 21:06, Dmitry Baryshkov wrote:
> On Thu, Jul 23, 2026 at 06:01:07PM +0530, Rahul Samana wrote:
>> Add QCC2072 as a supported Qualcomm Bluetooth controller.
>>
>> QCC2072 uses the ORN firmware and NVM naming scheme. Select the NVM file
>> and BCS calibration file using the controller board ID when available,
>> with fallback to the default files.
>>
>> Register the QCC2072 compatible with hci_qca and route it through the
>> same UART setup, speed switching and power-control paths as recent
>> Qualcomm Bluetooth controllers.
>>
>> Signed-off-by: Rahul Samana <rahul.samana@oss.qualcomm.com>
>> ---
>> drivers/bluetooth/btqca.c | 70 ++++++++++++++++++++++++++++++++++++++++++++-
>> drivers/bluetooth/btqca.h | 2 ++
>> drivers/bluetooth/hci_qca.c | 24 ++++++++++++++++
>> 3 files changed, 95 insertions(+), 1 deletion(-)
>
> I think you are a third engineer who submits a patch with this name and
> with no mentions of the previous work. Are you working in parallel with
> no idea what other team is doing, are you ignoring the previous work and
> implementing it from scratch or are you picking up a patch made by
> somebody else and killing the authorship / SoB tags?
And the absolute mess in undocumented dependencies (thus undocumented
ABI which already got accepted by Bartosz [1]), referencing some
patchsets which are not clear to go thus eventually pushing undocumented
ABI again and patchset which cannot be merged.
Broken process.
[1]
https://lore.kernel.org/all/9cc5af16-d95e-4f10-8b4a-5e29c136079c@kernel.org/
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [PATCH 1/3] Bluetooth: qca: add QCC2072 support
[not found] ` <20260723-rb3-industrial-bt-uart-v1-1-3c8e580c09d1@oss.qualcomm.com>
2026-07-23 15:46 ` Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial Mezz reworked for BT over UART bluez.test.bot
2026-07-23 19:06 ` [PATCH 1/3] Bluetooth: qca: add QCC2072 support Dmitry Baryshkov
@ 2026-07-23 19:19 ` Krzysztof Kozlowski
2 siblings, 0 replies; 7+ messages in thread
From: Krzysztof Kozlowski @ 2026-07-23 19:19 UTC (permalink / raw)
To: Rahul Samana, Luiz Augusto von Dentz, Krzysztof Kozlowski,
Marcel Holtmann, Bartosz Golaszewski, Conor Dooley, Rob Herring,
Bjorn Andersson, Konrad Dybcio
Cc: linux-bluetooth, linux-kernel, quic_hbandi, devicetree,
linux-arm-msm, quic_anubhavg, quic_mohamull
On 23/07/2026 14:31, Rahul Samana wrote:
> Add QCC2072 as a supported Qualcomm Bluetooth controller.
>
> QCC2072 uses the ORN firmware and NVM naming scheme. Select the NVM file
> and BCS calibration file using the controller board ID when available,
> with fallback to the default files.
>
> Register the QCC2072 compatible with hci_qca and route it through the
> same UART setup, speed switching and power-control paths as recent
> Qualcomm Bluetooth controllers.
>
> Signed-off-by: Rahul Samana <rahul.samana@oss.qualcomm.com>
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 7+ messages in thread