From: Jingoo Han <jg1.han@samsung.com>
To: "'Alan Stern'" <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
kgene.kim@samsung.com,
"'Vivek Gautam'" <gautam.vivek@samsung.com>,
"'Jingoo Han'" <jg1.han@samsung.com>
Subject: Re: [PATCH 1/2] usb: ehci-exynos: Return immediately from suspend if ehci_suspend fails
Date: Thu, 10 Apr 2014 09:23:48 +0900 [thread overview]
Message-ID: <001a01cf5453$243d9c70$6cb8d550$%han@samsung.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1404091430240.28384-100000@netrider.rowland.org>
On Thursday, April 10, 2014 3:32 AM, Alan Stern wrote:
> On Wed, 9 Apr 2014, Vivek Gautam wrote:
>
> > Patch 'b8efdaf USB: EHCI: add check for wakeup/suspend race'
> > adds a check for possible race between suspend and wakeup interrupt,
> > and thereby it returns -EBUSY as error code if there's a wakeup
> > interrupt.
> > So the platform host controller should not proceed further with
> > its suspend callback, rather should return immediately to avoid
> > powering down the essential things, like phy.
> >
> > Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
> > Cc: Alan Stern <stern@rowland.harvard.edu>
> > Cc: Jingoo Han <jg1.han@samsung.com>
> > ---
> >
> > Based on 'usb-next' branch of Greg's usb tree.
> >
> > drivers/usb/host/ehci-exynos.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/usb/host/ehci-exynos.c b/drivers/usb/host/ehci-exynos.c
> > index d1d8c47..a4550eb 100644
> > --- a/drivers/usb/host/ehci-exynos.c
> > +++ b/drivers/usb/host/ehci-exynos.c
> > @@ -212,6 +212,8 @@ static int exynos_ehci_suspend(struct device *dev)
> > int rc;
> >
> > rc = ehci_suspend(hcd, do_wakeup);
> > + if (rc)
> > + return rc;
> >
> > if (exynos_ehci->otg)
> > exynos_ehci->otg->set_host(exynos_ehci->otg, &hcd->self);
> > @@ -221,7 +223,7 @@ static int exynos_ehci_suspend(struct device *dev)
> >
> > clk_disable_unprepare(exynos_ehci->clk);
> >
> > - return rc;
> > + return 0;
> > }
> >
> > static int exynos_ehci_resume(struct device *dev)
>
> The first hunk of this patch is correct, but the second hunk isn't
> needed. A similar remark is true for the ehci-platform patch.
Hi Alan,
Do you mean the following?
1st hunk
+ if (rc)
+ return rc;
2nd hunk
- return rc;
+ return 0;
Currently, the 'rc' will be always 'zero'; however, I don't
Have any objection, because the code might be modified later.
Best regards,
Jingoo Han
>
> Alan Stern
next prev parent reply other threads:[~2014-04-10 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 4:00 Vivek Gautam
2014-04-09 4:00 ` [PATCH 2/2] usb: ehci-platform: " Vivek Gautam
2014-04-09 5:01 ` [PATCH 1/2] usb: ehci-exynos: " Jingoo Han
2014-04-09 18:32 ` Alan Stern
2014-04-10 0:23 ` Jingoo Han [this message]
2014-04-10 1:36 ` Alan Stern
2014-04-10 5:31 ` Vivek Gautam
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='001a01cf5453$243d9c70$6cb8d550$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=gautam.vivek@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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®