From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: insalata.fresca@gmail.com, jjohnson@kernel.org,
quic_rajkbhag@quicinc.com
Cc: ath12k@lists.infradead.org, linux-wireless@vger.kernel.org,
quic_bqiang@quicinc.com
Subject: Re: ath12k: QCN9274 hw2.0 single-band cards on IPQ9574 — firmware RDDM after WMI_INIT_CMD (WLAN.WBE.1.6-01243)
Date: Tue, 19 May 2026 08:50:47 -0700 [thread overview]
Message-ID: <f2ad69a2-35da-4611-9466-eda63c264c1f@oss.qualcomm.com> (raw)
In-Reply-To: <6a0b9e39.87c5160c.1d1e38.353c@mx.google.com>
On 5/18/2026 4:18 PM, insalata.fresca@gmail.com wrote:
> Fix B -- DMA ring capability parser must tolerate unknown module IDs:
>
> Without: "Invalid module id 3" -> "failed to parse tlv -22" -> WMI ready timeout
> Cause : WBE.1.6 sends capability entries for module_id 3 (and possibly
> others) the host enum does not know. ath12k_dp_get_ring_num()
> returns -EINVAL for unknown IDs, breaking TLV parsing entirely.
> Fix : warn-and-skip on unknown module_id instead of returning -EINVAL.
There is already a public patch for this issue:
https://patch.msgid.link/20260505172415.566328-3-nazar@mokrynskyi.com
I've pinged the development team to look at the other issues.
What would be best is if you could create a Bugzilla ticket for tracking.
https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath12k/bugreport.html
/jeff
next prev parent reply other threads:[~2026-05-19 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 23:18 ath12k: QCN9274 hw2.0 single-band cards on IPQ9574 — firmware RDDM after WMI_INIT_CMD (WLAN.WBE.1.6-01243) insalata.fresca
2026-05-19 15:50 ` Jeff Johnson [this message]
2026-05-20 5:05 ` Stefano Ursino
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=f2ad69a2-35da-4611-9466-eda63c264c1f@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=insalata.fresca@gmail.com \
--cc=jjohnson@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@quicinc.com \
--cc=quic_rajkbhag@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