diff options
author | Inaky Perez-Gonzalez <inaky@linux.intel.com> | 2009-05-08 15:51:44 -0700 |
---|---|---|
committer | Inaky Perez-Gonzalez <inaky@linux.intel.com> | 2009-05-28 18:02:27 -0700 |
commit | 2618ab774ea015089c6eb84787f7ede6f2a2cbd0 (patch) | |
tree | 98bdbb3c1f18d1505d09e3d1cd0bbd19f741a7d7 /drivers/scsi/NCR5380.c | |
parent | 7f0333eb2f98bbfece4fbfe21076d0a3e49f0bb0 (diff) | |
download | kernel-crypto-2618ab774ea015089c6eb84787f7ede6f2a2cbd0.tar.gz kernel-crypto-2618ab774ea015089c6eb84787f7ede6f2a2cbd0.tar.xz kernel-crypto-2618ab774ea015089c6eb84787f7ede6f2a2cbd0.zip |
wimax/i2400m: usb: fix device reset on autosuspend while not yet idle
When the i2400m is connected to a network, the host interface (USB)
cannot be suspended. For that to happen, the device has to have
negotiated with the basestation to put the link on IDLE state.
If the host tries to put the device in standby while it is connected
but not idle, the device resets, as the driver should not do that.
To avoid triggering that, when the USB susbsytem requires the driver
to autosuspend the device, the driver checks if the device is not yet
idle. If it is not, the request is requested (will be retried again
later on after the autosuspend timeout). At some point the device will
enter idle and the request will succeed (unless of course, there is
network traffic, but at that point, there is no idle neither in the
link or the host interface).
Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Diffstat (limited to 'drivers/scsi/NCR5380.c')
0 files changed, 0 insertions, 0 deletions