diff options
| author | Vipin Mehta <vmehta@atheros.com> | 2011-02-18 13:13:05 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-02-18 13:28:50 -0800 |
| commit | 83195cc8a83df3546d72873ca2aed51f97b0c901 (patch) | |
| tree | 8b787163ac6f92e78ba745147ca74e4f529fdd9b /include/linux/mutex-debug.h | |
| parent | 3f2fd78e68cdea8805c92b72008b9eb42f6580f6 (diff) | |
staging: ath6kl: Fixing target crash due to mismatch connect/disconnect
Firmware design requires a WMI_DISCONNECT_CMD for every WMI_CONNECT_CMD to
clear the firmware previous profile state. There is one case in linux host
driver where two WMI_CONNECT_CMD are given without a WMI_DISCONNECT_CMD.
This causes firmware state to mismatch causing an ASSERT. Use the driver
state variable arConnectPending to track whether a WMI_CONNECT_CMD is
issued to firmware.
Signed-off-by: Vipin Mehta <vmehta@atheros.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'include/linux/mutex-debug.h')
0 files changed, 0 insertions, 0 deletions