From: Kalle Valo <kvalo@kernel.org>
To: Balaji Pothunoori <quic_bpothuno@quicinc.com>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wifi: ath11k: Fix unexpected return buffer manager error for WCN6750/WCN6855
Date: Tue, 12 Nov 2024 12:17:27 +0200 [thread overview]
Message-ID: <87bjykwybs.fsf@kernel.org> (raw)
In-Reply-To: <20241030114625.2416942-1-quic_bpothuno@quicinc.com> (Balaji Pothunoori's message of "Wed, 30 Oct 2024 17:16:25 +0530")
Balaji Pothunoori <quic_bpothuno@quicinc.com> writes:
> The following error messages were encountered while parsing fragmented RX
> packets for WCN6750/WCN6855:
>
> ath11k 17a10040.wifi: invalid return buffer manager 4
>
> This issue arose due to a hardcoded check for HAL_RX_BUF_RBM_SW3_BM
> introduced in 'commit 71c748b5e01e ("ath11k: Fix unexpected return buffer
> manager error for QCA6390")'
>
> For WCN6750 and WCN6855, the return buffer manager ID should be
> HAL_RX_BUF_RBM_SW1_BM. The incorrect conditional check caused fragmented
> packets to be dropped, resulting in the above error log.
>
> Fix this by adding a check for HAL_RX_BUF_RBM_SW1_BM.
>
> Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.2.0.c2-00258-QCAMSLSWPL-1
> Tested-on: WCN6855 hw2.1 WLAN.HSP.1.1-04479-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1
>
> Fixes: 71c748b5e01e ("ath11k: Fix unexpected return buffer manager error for QCA6390")
> Signed-off-by: Balaji Pothunoori <quic_bpothuno@quicinc.com>
Acked-by: Kalle Valo <kvalo@kernel.org>
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-11-12 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 11:46 [PATCH] wifi: ath11k: Fix unexpected return buffer manager error for WCN6750/WCN6855 Balaji Pothunoori
2024-10-31 16:45 ` Jeff Johnson
2024-11-12 10:17 ` Kalle Valo [this message]
2024-11-13 1:01 ` Jeff Johnson
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=87bjykwybs.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bpothuno@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.