From: Alexandru Gagniuc <mr.nuke.me@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jjohnson@kernel.org, ath11k@lists.infradead.org
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexandru Gagniuc <mr.nuke.me@gmail.com>
Subject: [PATCH v2 0/2] ath11k: support IPQ9574
Date: Thu, 8 Jan 2026 22:44:52 -0600 [thread overview]
Message-ID: <20260109044457.3074510-1-mr.nuke.me@gmail.com> (raw)
This is my attempt to make ath11k work on IPQ9574. IPQ9574 is intended
for wifi-7 devices, so it seems the exception rather than the rule to
pair it with a wifi-6 chip. That's exactly what my Archer BE550 does.
This consists of a wifi-6 (QCN5024) chip connected via PCIe to the
SoC, but exposed to the OS via AHB. The Q6 firmware [4] requires
remoteproc support introduced in a separate series [3]. The QMI
firmware interface is very similar to IPQ6018, such that almost no
new code is needed.
I am not including the wifi@c000000 devicetree node in this series, as
it depends on nodes from the remoteproc series [3].
I have been successfully doogfooding this for a few of weeks in AP mode.
There dependencies to this series. [2] is a compile-time dependency,
whereas [1] and [3] are needed for full functionality. I was adivsed to
leave [1] and [2] as separate patches and not add them to this series.
`
[1] https://lore.kernel.org/ath11k/20251206175829.2573256-1-mr.nuke.me@gmail.com/
[2] https://lore.kernel.org/ath11k/20251228151408.2116108-1-mr.nuke.me@gmail.com/
[3] https://lore.kernel.org/linux-remoteproc/20260109043352.3072933-1-mr.nuke.me@gmail.com/
[4] https://github.com/quic/upstream-wifi-fw
Changes since v1:
- place compatible strings after instead of before ipq8074
Alexandru Gagniuc (2):
dt: bindings: net: ath11k: add IPQ9574 compatible
wifi: ath11k: support ipq9574
.../bindings/net/wireless/qcom,ath11k.yaml | 3 +
drivers/net/wireless/ath/ath11k/ahb.c | 4 +
drivers/net/wireless/ath/ath11k/core.c | 82 +++++++++++++++++++
drivers/net/wireless/ath/ath11k/core.h | 1 +
drivers/net/wireless/ath/ath11k/hw.c | 51 ++++++++++++
drivers/net/wireless/ath/ath11k/hw.h | 1 +
6 files changed, 142 insertions(+)
--
2.45.1
next reply other threads:[~2026-01-09 4:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 4:44 Alexandru Gagniuc [this message]
2026-01-09 4:44 ` [PATCH v2 1/2] dt: bindings: net: ath11k: add IPQ9574 compatible Alexandru Gagniuc
2026-01-09 8:45 ` Krzysztof Kozlowski
2026-01-09 4:44 ` [PATCH v2 2/2] wifi: ath11k: support ipq9574 Alexandru Gagniuc
2026-01-29 11:17 ` [PATCH v2 0/2] ath11k: support IPQ9574 Vasanthakumar Thiagarajan
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=20260109044457.3074510-1-mr.nuke.me@gmail.com \
--to=mr.nuke.me@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=robh@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