aboutsummaryrefslogtreecommitdiffstats
path: root/include/linux/wimax.h
diff options
context:
space:
mode:
authorInaky Perez-Gonzalez <inaky@linux.intel.com>2009-05-08 15:51:44 -0700
committerInaky Perez-Gonzalez <inaky@linux.intel.com>2009-05-28 18:02:27 -0700
commit2618ab774ea015089c6eb84787f7ede6f2a2cbd0 (patch)
tree98bdbb3c1f18d1505d09e3d1cd0bbd19f741a7d7 /include/linux/wimax.h
parent7f0333eb2f98bbfece4fbfe21076d0a3e49f0bb0 (diff)
downloadmrst-s0i3-test-2618ab774ea015089c6eb84787f7ede6f2a2cbd0.tar.gz
mrst-s0i3-test-2618ab774ea015089c6eb84787f7ede6f2a2cbd0.tar.xz
mrst-s0i3-test-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 'include/linux/wimax.h')
0 files changed, 0 insertions, 0 deletions