| Message ID | 20241205102213.1281865-4-quic_chejiang@quicinc.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | Expand firmware-name property to load specific | expand |
On Thu, Dec 05, 2024 at 06:22:13PM +0800, Cheng Jiang wrote: > The sa8775p-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. > > Signed-off-by: Cheng Jiang <quic_chejiang@quicinc.com> > --- > arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi > index 3fc62e123..e7fe53d95 100644 > --- a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi > +++ b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi > @@ -857,6 +857,7 @@ &uart17 { > > bluetooth { > compatible = "qcom,wcn6855-bt"; > + firmware-name = "QCA6698/hpnv21", "QCA6698/hpbtfw21.tlv"; And the rampatch is not going to be board-specific? > > vddrfacmn-supply = <&vreg_pmu_rfa_cmn>; > vddaon-supply = <&vreg_pmu_aon_0p59>; > -- > 2.25.1 >
Hi Dmitry, On 12/5/2024 8:13 PM, Dmitry Baryshkov wrote: > On Thu, Dec 05, 2024 at 06:22:13PM +0800, Cheng Jiang wrote: >> The sa8775p-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. >> >> Signed-off-by: Cheng Jiang <quic_chejiang@quicinc.com> >> --- >> arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi >> index 3fc62e123..e7fe53d95 100644 >> --- a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi >> +++ b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi >> @@ -857,6 +857,7 @@ &uart17 { >> >> bluetooth { >> compatible = "qcom,wcn6855-bt"; >> + firmware-name = "QCA6698/hpnv21", "QCA6698/hpbtfw21.tlv"; > > And the rampatch is not going to be board-specific? > Yes, rampatch is chip-specific. >> >> vddrfacmn-supply = <&vreg_pmu_rfa_cmn>; >> vddaon-supply = <&vreg_pmu_aon_0p59>; >> -- >> 2.25.1 >> >
diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi index 3fc62e123..e7fe53d95 100644 --- a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi +++ b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi @@ -857,6 +857,7 @@ &uart17 { bluetooth { compatible = "qcom,wcn6855-bt"; + firmware-name = "QCA6698/hpnv21", "QCA6698/hpbtfw21.tlv"; vddrfacmn-supply = <&vreg_pmu_rfa_cmn>; vddaon-supply = <&vreg_pmu_aon_0p59>;
The sa8775p-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. Signed-off-by: Cheng Jiang <quic_chejiang@quicinc.com> --- arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi | 1 + 1 file changed, 1 insertion(+)