[PATCH ath-next v3 0/2] wifi: ath12k: accept what newer QCN9274 firmware requests at boot

Rameshkumar Sundaram rameshkumar.sundaram at oss.qualcomm.com
Mon Nov 9 23:36:44 PST 2026


On 11/10/2026 5:51 AM, Goran Sustek wrote:
> QCN9274 firmware WLAN.WBE.1.6-01243 requests two things at boot that
> ath12k does not implement: a target memory segment of type 0xa (AFC)
> and direct buffer rings for module IDs 2 and 3. Neither is needed for
> operation. Today the first gets a wrong answer and the second aborts
> the parse of the service ready ext event.
> 
> Patch 1 answers every unsupported memory type with size 0. Patch 2
> skips unknown ring module IDs instead of failing the parse. Both keep
> a warning, so the gap between firmware and driver stays visible.
> 
> v3:
> - 1/2: clear the size in the default case, no AFC case; keep the
>    warning; describe only the response change (Rameshkumar Sundaram).
> - 2/2: warn for a skipped entry instead of a debug message.
> - Rebased on ath-next.
> 
> v2:
> - 1/2: do not allocate the region, answer with size 0 (Rameshkumar
>    Sundaram); former 3/3 dropped.
> - 2/2: commit message and comment reworded.
> 
> v2: https://lore.kernel.org/r/20261102200235.48973-1-gsustek@gmail.com
> v1: https://lore.kernel.org/r/20261030220836.14164-1-gsustek@gmail.com
> 
> Goran Sustek (2):
>    wifi: ath12k: report size 0 for unsupported target memory types
>    wifi: ath12k: skip unknown direct buffer ring module IDs
> 
>   drivers/net/wireless/ath/ath12k/qmi.c |  1 +
>   drivers/net/wireless/ath/ath12k/wmi.c | 43 +++++++++++++++++----------
>   2 files changed, 29 insertions(+), 15 deletions(-)
> 
> 
> base-commit: d0fbb39d65dc9dcb4175fa6b23e473dec3670f4d

Reviewed-by: Rameshkumar Sundaram <rameshkumar.sundaram at oss.qualcomm.com>



More information about the ath12k mailing list