From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/7] usb: xhci: plat: Fix suspend/resume when the optional clk exists
Date: Fri, 4 Dec 2015 22:13:37 +0800 [thread overview]
Message-ID: <20151204221337.46ded0bd@xhacker> (raw)
In-Reply-To: <1449238252-5630-2-git-send-email-jszhang@marvell.com>
cc linux-usb at vger.kernel.org
On Fri, 4 Dec 2015 22:10:46 +0800
Jisheng Zhang wrote:
> Commit 4718c1774051 ("usb: host: xhci-plat: add clock support") adds
> optional clk support, but it forgets to prepare/disable and
> enable/unprepare the clk in the resume/suspend path. This path fixes
> this issue by adding missing clk related calls.
>
> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> Fixes: 4718c1774051 ("usb: host: xhci-plat: add clock support")
> ---
> drivers/usb/host/xhci-plat.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/host/xhci-plat.c b/drivers/usb/host/xhci-plat.c
> index 05647e6..b566304 100644
> --- a/drivers/usb/host/xhci-plat.c
> +++ b/drivers/usb/host/xhci-plat.c
> @@ -226,6 +226,7 @@ static int xhci_plat_remove(struct platform_device *dev)
> #ifdef CONFIG_PM_SLEEP
> static int xhci_plat_suspend(struct device *dev)
> {
> + int ret;
> struct usb_hcd *hcd = dev_get_drvdata(dev);
> struct xhci_hcd *xhci = hcd_to_xhci(hcd);
>
> @@ -237,14 +238,25 @@ static int xhci_plat_suspend(struct device *dev)
> * reconsider this when xhci_plat_suspend enlarges its scope, e.g.,
> * also applies to runtime suspend.
> */
> - return xhci_suspend(xhci, device_may_wakeup(dev));
> + ret = xhci_suspend(xhci, device_may_wakeup(dev));
> + if (ret)
> + return ret;
> +
> + clk_disable_unprepare(xhci->clk);
> +
> + return ret;
> }
>
> static int xhci_plat_resume(struct device *dev)
> {
> + int ret;
> struct usb_hcd *hcd = dev_get_drvdata(dev);
> struct xhci_hcd *xhci = hcd_to_xhci(hcd);
>
> + ret = clk_prepare_enable(xhci->clk);
> + if (ret)
> + return ret;
> +
> return xhci_resume(xhci, 0);
> }
>
next prev parent reply other threads:[~2015-12-04 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 14:10 [PATCH 0/7] usb: xhci-plat: support generic PHY and vbus regulator Jisheng Zhang
2015-12-04 14:10 ` [PATCH 1/7] usb: xhci: plat: Fix suspend/resume when the optional clk exists Jisheng Zhang
2015-12-04 14:13 ` Jisheng Zhang [this message]
2015-12-04 14:10 ` [PATCH 2/7] usb: xhci: plat: attach the usb_phy to the correct hcd Jisheng Zhang
2015-12-04 14:14 ` Jisheng Zhang
2015-12-04 14:10 ` [PATCH 3/7] usb: xhci: plat: Fix suspend/resume when the optional usb_phy exists Jisheng Zhang
2015-12-04 14:15 ` Jisheng Zhang
2015-12-04 14:10 ` [PATCH 4/7] usb: xhci: plat: sort the headers in alphabetic order Jisheng Zhang
2015-12-04 14:18 ` Jisheng Zhang
2015-12-04 14:10 ` [PATCH 5/7] usb: xhci: plat: Remove checks for optional clock in error/remove path Jisheng Zhang
2015-12-04 14:19 ` Jisheng Zhang
2015-12-04 14:10 ` [PATCH 6/7] usb: xhci: plat: add generic PHY support Jisheng Zhang
2015-12-04 14:20 ` Jisheng Zhang
2015-12-04 14:10 ` [PATCH 7/7] usb: xhci: plat: add vbus regulator control Jisheng Zhang
2015-12-04 14:20 ` Jisheng Zhang
2015-12-04 14:13 ` [PATCH 0/7] usb: xhci-plat: support generic PHY and vbus regulator Jisheng Zhang
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=20151204221337.46ded0bd@xhacker \
--to=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.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).