From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Cheng Jiang <quic_chejiang@quicinc.com>,
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>
Cc: linux-bluetooth@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
quic_jiaymao@quicinc.com, quic_shuaz@quicinc.com,
quic_zijuhu@quicinc.com, quic_mohamull@quicinc.com
Subject: Re: [PATCH v5 2/4] Bluetooth: qca: Update firmware-name to support board specific nvm
Date: Fri, 13 Dec 2024 01:17:20 +0100 [thread overview]
Message-ID: <94eae703-ed9e-4f57-9786-99db7aaa07d1@oss.qualcomm.com> (raw)
In-Reply-To: <20241212150232.3823088-3-quic_chejiang@quicinc.com>
On 12.12.2024 4:02 PM, Cheng Jiang wrote:
> Different connectivity boards may be attached to the same platform. For
> example, QCA6698-based boards can support either a two-antenna or
> three-antenna solution, both of which work on the sa8775p-ride platform.
> Due to differences in connectivity boards and variations in RF
> performance from different foundries, different NVM configurations are
> used based on the board ID.
>
> Therefore, in the firmware-name property, if the NVM file has an
> extension, the NVM file will be used. Otherwise, the system will first
> try the .bNN (board ID) file, and if that fails, it will fall back to
> the .bin file.
>
> Possible configurations:
> firmware-name = "QCA6698/hpnv21";
> firmware-name = "QCA6698/hpnv21.bin";
I think we should agree on one and then do some magic to look up
the other variants.
>
> Signed-off-by: Cheng Jiang <quic_chejiang@quicinc.com>
> ---
> drivers/bluetooth/btqca.c | 112 ++++++++++++++++++++++++++++----------
> 1 file changed, 84 insertions(+), 28 deletions(-)
>
> diff --git a/drivers/bluetooth/btqca.c b/drivers/bluetooth/btqca.c
> index dfbbac922..4842f4335 100644
> --- a/drivers/bluetooth/btqca.c
> +++ b/drivers/bluetooth/btqca.c
> @@ -272,6 +272,38 @@ int qca_send_pre_shutdown_cmd(struct hci_dev *hdev)
> }
> EXPORT_SYMBOL_GPL(qca_send_pre_shutdown_cmd);
>
> +static bool qca_filename_has_extension(const char *filename)
> +{
> + const char *suffix;
> +
> + suffix = strrchr(filename, '.');
> + if (suffix && suffix != filename && *(suffix + 1) != '\0' && strchr(suffix, '/') == NULL)
> + return true;
> + else
> + return false;
How about:
const char *suffix = strrchr(filename, '.');
/* File extensions require a dot, but not as the last character */
if (!suffix || *(suffix + 1) == NULL)
return false;
/* Avoid matching directories with names that look like files with extensions */
return !(suffix, '/');
> + }
> + /* For nvm, if desired nvm file is not present and it's not the
> + * default nvm file(ends with .bin), try to load the default nvm.
nvm appears 4 times in two lines, how about:
/*
* If the board-specific file is missing, try loading the default
* one, unless that was attempted already
*/
But, even more importantly:
a) do we want to load the "incorrect" file?
b) why would we want to specify the .bin file if it's the default anyway?
> + */
> + else if (config->type == TLV_TYPE_NVM &&
> + qca_get_alt_nvm_file(config->fwname, sizeof(config->fwname))) {
> + bt_dev_info(hdev, "QCA Downloading %s", config->fwname);
> + ret = request_firmware(&fw, config->fwname, &hdev->dev);
> + if (ret) {
> + bt_dev_err(hdev, "QCA Failed to request file: %s (%d)",
> + config->fwname, ret);
> + return ret;
> + }
> } else {
> bt_dev_err(hdev, "QCA Failed to request file: %s (%d)",
> config->fwname, ret);
> @@ -700,34 +745,38 @@ static int qca_check_bdaddr(struct hci_dev *hdev, const struct qca_fw_config *co
> return 0;
> }
>
> -static void qca_generate_hsp_nvm_name(char *fwname, size_t max_size,
> +static void qca_get_nvm_name_by_board(char *fwname, size_t max_size,
> + const char *stem, enum qca_btsoc_type soc_type,
> struct qca_btsoc_version ver, u8 rom_ver, u16 bid)
> {
> const char *variant;
> + const char *prefix;
>
> - /* hsp gf chip */
> - if ((le32_to_cpu(ver.soc_id) & QCA_HSP_GF_SOC_MASK) == QCA_HSP_GF_SOC_ID)
> - variant = "g";
> - else
> - variant = "";
> + /* Set the defalut value to variant and prefixt */
typos: default, prefix
> + variant = "";
> + prefix = "b";
>
> - if (bid == 0x0)
> - snprintf(fwname, max_size, "qca/hpnv%02x%s.bin", rom_ver, variant);
> - else
> - snprintf(fwname, max_size, "qca/hpnv%02x%s.%x", rom_ver, variant, bid);
> -}
> + if (soc_type == QCA_QCA2066)
> + prefix = "";
>
> -static inline void qca_get_nvm_name_generic(struct qca_fw_config *cfg,
> - const char *stem, u8 rom_ver, u16 bid)
> -{
> - if (bid == 0x0)
> - snprintf(cfg->fwname, sizeof(cfg->fwname), "qca/%snv%02x.bin", stem, rom_ver);
> - else if (bid & 0xff00)
> - snprintf(cfg->fwname, sizeof(cfg->fwname),
> - "qca/%snv%02x.b%x", stem, rom_ver, bid);
> - else
> - snprintf(cfg->fwname, sizeof(cfg->fwname),
> - "qca/%snv%02x.b%02x", stem, rom_ver, bid);
> + if (soc_type == QCA_WCN6855 || soc_type == QCA_QCA2066) {
> + /* hsp gf chip */
This is a good opportunity to explain what that means
Konrad
next prev parent reply other threads:[~2024-12-13 0:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 15:02 [PATCH v5 0/4] Expand firmware-name property to load specific Cheng Jiang
2024-12-12 15:02 ` [PATCH v5 1/4] dt-bindings: net: bluetooth: qca: Expand firmware-name property Cheng Jiang
2024-12-12 15:17 ` Expand firmware-name property to load specific bluez.test.bot
2024-12-13 8:49 ` [PATCH v5 1/4] dt-bindings: net: bluetooth: qca: Expand firmware-name property Krzysztof Kozlowski
2024-12-12 15:02 ` [PATCH v5 2/4] Bluetooth: qca: Update firmware-name to support board specific nvm Cheng Jiang
2024-12-13 0:17 ` Konrad Dybcio [this message]
2024-12-13 7:05 ` Cheng Jiang (IOE)
2024-12-20 13:46 ` Konrad Dybcio
2024-12-23 2:47 ` Cheng Jiang (IOE)
2024-12-23 11:46 ` Konrad Dybcio
2024-12-24 8:29 ` Cheng Jiang (IOE)
2024-12-12 15:02 ` [PATCH v5 3/4] Bluetooth: qca: Expand firmware-name to load specific rampatch Cheng Jiang
2024-12-12 15:02 ` [PATCH v5 4/4] arm64: dts: qcom: sa8775p-ride: Add firmware-name in BT node Cheng Jiang
2024-12-13 8:51 ` Krzysztof Kozlowski
2024-12-16 6:51 ` Cheng Jiang (IOE)
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=94eae703-ed9e-4f57-9786-99db7aaa07d1@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@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_bgodavar@quicinc.com \
--cc=quic_chejiang@quicinc.com \
--cc=quic_jiaymao@quicinc.com \
--cc=quic_mohamull@quicinc.com \
--cc=quic_rjliao@quicinc.com \
--cc=quic_shuaz@quicinc.com \
--cc=quic_zijuhu@quicinc.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