diff options
author | Duncan Laurie <dlaurie@chromium.org> | 2013-09-25 14:08:16 -0700 |
---|---|---|
committer | Patrick Georgi <patrick@georgi-clan.de> | 2014-07-11 18:08:02 +0200 |
commit | 16a0f5c4e3677ce93949bb5383ebd04a636d13e7 (patch) | |
tree | cc0b5d3ef9228f19c47a0b876c9396b8d3f09c56 /documentation/Kconfig.tex | |
parent | 7fc2da910766686d55d489d0e539a1586b98d5bb (diff) | |
download | coreboot-16a0f5c4e3677ce93949bb5383ebd04a636d13e7.tar.xz |
intel/lynxpoint: xhci: Revert suspend/resume changes
I have been attempting to work around USB3 issues that appear in the
kernel with hacks in the firmware, but this is resulting in more
headaches in the kernel.
Instead remove all the work that was being done at resume time and undo
the change that was issuing a warm reset to all ports at suspend time.
The bad device behavior will be dealt with at the kernel level to
handle devices that get stuck in polling state after enable/disable
sequence.
BUG=chrome-os-partner:22754
BRANCH=falco,peppy,wolf,leon
TEST=manual:
suspend/resume with several misbehaving devices:
Kingston USB3 Media Reader
Transcend USB3 Media Reader
Various ADATA USB3 drives
Various Kingston USB3 sticks
Original-Change-Id: I0894454af42d2ced456fe0da921d74c9e74902d0
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/170107
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
(cherry picked from commit c2abb4d0dad6ed00e1e230d604c4c0a76eb4eef7)
Change-Id: Ib215d9c230f90a1c9f34bf29254bb9feec28c67e
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/170578
[pm: rebase to master branch of coreboot upstream]
Signed-off-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-on: http://review.coreboot.org/6016
Tested-by: build bot (Jenkins)
Reviewed-by: Patrick Georgi <patrick@georgi-clan.de>
Diffstat (limited to 'documentation/Kconfig.tex')
0 files changed, 0 insertions, 0 deletions