From: Greg KH <gregkh@linuxfoundation.org>
To: Guan-Yu Lin <guanyulin@google.com>
Cc: Thinh.Nguyen@synopsys.com, mathias.nyman@intel.com,
stern@rowland.harvard.edu, elder@kernel.org, oneukum@suse.com,
yajun.deng@linux.dev, dianders@chromium.org, kekrby@gmail.com,
perex@perex.cz, tiwai@suse.com, tj@kernel.org,
stanley_chang@realtek.com, andreyknvl@gmail.com,
christophe.jaillet@wanadoo.fr, quic_jjohnson@quicinc.com,
ricardo@marliere.net, grundler@chromium.org,
niko.mauno@vaisala.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
badhri@google.com, albertccwang@google.com,
quic_wcheng@quicinc.com, pumahsu@google.com
Subject: Re: [PATCH v4 1/5] usb: dwc3: separate dev_pm_ops for each pm_event
Date: Wed, 9 Oct 2024 14:45:42 +0200 [thread overview]
Message-ID: <2024100943-gallantly-animosity-2822@gregkh> (raw)
In-Reply-To: <20241009054429.3970438-2-guanyulin@google.com>
On Wed, Oct 09, 2024 at 05:42:55AM +0000, Guan-Yu Lin wrote:
> Separate dev_pm_ops for different power events such as suspend, thaw,
> and hibernation. This is crucial when dwc3 driver needs to adapt its
> behavior based on different power state changes.
>
> Signed-off-by: Guan-Yu Lin <guanyulin@google.com>
> ---
> drivers/usb/dwc3/core.c | 77 ++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 76 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index b25d80f318a9..2fdafbcbe44c 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -2582,6 +2582,76 @@ static int dwc3_resume(struct device *dev)
> return 0;
> }
>
> +static int dwc3_freeze(struct device *dev)
> +{
> + struct dwc3 *dwc = dev_get_drvdata(dev);
> + int ret;
> +
> + ret = dwc3_suspend_common(dwc, PMSG_FREEZE);
> + if (ret)
> + return ret;
> +
> + pinctrl_pm_select_sleep_state(dev);
> +
> + return 0;
> +}
> +
> +static int dwc3_thaw(struct device *dev)
> +{
> + struct dwc3 *dwc = dev_get_drvdata(dev);
> + int ret;
> +
> + pinctrl_pm_select_default_state(dev);
> +
> + pm_runtime_disable(dev);
> + pm_runtime_set_active(dev);
> +
> + ret = dwc3_resume_common(dwc, PMSG_THAW);
> + if (ret) {
> + pm_runtime_set_suspended(dev);
> + return ret;
> + }
> +
> + pm_runtime_enable(dev);
> +
> + return 0;
> +}
> +
> +static int dwc3_poweroff(struct device *dev)
> +{
> + struct dwc3 *dwc = dev_get_drvdata(dev);
> + int ret;
> +
> + ret = dwc3_suspend_common(dwc, PMSG_HIBERNATE);
Why is power off hibernate?
This needs an ack from the dwc3 maintainer as I can't determine if it's
correct at all...
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-09 12:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 5:42 [PATCH v4 0/5] Support system sleep with offloaded usb transfers Guan-Yu Lin
2024-10-09 5:42 ` [PATCH v4 1/5] usb: dwc3: separate dev_pm_ops for each pm_event Guan-Yu Lin
2024-10-09 12:45 ` Greg KH [this message]
2024-10-10 4:12 ` Guan-Yu Lin
2024-10-09 5:42 ` [PATCH v4 2/5] usb: xhci-plat: " Guan-Yu Lin
2024-10-09 5:42 ` [PATCH v4 3/5] usb: add apis for sideband uasge tracking Guan-Yu Lin
2024-10-09 7:33 ` Amadeusz Sławiński
2024-10-09 11:36 ` Guan-Yu Lin
2024-10-09 12:44 ` Greg KH
2024-10-10 5:30 ` Guan-Yu Lin
2024-10-10 6:33 ` Greg KH
2024-10-10 16:14 ` Guan-Yu Lin
2024-10-11 4:30 ` Greg KH
2024-10-11 7:33 ` Guan-Yu Lin
2024-10-09 5:42 ` [PATCH v4 4/5] xhci: sideband: add api to trace sideband usage Guan-Yu Lin
2024-10-09 12:47 ` Greg KH
2024-10-10 4:16 ` Guan-Yu Lin
2024-10-09 5:42 ` [PATCH v4 5/5] usb: host: enable sideband transfer during system sleep Guan-Yu Lin
2024-10-09 12:47 ` Greg KH
2024-10-11 7:34 ` Guan-Yu Lin
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=2024100943-gallantly-animosity-2822@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=albertccwang@google.com \
--cc=andreyknvl@gmail.com \
--cc=badhri@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dianders@chromium.org \
--cc=elder@kernel.org \
--cc=grundler@chromium.org \
--cc=guanyulin@google.com \
--cc=kekrby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=niko.mauno@vaisala.com \
--cc=oneukum@suse.com \
--cc=perex@perex.cz \
--cc=pumahsu@google.com \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_wcheng@quicinc.com \
--cc=ricardo@marliere.net \
--cc=stanley_chang@realtek.com \
--cc=stern@rowland.harvard.edu \
--cc=tiwai@suse.com \
--cc=tj@kernel.org \
--cc=yajun.deng@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