From: John Youn <John.Youn@synopsys.com>
To: Douglas Anderson <dianders@chromium.org>,
"John.Youn@synopsys.com" <John.Youn@synopsys.com>,
"balbi@ti.com" <balbi@ti.com>
Cc: "heiko@sntech.de" <heiko@sntech.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"lyz@rock-chips.com" <lyz@rock-chips.com>,
"wulf@rock-chips.com" <wulf@rock-chips.com>,
"dinguyen@opensource.altera.com" <dinguyen@opensource.altera.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RFT: usb: dwc2: bus suspend/resume that's not hibernate
Date: Thu, 5 Nov 2015 04:02:24 +0000 [thread overview]
Message-ID: <2B3535C5ECE8B5419E3ECBE30077290901DC3BA613@US01WEMBX2.internal.synopsys.com> (raw)
In-Reply-To: 1446237173-15263-1-git-send-email-dianders@chromium.org
On 10/30/2015 1:33 PM, Douglas Anderson wrote:
> This is an attempt to rehash commit 0cf884e819e0 ("usb: dwc2: add bus
> suspend/resume for dwc2") on ToT. That commit was reverted in commit
> b0bb9bb6ce01 ("Revert "usb: dwc2: add bus suspend/resume for dwc2"")
> because apparently it broke the Altera SOCFPGA.
>
> With all the changes that have happened to dwc2 in the meantime, it's
> possible that the Altera SOCFPGA will just magically work with this
> change now. ...and it would be good to get bus suspend/resume
> implemented.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
Hi Dinh,
Are you familiar with this? Would you care to test it?
I'm not sure what the breakage was but if you provide steps to
reproduce on the SOCFPGA I could try as well.
Regards,
John
prev parent reply other threads:[~2015-11-05 4:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 20:32 [PATCH] RFT: usb: dwc2: bus suspend/resume that's not hibernate Douglas Anderson
2015-11-05 4:02 ` John Youn [this message]
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=2B3535C5ECE8B5419E3ECBE30077290901DC3BA613@US01WEMBX2.internal.synopsys.com \
--to=john.youn@synopsys.com \
--cc=balbi@ti.com \
--cc=dianders@chromium.org \
--cc=dinguyen@opensource.altera.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lyz@rock-chips.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.