From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Rahul Samana <rahul.samana@oss.qualcomm.com>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_hbandi@quicinc.com, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, quic_anubhavg@quicinc.com,
quic_mohamull@quicinc.com
Subject: Re: [PATCH 1/3] Bluetooth: qca: add QCC2072 support
Date: Thu, 23 Jul 2026 21:26:02 +0200 [thread overview]
Message-ID: <13a29b0d-709b-421f-99e4-02c41dc5ffb4@kernel.org> (raw)
In-Reply-To: <vxyc3lgvofl3yrodrzgxh7dtw3aegdcy4bwn7nf6eivhz3ld64@i7romsdep7e7>
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
next prev parent reply other threads:[~2026-07-23 19:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 12:31 [PATCH 0/3] Bluetooth: qca: enable QCC2072 on RB3 Gen 2 Industrial Mezz reworked for BT over UART Rahul Samana
2026-07-23 12:31 ` [PATCH 1/3] Bluetooth: qca: add QCC2072 support Rahul Samana
2026-07-23 12:48 ` sashiko-bot
2026-07-23 19:06 ` Dmitry Baryshkov
2026-07-23 19:26 ` Krzysztof Kozlowski [this message]
2026-07-23 19:19 ` Krzysztof Kozlowski
2026-07-23 12:31 ` [PATCH 2/3] arm64: dts: qcom: kodiak: mark PCIe root port as bridge Rahul Samana
2026-07-23 12:38 ` Konrad Dybcio
2026-07-23 19:07 ` Dmitry Baryshkov
2026-07-23 19:31 ` Krzysztof Kozlowski
2026-07-23 12:31 ` [PATCH 3/3] arm64: dts: qcom: rb3gen2: add Industrial BT UART overlay Rahul Samana
2026-07-23 12:49 ` sashiko-bot
2026-07-23 19:10 ` Dmitry Baryshkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13a29b0d-709b-421f-99e4-02c41dc5ffb4@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quic_anubhavg@quicinc.com \
--cc=quic_hbandi@quicinc.com \
--cc=quic_mohamull@quicinc.com \
--cc=rahul.samana@oss.qualcomm.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox