From: Johan Hovold <johan@kernel.org>
To: Zijun Hu <quic_zijuhu@quicinc.com>, Tim Jiang <quic_tjiang@quicinc.com>
Cc: Janaki Ramaiah Thota <quic_janathot@quicinc.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: QCA NVM file for the X13s (WCN6855)
Date: Thu, 2 May 2024 12:57:00 +0200 [thread overview]
Message-ID: <ZjNxfFJmCgIyq8J6@hovoldconsulting.com> (raw)
Hi Zijun and Tim,
I noticed that you have both submitted firmware and NVM files for
QCA2066 to linux-firmware. [1][2]
I'm working on Linux support for the Lenovo ThinkPad X13s (Windows on
Arm, Snapdragon), which has the related WCN6855 controller that uses the
same firmware (hpbtfw21.tlv).
The current Linux driver is using the generic NVM file (hpnv21.bin) for
WCN6855, but connectivity is quite bad and I only get 2-3 meters of
range.
Switching to the board-specific NVM configuration (hpnv21b.b8c) that
came with the Windows driver make all issues go away and the range is
really good, but I'm not sure if that file is fully compatible with the
firmware used by the Linux driver.
Could you help us submit an NVM configuration file for the controller
with board id 0x008c to linux-firmware?
Bluetooth: hci0: setting up wcn6855
Bluetooth: hci0: QCA Product ID :0x00000013
Bluetooth: hci0: QCA SOC Version :0x400c1211
Bluetooth: hci0: QCA ROM Version :0x00000201
Bluetooth: hci0: QCA Patch Version:0x000038e6
Bluetooth: hci0: QCA controller version 0x12110201
Bluetooth: hci0: QCA Downloading qca/hpbtfw21.tlv
Bluetooth: hci0: qca_read_fw_board_id: bid = 8c
Bluetooth: hci0: QCA Downloading qca/hpnv21.bin
It looks like the NVM files should be updated in lockstep with the
firmware so if you could include that board in any future firmware
updates too that would be really helpful.
Johan
[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/qca?id=2ba1beaae0c649ce8a50baecc8df9e81cd524e65
[2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/qca?id=598f5bd22361d7e92eebe8452d1f8013a1d35b9a
next reply other threads:[~2024-05-02 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 10:57 Johan Hovold [this message]
2024-05-02 12:56 ` quic_zijuhu
2024-05-02 13:25 ` Johan Hovold
2024-05-02 13:46 ` quic_zijuhu
2024-05-02 14:13 ` Johan Hovold
2024-11-14 6:57 ` quic_zijuhu
2024-11-14 8:27 ` Paul Menzel
2024-11-14 8:39 ` quic_zijuhu
2024-11-15 9:08 ` Johan Hovold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZjNxfFJmCgIyq8J6@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_janathot@quicinc.com \
--cc=quic_tjiang@quicinc.com \
--cc=quic_zijuhu@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®