From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Roy Luo <royluo@google.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"badhri@google.com" <badhri@google.com>,
"frank.wang@rock-chips.com" <frank.wang@rock-chips.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v1] usb: dwc3: re-enable runtime PM after failed resume
Date: Sat, 7 Sep 2024 00:58:35 +0000 [thread overview]
Message-ID: <20240907005829.ldaspnspaegq5m4t@synopsys.com> (raw)
In-Reply-To: <20240906005803.1824339-1-royluo@google.com>
On Fri, Sep 06, 2024, Roy Luo wrote:
> When dwc3_resume_common() returns an error, runtime pm is left in
> disabled state in dwc3_resume(). The next dwc3_suspend_common()
What issue did you see when dwc3_suspend_common is not skipped?
BR,
Thinh
> should be skipped as the device is already in suspended state but
> it's not because power.disable_depth is non-zero.
> Ensures runtime PM is always re-enabled even after failed resume
> attempts.
>
> Fixes: 68c26fe58182 ("usb: dwc3: set pm runtime active before resume common")
> Cc: stable@vger.kernel.org
> Signed-off-by: Roy Luo <royluo@google.com>
> ---
> drivers/usb/dwc3/core.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index ccc3895dbd7f..1928b074b2df 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -2537,7 +2537,7 @@ static int dwc3_suspend(struct device *dev)
> static int dwc3_resume(struct device *dev)
> {
> struct dwc3 *dwc = dev_get_drvdata(dev);
> - int ret;
> + int ret = 0;
>
> pinctrl_pm_select_default_state(dev);
>
> @@ -2547,12 +2547,11 @@ static int dwc3_resume(struct device *dev)
> ret = dwc3_resume_common(dwc, PMSG_RESUME);
> if (ret) {
> pm_runtime_set_suspended(dev);
> - return ret;
> }
>
> pm_runtime_enable(dev);
>
> - return 0;
> + return ret;
> }
>
> static void dwc3_complete(struct device *dev)
>
> base-commit: ad618736883b8970f66af799e34007475fe33a68
> --
> 2.46.0.469.g59c65b2a67-goog
>
next prev parent reply other threads:[~2024-09-07 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 0:58 Roy Luo
2024-09-07 0:58 ` Thinh Nguyen [this message]
2024-09-13 18:02 ` Roy Luo
2024-09-13 18:12 ` Thinh Nguyen
2024-09-13 23:24 ` Roy Luo
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=20240907005829.ldaspnspaegq5m4t@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=badhri@google.com \
--cc=frank.wang@rock-chips.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=royluo@google.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®