From: Hongcheng Zhang <hongcheng.zhang@oss.qualcomm.com>
To: Jeff Johnson <jjohnson@kernel.org>,
linux-wireless@vger.kernel.org (open list:QUALCOMM ATHEROS
ATH11K WIRELESS DRIVER),
ath11k@lists.infradead.org (open list:QUALCOMM ATHEROS ATH11K
WIRELESS DRIVER), linux-kernel@vger.kernel.org (open list)
Cc: Hongcheng Zhang <hongcheng.zhang@oss.qualcomm.com>
Subject: [PATCH ath-next v1] wifi: ath11k: add usecase firmware entry for QCA2066 hw2.1
Date: Fri, 6 Nov 2026 07:38:08 +0530 [thread overview]
Message-ID: <20261106020809.3580396-1-hongcheng.zhang@oss.qualcomm.com> (raw)
The Monaco Monza platform (QCA2066 hw2.1) requires a usecase-specific
firmware variant located under the nfa725 subdirectory.
Add a new entry for "arduino,monza" compatible string to ensure that
the correct usecase firmware (nfa725) is selected.
Tested-on: QCA2066 hw2.1 PCI WLAN.HSP.1.1.c6-00302-QCAHSPSWPL_V1_V2_SILICONZ_LITE-1
Signed-off-by: Hongcheng Zhang <hongcheng.zhang@oss.qualcomm.com>
---
drivers/net/wireless/ath/ath11k/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ath11k/core.c b/drivers/net/wireless/ath/ath11k/core.c
index 766ae27306f4..b58dce133244 100644
--- a/drivers/net/wireless/ath/ath11k/core.c
+++ b/drivers/net/wireless/ath/ath11k/core.c
@@ -1049,6 +1049,7 @@ static const struct __ath11k_core_usecase_firmware_table {
const char *compatible;
const char *firmware_name;
} ath11k_core_usecase_firmware_table[] = {
+ { ATH11K_HW_QCA2066_HW21, "arduino,monza", "nfa725"},
{ ATH11K_HW_WCN6855_HW21, "qcom,hamoa-iot-evk", "nfa765"},
{ ATH11K_HW_WCN6855_HW21, "qcom,lemans-evk", "nfa765"},
{ ATH11K_HW_WCN6855_HW21, "qcom,monaco-evk", "nfa765"},
base-commit: 5c8eab13e391aaabd5a1ad58f3ee4bb10ce7573e
--
2.34.1
next reply other threads:[~2026-11-06 2:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 2:08 Hongcheng Zhang [this message]
2026-11-06 2:37 ` Baochen Qiang
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=20261106020809.3580396-1-hongcheng.zhang@oss.qualcomm.com \
--to=hongcheng.zhang@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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®