From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Hal Emmerich <hal@halemmerich.com>,
linux-usb@vger.kernel.org, hminas@synopsys.com
Subject: [RESEND,v2] usb: dwc2: disable power_down on rockchip for regression
Date: Wed, 14 Nov 2018 11:01:05 +0200 [thread overview]
Message-ID: <875zx0jani.fsf@linux.intel.com> (raw)
Hal Emmerich <hal@halemmerich.com> writes:
> From 04fbf78e4e569bf872f1ffcb0a6f9b89569dc913 Mon Sep 17 00:00:00 2001
> From: Hal Emmerich <hal@halemmerich.com>
> Date: Thu, 19 Jul 2018 21:48:08 -0500
> Subject: [PATCH] usb: dwc2: disable power_down on rockchip devices
>
> The bug would let the usb controller enter partial power down,
> which was formally known as hibernate, upon boot if nothing was plugged
> in to the port. Partial power down couldn't be exited properly, so any
> usb devices plugged in after boot would not be usable.
>
> Before the name change, params.hibernation was false by default, so
> _dwc2_hcd_suspend() would skip entering hibernation. With the
> rename, _dwc2_hcd_suspend() was changed to use params.power_down
> to decide whether or not to enter partial power down.
>
> Since params.power_down is non-zero by default, it needs to be set
> to 0 for rockchip devices to restore functionality.
>
> This bug was reported in the linux-usb thread:
> REGRESSION: usb: dwc2: USB device not seen after boot
>
> The commit that caused this regression is:
> 6d23ee9caa6790aea047f9aca7f3c03cb8d96eb6
What are these weird space characters you're using in your commit log?
I've fixed it locally this time, but please fix your editor.
next reply other threads:[~2018-11-14 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 9:01 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-08 22:48 [RESEND,v2] usb: dwc2: disable power_down on rockchip for regression Doug Anderson
2018-11-01 5:42 Minas Harutyunyan
2018-10-31 23:02 Hal Emmerich
2018-10-29 9:02 Minas Harutyunyan
2018-10-26 14:38 Hal Emmerich
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=875zx0jani.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=hal@halemmerich.com \
--cc=hminas@synopsys.com \
--cc=linux-usb@vger.kernel.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).