Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rahul Samana <rahul.samana@oss.qualcomm.com>,
	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>
Cc: 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:19:38 +0200	[thread overview]
Message-ID: <591cea7a-0892-42c7-aa38-51a90cd2c450@kernel.org> (raw)
In-Reply-To: <20260723-rb3-industrial-bt-uart-v1-1-3c8e580c09d1@oss.qualcomm.com>

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

  parent reply	other threads:[~2026-07-23 19:19 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
2026-07-23 19:19   ` Krzysztof Kozlowski [this message]
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=591cea7a-0892-42c7-aa38-51a90cd2c450@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=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