[PATCH v1] linux-qcom-base-6.6: Add firmware-name in BT node for qcs615-ride

[PATCH v1] linux-qcom-base-6.6: Add firmware-name in BT node for qcs615-ride

[Jiayang Mao]

The qcs615-ride platform uses the QCA6698 Bluetooth chip. While the
QCA6698 shares the same IP core as the WCN6855, it has different RF
components and RAM sizes, requiring new firmware files. Use the
firmware-name property to specify the nvm and rampatch firmware to load.

This patch depends on below patch:
- WiFi/BT DTS
https://lore.kernel.org/all/20241203060318.1750927-1-quic_yuzha@quicinc.com/

Signed-off-by: Jiayang Mao <quic_jiaymao@quicinc.com>
---
 arch/arm64/boot/dts/qcom/qcs615-ride.dts | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/arch/arm64/boot/dts/qcom/qcs615-ride.dts b/arch/arm64/boot/dts/qcom/qcs615-ride.dts
index 5ba9dd5eec6c..03547fbd33bc 100644
--- a/arch/arm64/boot/dts/qcom/qcs615-ride.dts
+++ b/arch/arm64/boot/dts/qcom/qcs615-ride.dts
@@ -1,6 +1,6 @@
 // SPDX-License-Identifier: BSD-3-Clause
 /*
- * Copyright (c) 2024, Qualcomm Innovation Center, Inc. All rights reserved.
+ * Copyright (c) 2024-2025, Qualcomm Innovation Center, Inc. All rights reserved.
  */
 /dts-v1/;
 
@@ -611,6 +611,7 @@ &uart7 {
 
 	bluetooth {
 		compatible = "qcom,wcn6855-bt";
+		firmware-name = "QCA6698/hpnv21", "QCA6698/hpbtfw21.tlv";
 
 		vddrfacmn-supply = <&vreg_pmu_rfa_cmn>;
 		vddaon-supply = <&vreg_pmu_aon_0p59>;
-- 
2.25.1

Re: [PATCH v1] linux-qcom-base-6.6: Add firmware-name in BT node for qcs615-ride

[Krzysztof Kozlowski]

On 18/02/2025 08:42, Jiayang Mao wrote:
> The qcs615-ride platform uses the QCA6698 Bluetooth chip. While the
> QCA6698 shares the same IP core as the WCN6855, it has different RF
> components and RAM sizes, requiring new firmware files. Use the
> firmware-name property to specify the nvm and rampatch firmware to load.


NAK, we do not develop 6.6 kernel.

> This patch depends on below patch:
> - WiFi/BT DTS
> https://lore.kernel.org/all/20241203060318.1750927-1-quic_yuzha@quicinc.com/
Not relevant to git history. Read submitting patches and internal guideline.

Best regards,
Krzysztof