| commit | aab2d4086a1876fcff282aa36e2d4a92aa9935c9 | |
| author | Jason Wessel <jason.wessel@windriver.com> | |
| Thu, 20 Aug 2009 20:39:55 +0000 (20 15:39 -0500) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Wed, 23 Sep 2009 13:46:38 +0000 (23 06:46 -0700) | ||
| tree | 3b1bb3d934bec91c44eaf61aadb6c624eb8dd9b3 | treesnapshot (tar.gz zip) |
| parent | 8d053c79f22462f55c02c8083580730b922cf7b4 | commitdiff |
USB: ehci-dbgp: errata for EHCI debug controller initialization
On some EHCI usb debug controllers, the EHCI debug device will fail to
be seen after a port reset, after a warm reset. Two options exist to
get the device to initialize correctly.
Option 1 is to unplug and plug in the device.
Option 2 is to use the EHCI port test to get the usb debug device to
start talking again. At that point the debug controller port reset
will succeed.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Yinghai Lu <yinghai@kernel.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
CC: dbrownell@users.sourceforge.net
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
On some EHCI usb debug controllers, the EHCI debug device will fail to
be seen after a port reset, after a warm reset. Two options exist to
get the device to initialize correctly.
Option 1 is to unplug and plug in the device.
Option 2 is to use the EHCI port test to get the usb debug device to
start talking again. At that point the debug controller port reset
will succeed.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Yinghai Lu <yinghai@kernel.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
CC: dbrownell@users.sourceforge.net
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/usb/early/ehci-dbgp.c | diffblobblamehistory | |
| include/linux/usb/ehci_def.h | diffblobblamehistory |