Hi Luiz,
On Sat, Nov 16, 2024 at 07:49:23AM -0800, Zijun Hu wrote:
For WCN6855, board ID specific NVM needs to be downloaded once board ID is available, but the default NVM is always downloaded currently, and the wrong NVM causes poor RF performance which effects user experience.
Fix by downloading board ID specific NVM if board ID is available.
Cc: Bjorn Andersson bjorande@quicinc.com Cc: Aiqun Yu (Maria) quic_aiquny@quicinc.com Cc: Cheng Jiang quic_chejiang@quicinc.com Cc: Johan Hovold johan@kernel.org Cc: Jens Glathe jens.glathe@oldschoolsolutions.biz Cc: Steev Klimaszewski steev@kali.org Cc: Paul Menzel pmenzel@molgen.mpg.de Fixes: 095327fede00 ("Bluetooth: hci_qca: Add support for QTI Bluetooth chip wcn6855") Cc: stable@vger.kernel.org # 6.4 Reviewed-by: Johan Hovold johan+linaro@kernel.org Tested-by: Johan Hovold johan+linaro@kernel.org Tested-by: Steev Klimaszewski steev@kali.org Tested-by: Jens Glathe jens.glathe@oldschoolsolutions.biz Signed-off-by: Zijun Hu quic_zijuhu@quicinc.com
I will help to backport it to LTS kernels ASAP once this commit is mainlined.
Changes in v2:
- Correct subject and commit message
- Temporarily add nvm fallback logic to speed up backport.
— Add fix/stable tags as suggested by Luiz and Johan
The board-specific NVM configuration files have now been included in the linux-firmware-20241210 release and are making their way into the distros (e.g. Arch Linux ARM and Fedora now ship them).
Could we get this merged for 6.13-rc (and backported) so that Lenovo ThinkPad X13s users can finally enjoy excellent Bluetooth range? :)
Johan