]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
Bluetooth: qca: Update firmware-name to support board specific nvm
authorCheng Jiang <quic_chejiang@quicinc.com>
Tue, 7 Jan 2025 09:26:49 +0000 (17:26 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 7 Mar 2025 15:56:30 +0000 (16:56 +0100)
commit55d69a2d2ab07f7207a7e05f4c4fc9a5b29bdd36
tree9107157d8142312afd6f88f0f41bdecd302f2c43
parente3c4cc00e111f206ea7b4d02329a70dff09700a6
Bluetooth: qca: Update firmware-name to support board specific nvm

[ Upstream commit a4c5a468c6329bde7dfd46bacff2cbf5f8a8152e ]

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";

Signed-off-by: Cheng Jiang <quic_chejiang@quicinc.com>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Stable-dep-of: a2fad248947d ("Bluetooth: qca: Fix poor RF performance for WCN6855")
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/bluetooth/btqca.c