From: Baochen Qiang <quic_bqiang@quicinc.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <mhi@lists.linux.dev>
Subject: Re: [PATCH v2 2/3] net: qrtr: support suspend/hibernation
Date: Tue, 27 Feb 2024 18:02:01 +0800 [thread overview]
Message-ID: <bb25f9cb-720e-4b53-950c-41eddc19da59@quicinc.com> (raw)
In-Reply-To: <20240227095602.GK2587@thinkpad>
On 2/27/2024 5:56 PM, Manivannan Sadhasivam wrote:
> On Tue, Feb 27, 2024 at 04:39:41PM +0800, Baochen Qiang wrote:
>>
>>
>> On 2/27/2024 3:15 PM, Manivannan Sadhasivam wrote:
>>> On Tue, Feb 27, 2024 at 02:36:12PM +0800, Baochen Qiang wrote:
>>>> MHI devices may not be destroyed during suspend/hibernation, so need
>>>> to unprepare/prepare MHI channels throughout the transition, this is
>>>> done by adding suspend/resume callbacks.
>>>>
>>>> The suspend callback is called in the late suspend stage, this means
>>>> MHI channels are still alive at suspend stage, and that makes it
>>>> possible for an MHI controller driver to communicate with others over
>>>> those channels at suspend stage. While the resume callback is called
>>>> in the early resume stage, for a similar reason.
>>>>
>>>> Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30
>>>>
>>>> Signed-off-by: Baochen Qiang <quic_bqiang@quicinc.com>
>>>
>>> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>>>
>>> Could you please confirm if this patch can be applied separately and won't cause
>>> regression?
>> Just searched the kernel and found another two drivers using IPCR channels,
>> one is pci_epf_mhi_driver in drivers/pci/endpoint/functions/pci-epf-mhi.c
>> and the other is mhi_pci_driver in drivers/bus/mhi/host/pci_generic.c.
>>
>> For pci_epf_mhi_driver, this is not impacted because the devices for those
>> channels are attached to mhi_ep_bus_type while QRTR MHI driver attached to
>> mhi_bus_type.
>>
>> For mhi_pci_driver, I am afraid there would be regressions caused by this
>> patch. The regression is because when system suspends, mhi_pci_suspend() is
>> called and then qcom_mhi_qrtr_pm_suspend_late() called, however the latter
>> would fail because MHI is moved to M3 state by call mhi_pm_suspend() in
>> mhi_pci_suspend(). To address this, there might be two options: the first is
>> to move mhi_pci_suspend() to a late suspend stage which would be called
>> after qcom_mhi_qrtr_pm_suspend_late(). and the second is to avoid whole QRTR
>> suspend operation in such cases. I prefer the second one, because if MHI is
>> going to suspend, instead of power down, it is pointless to unprepare MHI
>> channels and re-prepare them after resume back. We can achieve this purpose
>> by adding a status_cb() to QRTR MHI driver which would be called when MHI
>> goes to low power mode. And then QRTR MHI driver could decide not to
>> suspend/resume if low power mode is notified.
>>
>> Your thoughts?
>>
>
> I'd rather query the MHI state of the device in suspend/resume callback using
> mhi_get_mhi_state(mhi_dev->mhi_cntrl) and if the device is found to be in M3
> (suspend) state, then I'd skip prepare/unprepare part.
>
> Because this makes it clear that, if the device is in suspend state, then no
> need for the client drivers to unprepare/prepare the channels.
>
Sounds reasonable, will do accordingly in v3.
> - Mani
>
next prev parent reply other threads:[~2024-02-27 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 6:36 [PATCH v2 0/3] wifi: ath11k: hibernation support Baochen Qiang
2024-02-27 6:36 ` [PATCH v2 1/3] bus: mhi: host: add mhi_power_down_keep_dev() Baochen Qiang
2024-02-27 7:12 ` Manivannan Sadhasivam
2024-02-27 6:36 ` [PATCH v2 2/3] net: qrtr: support suspend/hibernation Baochen Qiang
2024-02-27 7:15 ` Manivannan Sadhasivam
2024-02-27 8:39 ` Baochen Qiang
2024-02-27 9:56 ` Manivannan Sadhasivam
2024-02-27 10:02 ` Baochen Qiang [this message]
2024-02-27 6:36 ` [PATCH v2 3/3] wifi: ath11k: support hibernation Baochen Qiang
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=bb25f9cb-720e-4b53-950c-41eddc19da59@quicinc.com \
--to=quic_bqiang@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).