Hi, + ath11k list and Jeff On Tue, Feb 11, 2025 at 01:15:55PM +0500, Muhammad Usama Anjum wrote: > Hi, > > I've been digging in the MHI code to find the reason behind broken > resume from hibernation for MHI. The same resume function is used > for both resume from suspend and resume from hibernation. The resume > from suspend works fine because at resume time the state of MHI is > MHI_STATE_M3. On the other hand, the state is MHI_STATE_RESET when > we resume from hibernation. > > It seems resume from MHI_STATE_RESET state isn't correctly supported. > The channel state is MHI_CH_STATE_ENABLED at this point. We get error > while switching channel state from MHI_CH_STATE_ENABLE to > MHI_CH_STATE_RUNNING. Hence, channel state change fails and later mhi > resume fails as well. > > I've put some debug prints to understand the issue. These may be > helpful: > > [ 669.032683] mhi_update_channel_state: switch to MHI_CH_STATE_TYPE_START[2] channel state not possible cuzof channel current state[1]. mhi state: [0] Return -EINVAL > [ 669.032685] mhi_prepare_channel: mhi_update_channel_state to MHI_CH_STATE_TYPE_START[2] returned -22 > [ 669.032693] qcom_mhi_qrtr mhi0_IPCR: failed to prepare for autoqueue transfer -22 > Thanks for the report! Could you please enable the MHI and ath11k debug logs and share the full dmesg to help us understand the issue better? > This same error has been reported on some fix patches [1] [2]. Are there > any patches which I should test? > > Is officially hibernation use case supported at all? > Yes. The hibernation support was tested with x86 host machine for both MHI modems and WLAN chipsets (especially ath11k devices). > In my view, this path may not have gotten tested and can be fixed easily > as we need to perform, more or less the same steps which were performed > at init time. But I've not found much documentation around MHI protocol > and its state machine, how is mhi state related to mhi channels support. > During hibernation, the power to the device could be lost. But it should be handled by the ath11k driver. Maybe the debug logs could help us know what is going wrong. - Mani -- மணிவண்ணன் சதாசிவம்
