On 1/10/2024 11:14 PM, Baochen Qiang wrote: > Currently we do reset for each RDDM event from MHI, however there are > cases, see below log, that we get two or more consecutive events, and > it is pointless to do reset for the subsequent ones. What's more, it > makes reset process more likely to fail. > > [ 1502.115876] ath11k_pci 0000:04:00.0: boot notify status reason MHI_CB_EE_RDDM > [ 1502.115884] ath11k_pci 0000:04:00.0: firmware crashed: MHI_CB_EE_RDDM > [ 1502.224041] ath11k_pci 0000:04:00.0: boot notify status reason MHI_CB_EE_RDDM > [ 1502.224050] ath11k_pci 0000:04:00.0: firmware crashed: MHI_CB_EE_RDDM > > Add a check to avoid reset again and again. This is done by tracking previous > MHI status: if we receive a new RDDM event while the previous one is > also the same, we treat it as duplicate and ignore it, because normally > we should receive a MHI_CB_EE_MISSION_MODE event between them. > > Tested-on: WCN6855 hw2.1 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 > > Signed-off-by: Baochen Qiang <quic_bqiang@xxxxxxxxxxx> Acked-by: Jeff Johnson <quic_jjohnson@xxxxxxxxxxx>
