From: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
To: Slark Xiao <slark_xiao@163.com>,
mani@kernel.org, krishna.chundru@oss.qualcomm.com
Cc: loic.poulain@oss.qualcomm.com, val@packett.cool,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v3] bus: mhi: host: pci_generic: Update the default autosuspend_delay_ms as 5000ms
Date: Wed, 28 Oct 2026 15:32:43 -0600 [thread overview]
Message-ID: <a34090f0-1843-4e04-a3f0-a53a62b1c1fd@oss.qualcomm.com> (raw)
In-Reply-To: <20261021105434.29897-1-slark_xiao@163.com>
On 10/21/2026 4:54 AM, Slark Xiao wrote:
> For some MHI devices in some specific scenarios, the default value
> of autosuspend_delay_ms may not be enough to handle the last wake
> event, potentially leading to device timeout or link drop issues.
> This can lead to a runtime resume failure and a subsequent system
> error:
>
> [ 8749.089545] mhi mhi0: Resuming from non M3 state (SYS ERROR)
> [ 8749.089573] mhi-pci-generic 0000:73:00.0: failed to resume device: -22
> [ 8749.090218] mhi-pci-generic 0000:73:00.0: device recovery started
> ...
> [ 8752.940324] mhi-pci-generic 0000:73:00.0: reset failed
>
> Following Qualcomm's recommended settings from Windows and their
> suggestion during case discussions, update the default autosuspend
> delay to 5000ms for MHI devices.
>
> Fixes: d3800c1dce24 ("bus: mhi: pci_generic: Add support for runtime PM")
> Cc: stable@vger.kernel.org
> Signed-off-by: Slark Xiao <slark_xiao@163.com>
Reviewed-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
prev parent reply other threads:[~2026-10-28 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 10:54 Slark Xiao
2026-10-21 12:51 ` Loic Poulain
2026-10-28 21:32 ` Jeff Hugo [this message]
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=a34090f0-1843-4e04-a3f0-a53a62b1c1fd@oss.qualcomm.com \
--to=jeff.hugo@oss.qualcomm.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=slark_xiao@163.com \
--cc=stable@vger.kernel.org \
--cc=val@packett.cool \
/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
all inboxes | Powered by JetHome®