From: Shuai Zhang <shuai.zhang@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
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
Subject: Re: [PATCH v3 1/1] Bluetooth: btqca: Add WCN6855 firmware priority selection feature
Date: Tue, 16 Dec 2025 20:54:45 +0800 [thread overview]
Message-ID: <cee7d849-54ca-486b-b168-086e44f1762f@oss.qualcomm.com> (raw)
In-Reply-To: <mtp3qxngbnlpzk2cdp45ndtecab2h56ocwm6cp5ia7butra55a@bevidj6vdwzj>
Hi Dmitry
On 11/19/2025 3:59 PM, Dmitry Baryshkov wrote:
> On Mon, Nov 17, 2025 at 10:16:45AM +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 | 22 ++++++++++++++++++++--
>> 1 file changed, 20 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/bluetooth/btqca.c b/drivers/bluetooth/btqca.c
>> index 7c958d606..8e0004ef7 100644
>> --- a/drivers/bluetooth/btqca.c
>> +++ b/drivers/bluetooth/btqca.c
>> @@ -847,8 +847,12 @@ int qca_uart_setup(struct hci_dev *hdev, uint8_t baudrate,
>> "qca/msbtfw%02x.mbn", rom_ver);
>> break;
>> case QCA_WCN6855:
>> + /* Due to historical reasons, WCN685x chip has been using firmware
>> + * without the "wcn" prefix. The mapping between the chip and its
>> + * corresponding firmware has now been corrected.
>> + */
>> snprintf(config.fwname, sizeof(config.fwname),
>> - "qca/hpbtfw%02x.tlv", rom_ver);
>> + "qca/wcnhpbtfw%02x.tlv", rom_ver);
>> break;
>> case QCA_WCN7850:
>> snprintf(config.fwname, sizeof(config.fwname),
>> @@ -861,6 +865,13 @@ int qca_uart_setup(struct hci_dev *hdev, uint8_t baudrate,
>> }
>>
>> err = qca_download_firmware(hdev, &config, soc_type, rom_ver);
>> +
>> + if (!rampatch_name && err < 0 && soc_type == QCA_WCN6855) {
>> + snprintf(config.fwname, sizeof(config.fwname),
>> + "qca/hpbtfw%02x.tlv", rom_ver);
>> + err = qca_download_firmware(hdev, &config, soc_type, rom_ver);
>> + }
> Is there a reason for ignoring how it was done already for other cases when
> we need a similar fallback? Please extend the existing code (or rewrite
> it) instead of adding a similar hook at a completely different place.
Sorry, I missed this email. I will resubmit the new changes using the
existing callback mechanism.
>> +
>> if (err < 0) {
>> bt_dev_err(hdev, "QCA Failed to download patch (%d)", err);
>> return err;
>> @@ -923,7 +934,7 @@ int qca_uart_setup(struct hci_dev *hdev, uint8_t baudrate,
>> case QCA_WCN6855:
>> qca_read_fw_board_id(hdev, &boardid);
>> qca_get_nvm_name_by_board(config.fwname, sizeof(config.fwname),
>> - "hpnv", soc_type, ver, rom_ver, boardid);
>> + "wcnhpnv", soc_type, ver, rom_ver, boardid);
>> break;
>> case QCA_WCN7850:
>> qca_get_nvm_name_by_board(config.fwname, sizeof(config.fwname),
>> @@ -936,6 +947,13 @@ int qca_uart_setup(struct hci_dev *hdev, uint8_t baudrate,
>> }
>>
>> err = qca_download_firmware(hdev, &config, soc_type, rom_ver);
>> +
>> + if (!firmware_name && err < 0 && soc_type == QCA_WCN6855) {
>> + 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 < 0) {
>> bt_dev_err(hdev, "QCA Failed to download NVM (%d)", err);
>> return err;
>> --
>> 2.34.1
Thanks,
Shuai
next prev parent reply other threads:[~2025-12-16 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 2:16 [PATCH v3 0/1] Bluetooth: btqca: Add WCN6855 firmware priority selection feature Shuai Zhang
2025-11-17 2:16 ` [PATCH v3 1/1] " Shuai Zhang
2025-11-18 13:44 ` Shuai Zhang
2025-11-18 14:04 ` Konrad Dybcio
2025-11-19 7:59 ` Dmitry Baryshkov
2025-12-16 12:54 ` Shuai Zhang [this message]
2025-12-19 9:19 ` Shuai Zhang
2025-12-21 15:21 ` Dmitry Baryshkov
2025-12-23 2:03 ` Shuai Zhang
2025-12-24 4:23 ` Dmitry Baryshkov
2025-12-24 6:54 ` Shuai Zhang
2025-12-24 9:39 ` Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2025-11-17 2:14 [PATCH v3 0/1] " Shuai Zhang
2025-11-17 2:14 ` [PATCH v3 1/1] " Shuai Zhang
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=cee7d849-54ca-486b-b168-086e44f1762f@oss.qualcomm.com \
--to=shuai.zhang@oss.qualcomm.com \
--cc=brgl@bgdev.pl \
--cc=cheng.jiang@oss.qualcomm.com \
--cc=dmitry.baryshkov@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=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