mbox series

[v5,0/4] Expand firmware-name property to load specific

Message ID 20241212150232.3823088-1-quic_chejiang@quicinc.com (mailing list archive)
Headers show
Series Expand firmware-name property to load specific | expand

Message

Cheng Jiang (IOE) Dec. 12, 2024, 3:02 p.m. UTC 
Expand the firmware-name property to specify the names of NVM and
rampatch firmware to load.

This update will support loading specific firmware (nvm and rampatch)
for certain chips, like the QCA6698 Bluetooth chip, which shares the
same IP core as the WCN6855 but has different RF components and RAM
sizes, requiring new firmware files.

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.

So In firmware-name, 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.bin", "QCA6698/hpbtfw21.tlv";
firmware-name = "QCA6698/hpnv21", "QCA6698/hpbtfw21.tlv";
firmware-name = "QCA6698/hpnv21.bin";

---
v5:
  1. Update the dt-bindings decription.
  2. Extract the have-suffix check code to a helper function.
  3. Merge three generate nvm name functions to a signle function.

v4:
  1. Split nvm and rampatch changes to 2 commits.
  2. Fix the dt_binding_check error.
  3. Change the qca_get_alt_nvm_path return type from int to bool.
  4. Fix the nvm name suffix check error when path has '.'.
  5. Optimize the nvm file name generation function.

v3:
  1. Expand firmware-name property to specify the nvm and rampatch to
  load.
  2. Change the driver to support two items in firmware-name and choose
  the NVM file according to board id if there is no extension in NVM
  file.
  3. Update the dts file to idendify the firmware for QCA6698.
---

Cheng Jiang (4):
  dt-bindings: net: bluetooth: qca: Expand firmware-name property
  Bluetooth: qca: Update firmware-name to support board specific nvm
  Bluetooth: qca: Expand firmware-name to load specific rampatch
  arm64: dts: qcom: sa8775p-ride: Add firmware-name in BT node

 .../net/bluetooth/qualcomm-bluetooth.yaml     |   5 +-
 arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi    |   1 +
 drivers/bluetooth/btqca.c                     | 194 ++++++++++++------
 drivers/bluetooth/btqca.h                     |   5 +-
 drivers/bluetooth/hci_qca.c                   |  22 +-
 5 files changed, 152 insertions(+), 75 deletions(-)


base-commit: 3e42dc9229c5950e84b1ed705f94ed75ed208228