Linux bluetooth development
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Yepuri Siddu <yepuri.siddu@oss.qualcomm.com>,
	Bartosz Golaszewski <brgl@kernel.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Balakrishna Godavarthi <quic_bgodavar@quicinc.com>,
	Rocky Liao <quic_rjliao@quicinc.com>,
	quic_mohamull@quicinc.com, quic_hbandi@quicinc.com,
	rahul.samana@oss.qualcomm.com, harshitha.reddy@oss.qualcomm.com,
	dishank.garg@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] Bluetooth: qca: add QCC2072 support
Date: Thu, 16 Jul 2026 11:35:22 +0200	[thread overview]
Message-ID: <7414f49f-b05f-4c6a-b416-a9c2004f5d98@oss.qualcomm.com> (raw)
In-Reply-To: <ca635179-eb3c-4a5f-882c-065deaca155c@oss.qualcomm.com>

On 7/2/26 12:11 PM, Yepuri Siddu wrote:
> 
> 
> On 6/1/2026 1:57 PM, Bartosz Golaszewski wrote:
>> On Fri, 29 May 2026 19:58:22 +0200, Yepuri Siddu
>> <yepuri.siddu@oss.qualcomm.com> said:
>>> QCC2072 is a BT/WiFi combo SoC that uses different firmware
>>> filenames and requires no external voltage regulators, so add
>>> it as a new SoC type.
>>>
>>> The chip supports the wideband speech and valid LE states
>>> capabilities. Its firmware is named using the "orn" prefix and
>>> follows the standard rom-version-based scheme:
>>>      - qca/ornbtfw<ver>.tlv
>>>      - qca/ornnv<ver>.bin
>>>
>>> These firmware files are already present in the linux-firmware
>>> repository.
>>>
>>> Signed-off-by: Yepuri Siddu <yepuri.siddu@oss.qualcomm.com>
>>> ---

[...]

>> Looking at the bindings: this chip cannot have an enable GPIO, so it probably
>> should have its own if branch that unconditionally sets power_ctrl_enabled to
>> false?
> 
> QCC2072 is an M.2 E-key chip. As M.2 Power Sequencing changes are being upstreamed, we will reupdate our existing patches to align with M.2 power sequencing approach.
> This includes aligning the bindings, DT and also BT driver changes.

FWIW with the M.2 patches applied, I can confirm this patch works
as-is (modulo merge conflict) for me, please resubmit soon.

Konrad

      reply	other threads:[~2026-07-16  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 17:58 [PATCH 2/4] Bluetooth: qca: add QCC2072 support Yepuri Siddu
2026-06-01  8:27 ` Bartosz Golaszewski
2026-07-02 10:11   ` Yepuri Siddu
2026-07-16  9:35     ` Konrad Dybcio [this message]

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=7414f49f-b05f-4c6a-b416-a9c2004f5d98@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=dishank.garg@oss.qualcomm.com \
    --cc=harshitha.reddy@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_bgodavar@quicinc.com \
    --cc=quic_hbandi@quicinc.com \
    --cc=quic_mohamull@quicinc.com \
    --cc=quic_rjliao@quicinc.com \
    --cc=rahul.samana@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=yepuri.siddu@oss.qualcomm.com \
    /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