diff options
author | Sergei Shtylyov <sshtylyov@ru.mvista.com> | 2011-07-06 23:19:38 +0400 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-07-08 14:55:47 -0700 |
commit | 81463c1d707186adbbe534016cd1249edeab0dac (patch) | |
tree | 28ebdec53e33efce94b8a3d6be1f804e5d43a3d3 /include/linux/usb | |
parent | 8dec92b24064f1ffbb6537ba97729b633b400c28 (diff) | |
download | linux-81463c1d707186adbbe534016cd1249edeab0dac.tar.gz linux-81463c1d707186adbbe534016cd1249edeab0dac.tar.bz2 linux-81463c1d707186adbbe534016cd1249edeab0dac.zip |
EHCI: only power off port if over-current is active
MAX4967 USB power supply chip we use on our boards signals over-current when
power is not enabled; once it's enabled, over-current signal returns to normal.
That unfortunately caused the endless stream of "over-current change on port"
messages. The EHCI root hub code reacts on every over-current signal change
with powering off the port -- such change event is generated the moment the
port power is enabled, so once enabled the power is immediately cut off.
I think we should only cut off power when we're seeing the active over-current
signal, so I'm adding such check to that code. I also think that the fact that
we've cut off the port power should be reflected in the result of GetPortStatus
request immediately, hence I'm adding a PORTSCn register readback after write...
Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: stable@kernel.org
Acked-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'include/linux/usb')
0 files changed, 0 insertions, 0 deletions