From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Shuai Zhang <shuai.zhang@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,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/1] Bluetooth: btqca: Add WCN6855 firmware priority selection feature
Date: Fri, 14 Nov 2025 11:04:25 +0100 [thread overview]
Message-ID: <967d99e5-7cc1-4f8c-8a1b-21b1bd096cb9@molgen.mpg.de> (raw)
In-Reply-To: <20251114081751.3940541-2-shuai.zhang@oss.qualcomm.com>
Dear Shuai,
Thank you for your patch.
Am 14.11.25 um 09:17 schrieb Shuai Zhang:
> The prefix "wcn" corresponds to the WCN685x chip, while entries without
> the "wcn" prefix correspond to the QCA2066 chip. There are some feature
> differences between the two.
>
> However, 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.
Present tense: … is now corrected.
Maybe give one example of the firmware file.
How did you test this? Maybe paste some log lines before and after?
> Cc: stable@vger.kernel.org
> Fixes: 30209aeff75f ("Bluetooth: qca: Expand firmware-name to load specific rampatch")
> 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);
> + }
> +
> 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;
The diff logs good.
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
next prev parent reply other threads:[~2025-11-14 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 8:17 [PATCH v2 0/1] " Shuai Zhang
2025-11-14 8:17 ` [PATCH v2 1/1] " Shuai Zhang
2025-11-14 10:04 ` Paul Menzel [this message]
2025-11-14 10:41 ` Shuai Zhang
2025-11-14 10:45 ` Paul Menzel
2025-11-14 11:24 ` Shuai Zhang
2025-11-14 11:00 ` 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=967d99e5-7cc1-4f8c-8a1b-21b1bd096cb9@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=brgl@bgdev.pl \
--cc=cheng.jiang@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=shuai.zhang@oss.qualcomm.com \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®