From: Shuai Zhang <shuai.zhang@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-arm-msm@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, cheng.jiang@oss.qualcomm.com,
quic_chezhou@quicinc.com, wei.deng@oss.qualcomm.com,
jinwang.li@oss.qualcomm.com, mengshi.wu@oss.qualcomm.com
Subject: Re: [PATCH v5 2/2] Bluetooth: btqca: Add WCN6855 firmware priority selection feature
Date: Mon, 5 Jan 2026 11:36:10 +0800 [thread overview]
Message-ID: <4d9c38b2-d2c7-49a0-8034-e7874e000466@oss.qualcomm.com> (raw)
In-Reply-To: <wxfba3ldef52mwuhthyh76qd3ppmmhmhuzhck3yziju2iil2vy@6elo3tzkjdvq>
Dear
On 1/1/2026 1:23 AM, Dmitry Baryshkov wrote:
> On Wed, Dec 31, 2025 at 03:58:17PM +0800, Shuai Zhang wrote:
>> Historically, WCN685x and QCA2066 shared the same firmware files.
>> Now, changes are planned for the firmware that will make it incompatible
>> with QCA2066, so a new firmware name is required for WCN685x.
>>
>> Test Steps:
>> - Boot device
>> - Check the BTFW loading status via dmesg
>>
>> Sanity pass and Test Log:
>> QCA Downloading qca/wcnhpbftfw21.tlv
>> Direct firmware load for qca/wcnhpbftfw21.tlv failed with error -2
>> QCA Downloading qca/hpbftfw21.tlv
>>
>> Signed-off-by: Shuai Zhang <shuai.zhang@oss.qualcomm.com>
>> ---
>> drivers/bluetooth/btqca.c | 25 +++++++++++++++++++++----
>> 1 file changed, 21 insertions(+), 4 deletions(-)
>> @@ -936,8 +944,17 @@ int qca_uart_setup(struct hci_dev *hdev, uint8_t baudrate,
>>
>> err = qca_download_firmware(hdev, &config, soc_type, rom_ver);
>> if (err < 0) {
>> - bt_dev_err(hdev, "QCA Failed to download NVM (%d)", err);
>> - return err;
>> + if (!firmware_name && soc_type == QCA_WCN6855) {
> Same comment as for the first patch: move this one level up,
> incorporating err < 0 check.
Thank you for your suggestion, I will update it.
>
>> + qca_get_nvm_name_by_board(config.fwname, sizeof(config.fwname),
>> + "hpnv", soc_type, ver, rom_ver, boardid);
>> + err = qca_download_firmware(hdev, &config, soc_type, rom_ver);
>> + }
>> +
>> + if (err) {
>> + bt_dev_err(hdev, "QCA Failed to request file: %s (%d)",
>> + config.fwname, err);
>> + return err;
>> + }
>> }
>>
>> switch (soc_type) {
>> --
>> 2.34.1
>>
prev parent reply other threads:[~2026-01-05 3:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 7:58 [PATCH v5 0/2] Bluetooth: btqca: move WCN7850 WA and add WCN6855 firmware priority selection feature Shuai Zhang
2025-12-31 7:58 ` [PATCH v5 1/2] Bluetooth: btqca: move WCN7850 workaround to the caller Shuai Zhang
2025-12-31 8:38 ` Paul Menzel
2026-01-05 3:01 ` Shuai Zhang
2025-12-31 17:21 ` Dmitry Baryshkov
2025-12-31 7:58 ` [PATCH v5 2/2] Bluetooth: btqca: Add WCN6855 firmware priority selection feature Shuai Zhang
2025-12-31 17:23 ` Dmitry Baryshkov
2026-01-05 3:36 ` Shuai Zhang [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=4d9c38b2-d2c7-49a0-8034-e7874e000466@oss.qualcomm.com \
--to=shuai.zhang@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jinwang.li@oss.qualcomm.com \
--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=mengshi.wu@oss.qualcomm.com \
--cc=quic_chezhou@quicinc.com \
--cc=wei.deng@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