linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeffrey Hugo <jhugo@codeaurora.org>
To: Loic Poulain <loic.poulain@linaro.org>,
	manivannan.sadhasivam@linaro.org, hemantk@codeaurora.org
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] bus: mhi: pm: Change mhi_pm_resume timeout value
Date: Fri, 5 Mar 2021 07:49:44 -0700	[thread overview]
Message-ID: <153fe801-3855-5aa3-8698-ac7fde697255@codeaurora.org> (raw)
In-Reply-To: <1614953347-10192-1-git-send-email-loic.poulain@linaro.org>

On 3/5/2021 7:09 AM, Loic Poulain wrote:
> mhi_cntrl->timeout_ms is set by the controller and indicates the
> maximum amount of time the controller device will take to be ready.
> In case of PCI modems, this value is quite high given modems can take
> up to 15 seconds from cold boot to be ready.
> 
> Reusing this value in mhi_pm_resume can cause huge resuming latency
> and delay the whole system resume (in case of system wide suspend/
> resume), leading to bad use experience.

I think this needs more explanation.  The timeout is a maximum value. 
You indicate that 2 seconds is more than enough for any MHI device to 
exit M3 (citation needed), but 15 seconds is too much?  The difference 
should only be apparent when the device doesn't transition in the timeout.

Put another way, this doesn't say why 15 seconds is bad, if every device 
only needs 2, given that wait_event_timeout() doesn't always wait for 
the entire timeout value if the event occurs earlier.

> 
> This change adjusts the resume timeout to a fixed 2s value, which is
> more than enough for any MHI device for exiting M3.
> 
> Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
> ---
>   drivers/bus/mhi/core/pm.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/bus/mhi/core/pm.c b/drivers/bus/mhi/core/pm.c
> index 0cd6445..e2d83a9 100644
> --- a/drivers/bus/mhi/core/pm.c
> +++ b/drivers/bus/mhi/core/pm.c
> @@ -17,6 +17,8 @@
>   #include <linux/wait.h>
>   #include "internal.h"
>   
> +#define MHI_PM_RESUME_TIMEOUT_MS 2000
> +
>   /*
>    * Not all MHI state transitions are synchronous. Transitions like Linkdown,
>    * SYS_ERR, and shutdown can happen anytime asynchronously. This function will
> @@ -942,7 +944,7 @@ int mhi_pm_resume(struct mhi_controller *mhi_cntrl)
>   	ret = wait_event_timeout(mhi_cntrl->state_event,
>   				 mhi_cntrl->dev_state == MHI_STATE_M0 ||
>   				 MHI_PM_IN_ERROR_STATE(mhi_cntrl->pm_state),
> -				 msecs_to_jiffies(mhi_cntrl->timeout_ms));
> +				 msecs_to_jiffies(MHI_PM_RESUME_TIMEOUT_MS));
>   
>   	if (!ret || MHI_PM_IN_ERROR_STATE(mhi_cntrl->pm_state)) {
>   		dev_err(dev,
> 


-- 
Jeffrey Hugo
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2021-03-05 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 14:09 [PATCH] bus: mhi: pm: Change mhi_pm_resume timeout value Loic Poulain
2021-03-05 14:49 ` Jeffrey Hugo [this message]
2021-03-05 15:08   ` Loic Poulain
2021-03-05 15:09     ` Jeffrey Hugo
2021-03-05 15:34       ` Loic Poulain
2021-03-05 16:16         ` Loic Poulain

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=153fe801-3855-5aa3-8698-ac7fde697255@codeaurora.org \
    --to=jhugo@codeaurora.org \
    --cc=hemantk@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=manivannan.sadhasivam@linaro.org \
    /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 NNTP newsgroup(s).