From: Felipe Balbi <balbi@ti.com>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: Paul Zimmerman <paulz@synopsys.com>, Felipe Balbi <balbi@ti.com>,
Dinh Nguyen <dinguyen@opensource.altera.com>,
<romain.perier@gmail.com>, Heiko Stuebner <heiko@sntech.de>,
<dianders@chromium.org>, <sonnyrao@chromium.org>,
<addy.ke@rock-chips.com>, <cf@rock-chips.com>,
<wulf@rock-chips.com>, <huangtao@rock-chips.com>,
<linux-rockchip@lists.infradead.org>,
Roy Li <roy.li@rock-chips.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] usb: dwc2: resume root hub when device detect with suspend state
Date: Mon, 17 Nov 2014 22:35:20 -0600 [thread overview]
Message-ID: <20141118043520.GA19332@saruman> (raw)
In-Reply-To: <1416273684-11300-1-git-send-email-kever.yang@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Tue, Nov 18, 2014 at 09:21:24AM +0800, Kever Yang wrote:
> After we implement the bus_suspend/resume, auto suspend id enabled.
> The root hub will be auto suspend if there is no device connected,
> we need to resume the root hub when a device connect detect.
>
> This patch tested on rk3288.
>
> Signed-off-by: Roy Li <roy.li@rock-chips.com>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
looks correct to my eyes. It's the same thing XHCI does.
Reviewed-by: Felipe Balbi <balbi@ti.com>
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-18 4:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 1:21 [PATCH v2] usb: dwc2: resume root hub when device detect with suspend state Kever Yang
2014-11-18 3:01 ` Doug Anderson
2014-11-18 4:35 ` Felipe Balbi [this message]
2014-11-18 16:07 ` Alan Stern
2014-11-18 16:41 ` Felipe Balbi
2014-11-19 2:03 ` Julius Werner
2014-11-19 16:00 ` Alan Stern
[not found] ` <2014111916244796336915@rock-chips.com>
2014-11-19 19:27 ` Julius Werner
2014-11-19 16:06 ` Mathias Nyman
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=20141118043520.GA19332@saruman \
--to=balbi@ti.com \
--cc=addy.ke@rock-chips.com \
--cc=cf@rock-chips.com \
--cc=dianders@chromium.org \
--cc=dinguyen@opensource.altera.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=paulz@synopsys.com \
--cc=romain.perier@gmail.com \
--cc=roy.li@rock-chips.com \
--cc=sonnyrao@chromium.org \
--cc=wulf@rock-chips.com \
/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