[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <432f80c3-0f9a-133b-5447-a8e2cee5479e@quicinc.com>
Date: Tue, 8 Apr 2025 15:30:09 +0530
From: Vasanthakumar Thiagarajan <quic_vthiagar@...cinc.com>
To: Aditya Kumar Singh <aditya.kumar.singh@....qualcomm.com>,
Johannes Berg
<johannes@...solutions.net>,
Jeff Johnson <jjohnson@...nel.org>,
"Karthikeyan
Periyasamy" <quic_periyasa@...cinc.com>,
Kalle Valo <kvalo@...nel.org>, Harshitha Prem <quic_hprem@...cinc.com>
CC: Jeff Johnson <jeff.johnson@....qualcomm.com>,
<linux-wireless@...r.kernel.org>, <ath12k@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH ath-next v4 9/9] wifi: ath12k: reset MLO global memory
during recovery
On 4/8/2025 11:36 AM, Aditya Kumar Singh wrote:
> When operating with multiple devices grouped together, the firmware stores
> data related to the state machine of each partner device in the MLO global
> memory region. If the firmware crashes, it updates the state to 'crashed'.
> During recovery, this memory is shared with the firmware again, and upon
> detecting the 'crashed' state, it reasserts. This leads to a loop of
> firmware asserts and it never recovers.
>
> Hence to fix this issue, once all devices in the group have been asserted
> and powered down, reset the MLO global memory region.
>
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1
> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ-1
> Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
>
> Signed-off-by: Aditya Kumar Singh <aditya.kumar.singh@....qualcomm.com>
Reviewed-by: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@....qualcomm.com>
Powered by blists - more mailing lists