]> 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>
Thu, 27 Feb 2025 12:30:14 +0000 (04:30 -0800)
commit065215ef00f1e5773dcb0a5de4203aa6f00a7496
tree7dd2183b693c887179476f7d0092c190e55bdb81
parenta81171bb2b78044df11acc19233574ebf277aef9
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